Minor impactResolvedDatabases

Supabase incident: Intermittent 502/503 errors for pg_net calls to Edge Functions

Supabase reported this minor-impact incident on its official status page on Nov 5, 2026, 23:12 UTC. It was resolved after 42 min.

Right now Supabase is operational. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Nov 5, 2026, 23:12 UTC
started
Nov 5, 2026, 23:55 UTC
resolved
42 min
duration
Minor
impact
  1. resolvedNov 5, 2026, 23:55 UTC

    The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.

  2. investigatingNov 5, 2026, 23:12 UTC

    We are seeing intermittent 502 and 503 errors affecting Edge Functions requests in ap-southeast-1. We will provide updates and more information becomes available.

What APIStatus.watch saw

  • Nov 5, 2026, 23:16 UTCoperational → degraded
  • Nov 5, 2026, 23:56 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Supabase have incidents?

Supabase reported 59 incidents in the last 90 days, 22 of them major or critical. A typical incident lasted 2h. See Supabase's uptime and incident history