Supabase statusLiveFetched seconds agoSource: status.supabase.com
Is Supabase down?
Live status check · All systems operational
Live status pulled from status.supabase.com, cached and revalidated every 60 seconds. Below: the components that can break, what to do during an incident, and how to keep your scheduled jobs running independently.
About Supabase status
Supabase fronts Postgres, Auth, Storage, Realtime, and Edge Functions for most of its users. A single regional incident can take down your sign-in flow, your scheduled jobs (pg_cron), and your file uploads simultaneously.
Components and surfaces that can break
- Surface 01
Database (direct Postgres connections, REST, GraphQL).
- Surface 02
Auth (sign-in, magic links, OAuth, JWT verification).
- Surface 03
Storage, Realtime, Edge Functions, and pg_cron.
Recent Supabase incidents
Supabase maintains a public incident history. Read the latest entries to see whether you're hitting a known issue, and look at the post-mortems for context on how long similar incidents typically take to clear.
What to do if Supabase is actually down
Identify the project's region first
Supabase incidents are usually regional (us-east-1, eu-central-1, etc.). The global status page lists the affected region; if yours isn't named, the problem is more likely your code or your network than Supabase.
Fall back to a cached read where possible
If you serve a public page that hits Supabase on every request, switch to a stale-while-revalidate cache during the incident so visitors get the last good snapshot instead of an error.
Do not stack retries against the API
When Supabase is degraded, exponential backoff with jitter is the friendly thing to do. A retry storm from your app or your cron jobs can keep the region pinned even after the underlying fault clears.
Keep firing through the incident
Schedule your own Supabase health check with Crontap
pg_cron lives inside the Postgres instance, so scheduled jobs pause when the database is down. An external scheduler can keep firing the Edge Function or REST endpoint and pick up as soon as the database is reachable again.
External HTTP cron hits your endpoint on the cadence you pick, stores every response, and emails you the moment a run fails. Pro schedules down to 1 minute; $3.25/mo annual flat for unlimited jobs.
Go deeper
Supabase status: FAQ
- How do I know if Supabase is down or just my project?
- Check status.supabase.com first — it splits status by component and region. If everything is green there, log into the Supabase dashboard and look at the project's health graphs. A single project can be unhealthy (full disk, exhausted connection pool) while the global plane is fine.
- Will pg_cron jobs catch up after a Supabase outage?
- No. pg_cron only runs when the Postgres instance is available. Skipped runs are not retried automatically. If you need guarantees, schedule the same Edge Function or RPC from an external scheduler that retries on failure.
- Can I monitor my Supabase Edge Function from outside?
- Yes. Set up a Crontap schedule that hits the function URL on your chosen cadence. The dashboard records the response status and latency, and you get an email the moment the function starts returning 5xx or timing out — independent of the official status page.