Statuspy
Databases

Is Supabase down right now?

No, it’s up.

Supabase appears to be up and running normally.

checked responded in 113msHTTP 200

Over the last 7 days, Supabase has answered our automated checks with 100.00% availability and a typical response time of ~163 ms. According to Supabase's official status page, the most recent outage began 2026-08-28 16:18 UTC and lasted 0s (severity: down). It was reported as "Projects failing to load Supautils in multiple regions".

Supabase is an open-source Firebase alternative built on Postgres, bundling authentication, storage, realtime subscriptions, and edge functions. Each component reports separately, so a project's database can be perfectly healthy while auth sign-ins or the realtime websocket fail, which looks like a total outage to end users.

Is Supabase down for everyone or just you?

Our automated checks are reaching Supabase normally right now, and it answered our last one in 113ms. That makes any trouble you are hitting more likely to be local to your connection, account or network than a full outage, which usually means you can fix it from your end.

Still not working for you?Try the fixes

Supabase response time (last 24h)

Last 24hpeak 703 ms

Supabase incident history (last 90 days)

JulAugSep
  • up
  • slow
  • down
  • no reading
All 40 recorded outages

30 of the incidents below were reported by Supabase on days we were not yet monitoring, so the timeline above leaves those days hatched rather than colouring them in.

DateWhat happenedDurationSeverity
Projects failing to load Supautils in multiple regionsReported by Supabase0sDown
Increased response times for requestsReported by Supabase1d 3hDown
pgBouncer issues on some older projectsReported by Supabase22h 34mDegraded
Issues affecting automatic disk resizingReported by Supabase2hDown
Error spikes in one of the ap-northeast-2 Supavisor clustersReported by Supabase3h 49mDegraded
Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projectsReported by Supabase3h 9mDegraded
Project creation failing in selected regionsReported by Supabase8mDegraded
Project access, updating and creation impacted in us-east-2Reported by Supabase1h 13mDown
401 errors due to JWT rejectionsReported by Supabase13d 14hDegraded
Project Upgrade DelaysReported by Supabase2d 2hDegraded
Management API Performance DegradationReported by Supabase4d 1hDegraded
DNS creation delaysReported by Supabase58mDegraded
Log Ingestion IssuesReported by Supabase52mDegraded
Management API Performance DegradationReported by Supabase5h 51mDegraded
Issues with Edge Function DeploymentReported by Supabase19h 42mDown
SSO login failures in us-east-1Reported by Supabase42mDegraded
Documents Search UnavailableReported by Supabase6mDegraded
Delays in creation of DNS recordsReported by Supabase2h 1mDegraded
Project Resize Problems in US-West-2Reported by Supabase3h 4mDown
Authentication issues for some projectsReported by Supabase34mDegraded
Log Ingestion ProblemsReported by Supabase3h 40mDegraded
Project Actions Failing Across Multiple RegionsReported by Supabase7h 51mDown
S3 endpoints for keys with special characters brokenReported by Supabase53mDegraded
Projects in stuck state in EU-CENTRAL-1 (Frankfurt)Reported by Supabase4h 35mDown
Errors configuring authentication providersReported by Supabase45mDegraded
Degraded log ingestionReported by Supabase4h 13mDegraded
Elevated JWT authorization errorsReported by Supabase1h 19mDegraded
Project creation delays in AP regionsReported by Supabase2h 37mDegraded
Endpoints in Americas regions returning 500 Internal server errorReported by Supabase1h 25mDown
Degraded project creation success rates in the ca-central-1 regionReported by Supabase5h 51mDegraded
Errors when attempting to view advisor results in the Supabase dashboardReported by Supabase2h 47mDegraded
Delays in newly created project setupReported by Supabase1h 16mDegraded
Functions management API is returning 500s for multiple function operationsReported by Supabase1h 31mDown
Project status change failures in multiple regionsReported by Supabase13d 12hDown
Upgrade FailuresReported by Supabase4h 31mDegraded
Elevated errors on Postgres change subscriptionsReported by Supabase2h 23mDegraded
Degraded performance of the Shared Pooler cluster in ap-southeast-1Reported by Supabase14mDegraded
Project create and unpause errors in eu-west-1Reported by Supabase1h 15mDegraded
Increased latency for Management API requestsReported by Supabase58mDegraded

Supabase uptime

100.00%
7 days
100.00%
30 days
100.00%
90 days

Measured since 2026-08-12. Windows reaching further back are averaged over the 39 days we watched, not the full period. Counts our own checks. Days Supabase reported an incident are coloured in the timeline above but do not change this figure.

What to do if Supabase is down for just you

  • Check your project's status in the dashboard: a paused free-tier project refuses connections exactly like an outage.
  • Distinguish the database from Auth, Storage and Edge Functions — each can fail on its own.
  • If connections are refused under load, you may be exhausting the connection pool; use the pooled connection string.
  • Confirm your API keys and Row Level Security policies haven't changed, since a policy denial reads as a failed query.

Frequently asked questions

Supabase appears to be up and running normally. Last checked 2026-09-19 02:54 UTC.

Supabase’s official status page

Related services