Supabase outage, 12 November 2026

Database Connection Errors

Started
Resolved
12 Nov 2026, 23:40 UTC (after 3 h 4 min)
Impact
Minor

Is this still happening?

No. Supabase marked this incident resolved on 12 Nov 2026, 23:40 UTC, 3 h 4 min after it began.

Right now: Supabase reports all systems operational. (as of 13 Nov, 20:53 UTC) Live Supabase status

At a glance

Our summary from the Supabase incidents we have recorded since 28 Aug 2026 - how we count.

Last update from Supabase

The issue has been resolved, and services across all affected regions have recovered. We are no longer observing elevated connection errors and will close this incident.

12 Nov 2026, 23:40 UTC

Similar Supabase incidents

Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.

  1. , resolved

    Intermittent connection errors via the connection pooler in us-east-1

Other recent Supabase incidents

  1. Elevated Error rates for All Supabase project APIs

  2. Storage request degradation in eu-west-1

  3. Project Lifecycle Issues in ap-northeast-1

  4. Interruption in connections to Supavisor in eu-west-2

  5. Increased Errors with Project Lifecycle Operations in US-West-2

  6. Intermittent 502/503 errors for pg_net calls to Edge Functions

  7. Storage issues in us-east-1 and eu-central-1

  8. Intermittent errors on Supavisor Shared Pooler in us-east-2

All recorded Supabase incidents

Something wrong on this page?

A person reads every report. We fix our own mistakes - wording, mapping, a moved status page; the status itself always comes from Supabase's official page. How we handle corrections.

Thanks - your report is on its way to us. We read every one.