Live check
Is Supabase down right now?
Observed from Supabase’s public feed by our independent monitor. Always confirm operational decisions on the official status page.
While you wait: the Supabase incident checklist
- Scope which service and region. Supabase separates Database (Postgres), Auth, Realtime, Storage, Edge Functions, the API gateway and the dashboard — and incidents are frequently region-scoped. Check the component and the region your project lives in before declaring impact.
- Separate auth from data. An Auth incident blocks new logins and token issuance while existing JWTs stay valid until they expire — so users can be 'logged in' but unable to sign in. That points at Auth, not your database.
- Check pooling before blaming the platform. Connection errors can be your own pool exhaustion (Supavisor/PgBouncer limits, a leak, a traffic spike) rather than a Supabase incident. Confirm on the status page before you restart everything.
- Know your recovery posture. If the data plane is degraded, don't run risky migrations or bulk writes mid-incident. Know which plan-level backups/PITR you have before you need them — an incident is not the time to discover your recovery window.
- Dashboard-only vs data-plane. A dashboard/API-gateway incident can leave your app serving fine while you just can't manage the project. Don't page the whole team for a control-plane blip that users never see.
What breaks when Supabase has issues
Supabase sits under your app's data and auth, so a data-plane incident is customer-facing: logins fail, reads and writes error, Realtime subscriptions drop, Storage assets 404 and Edge Functions error. A control-plane (dashboard) incident is the milder case — the app keeps serving while you lose the ability to manage it. Because incidents are usually region-scoped, the first question is always which region your project runs in.
FAQ
Is it Supabase or my project?
Check status.supabase.com for your project's region and the specific component. Connection-limit or query errors with a green status page usually mean your own pooling, a slow query or a traffic spike — not a platform incident.
Why can users stay logged in but not sign in?
Auth and the database are separate components. An Auth incident stops new logins and token issuance while already-issued JWTs remain valid until expiry, so existing sessions keep working.
Is my data at risk during an outage?
An availability incident is not the same as data loss. Durability depends on your plan's backups and point-in-time recovery; know that posture in advance and avoid risky migrations or bulk writes until the data plane is confirmed healthy.
The dashboard is down but my app works — why?
That's a control-plane incident. The API gateway or dashboard can be degraded while your app's database and auth keep serving. Users won't notice; you just can't manage the project until it clears.
Put Supabase’s status in your toolbar
Is it you — or your vendor? You checked once. The extension watches Supabase and the rest of your stack continuously — badge, popup and Side Panel, free for 5 vendors, no account.
Add to Chrome — free, no accountNot an outage? Track API changes before they become incidents.
VendorStatus shows when a dependency is failing now. Breakwater watches official developer changelogs and migration deadlines locally in your browser, so your team can plan the change before the next deploy.
Also on your stack?
Not affiliated with Supabase. Status data comes from their public status page.