Supabase outage, 11 November 2026

Project Lifecycle Issues in ap-northeast-1

Started
Resolved
11 Nov 2026, 21:32 UTC (after 4 h 48 min)
Impact
Minor

Is this still happening?

No. Supabase marked this incident resolved on 11 Nov 2026, 21:32 UTC, 4 h 48 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

All operations have returned to normal and have remained stable.

11 Nov 2026, 21:32 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 after 2 h 27 min

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

  2. , resolved after 12 h 3 min

    Project lifecycle operation errors in the EU region

  3. , resolved after 1 h 15 min

    Project lifecycle operations such as project creation, pausing, and restoration, in all regions

  4. , resolved after 2 h 1 min

    Project Lifecycle Issues in eu-west-1

  5. , resolved after 2 h

    Project Lifecycle Activity Degradation

Other recent Supabase incidents

  1. Elevated Error rates for All Supabase project APIs

  2. Database Connection Errors

  3. Storage request degradation in eu-west-1

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

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

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

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

  8. Management API Postgres config updates overwriting previous updates

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.