Live / Supabase / Incident
Supabase: Intermittent 502/503 errors for pg_net calls to Edge Functions
Supabase · supabase.comMinor incidentResolved2026-11-05 23:55 UTC
Public — what happened
Summary
Supabase reported a minor incident in which some requests from its pg_net feature to Edge Functions intermittently failed with 502 and 503 errors. The company said the problem affected the ap-southeast-1 region and began at 23:12 UTC on 2026-11-05. Its only update said it was investigating, and no cause was given in the text provided. Supabase marked the incident resolved at 23:55.
Timeline
- Started — 2026-11-05 23:12 UTC
- Investigating — 2026-11-05 23:12 UTC
- Resolved — 2026-11-05 23:55 UTC · 42 min after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Supabase report →
More from Supabase
Covered in The Squid’s Ink, Week 46, 2026, our weekly internet health report.