Supabase project paused (HTTP 540): why your app loads but nothing saves
Your page still loads, but sign-in, saving and every data request fail. The Supabase project behind the app is paused, and Supabase answers paused projects with its own HTTP status 540.
What is happening
Your front end and your Supabase backend are hosted separately, so the page keeps loading after the backend stops.
Supabase pauses Free-plan projects after a week without activity, and also pauses on request or for abuse. While paused, requests to the project are answered with HTTP 540.
Supabase's own troubleshooting pages also describe a paused project's address no longer resolving at all (an NXDOMAIN error), which looks the same as a deleted project from the outside.
How to fix it
Open the project in the Supabase dashboard and restore it. Paused Free projects can be restored for a period after pausing.
If the project matters, a paid plan is never paused for inactivity.
After restoring, open your live app (not just the editor) and sign in once to confirm data loads.
How to hear about it before your users do
Run the free check below. It reads your app's public code, finds the Supabase project it uses, and asks its public health endpoint whether it is up, paused or gone.
Check your app now — free, no sign-up
Paste your app's address and see, from the outside, whether it loads, whether its database is awake, and whether anything here applies to you.
Run the free checkSources
Checked against these sources on 26 October 2026.