Live status · Supabase

Is Supabase down?

This page asks Supabase’s own status feed, straight from your browser, when you open it and once a minute while it stays open. It shows what Supabase reports and never fills in a gap with a guess.

Not checked

Checking needs JavaScript, which is off or has not loaded. Supabase’s own page has the answer: status.supabase.com.

Supabase’s status page

What this checks

The database, the login system, and the front door to both. What most vibe-coded apps actually run on. On this page that means the parts on Supabase’s status page whose names include “database”, “auth”, “api gateway”, “realtime” or “storage”.

The list appears after the live check.

Open incidents

Anything open appears here after the live check.

Recent incidents

Finished incidents from the last 30 days appear here after the live check.

If it is down

When the database or login part is down, your app's reads, writes and sign-ins fail with errors that look like bugs in your code. Check here before you start changing your policies.
“new row violates row-level security policy” comes from your table's policies, not from an outage: see that page.
If Supabase reports no problems and it still fails, the cause is more likely on your side: your key, your code or your network. The error explainers cover the common messages.
A status page shows what the company has reported. A problem that has started but has not been reported yet will not show here, so if the answer above is no and something still fails for everyone you know, check again in a few minutes.
Do not rewrite working code to chase an outage. Commit what you have now, so that when the service is back you can tell whether anything you changed in the meantime broke something.
Down? Save your place before you switch tools: Cold Handoff writes the note you paste into the next session, so it picks up where this one stopped instead of starting over.

Where this comes from