Supabase outage, 5 November 2026

Intermittent 502/503 errors for pg_net calls to Edge Functions

Started
Resolved
5 Nov 2026, 23:55 UTC (after 42 min)
Impact
Minor

Is this still happening?

No. Supabase marked this incident resolved on 5 Nov 2026, 23:55 UTC, 42 min after it began.

Right now: Supabase reports all systems operational. (as of 13 Nov, 20:59 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 pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.

5 Nov 2026, 23:55 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 22 h 35 min

    Edge Function Degradation

  2. , resolved after 3 h 2 min

    Edge Function Latency

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. Project Lifecycle Issues in ap-northeast-1

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

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

  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.