Supabase outage on November 5, 2026: Intermittent 502/503 errors for pg_net calls to Edge Functions
Supabase has reported an incident affecting Supabase since 23:12 UTC on 5 November 2026 (37 minutes so far).
Open
Official incident reported by Supabase
- Started
- 23:12
- 5 Nov 2026 UTC
- Status
- Open
- not resolved yet
- Duration
- 37m
- 37 minutes so far
- Impact
- Minor
- as rated by Supabase
- Updates
- 1
- posted by Supabase
Timeline
All times UTC.
Official incident from Supabase
Intermittent 502/503 errors for pg_net calls to Edge Functions
-
Official
Investigating
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.
"Official" rows are quoted from Supabase's public status page, status.supabase.com. Very long posts are shortened.
What our checkpoints saw
HostTracker's checkpoints, which test supabase.com from several locations, recorded no outage of 5 minutes or longer during this incident. A provider can report a problem that affects only some features, regions or accounts, which a check of the main address does not see. The live Supabase status shows what our checks see right now.
Does your product depend on Supabase?
An outage like this one reaches your users through your product, and most teams hear about it from a customer rather than from a dashboard. HostTracker watches any endpoint you name - your own site, an API you call, a vendor you resell - from 300+ locations, confirms a failure from several of them before it says anything, and then tells you by email, SMS, voice call or your chat tool.
You get the same record you are reading here for your own services: every outage timestamped, with the checks that observed it.
Independent measurement by HostTracker. Not affiliated with Supabase. Official updates are quoted from Supabase's public status page and remain Supabase's own words.