rewindex

ChangesSupabaseIntermittent 502/503 errors for pg_net calls to Edge Functions

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

Incident updateNormal progress (rule, 100%)Changed status.supabase.com (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Supabase removed; blue is what they added. Muted text is unchanged context.

ChangedStatus#1
Before: investigating
After: resolved
AddedResolved time#2
Before: not present
After: 2026-11-05 23:55 UTC
AddedUpdateresolved#3
Before: not present
After: The issue has been resolved, and pg_net calls to Edge Functions in ap-southeast-1 are now operating normally.

Compared with the previous archived version of this incident (10 to 30-minute polling). View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Friday, November 6

1 incident change

Cite this

Incident updated: Intermittent 502/503 errors for pg_net calls to Edge Functions on Supabase’s status page, changed 2026-11-06 00:03 UTC (change 1 of 1).

Title
Incident updated: Intermittent 502/503 errors for pg_net calls to Edge Functions
Vendor
Supabase
Date
URL
https://rewindex.com/change/r524d5af4533913

All Supabase changesSupabase profileMarkdownJSON