rewindex

CompaniesSupabaseIncidents

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

MinorStatus: resolvededitedStarted Resolved (42 min)2 updatesstatus.supabase.com (opens in new tab)

Affected components: ap-southeast-1

Timeline of updates

  1. 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.

  2. resolved

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

Changes Rewindex caught on this incident

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.

Impact, status and times are the vendor’s own, as last archived. View on status.supabase.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Supabase, started 2026-11-05 23:12 UTC, resolved after 42 min, 2 update(s); edited after publishing.

Title
Intermittent 502/503 errors for pg_net calls to Edge Functions
Vendor
Supabase
Date
URL
https://rewindex.com/company/supabase/incidents/01M6PZSAS3Q36YESDRFF8QF8JS

Supabase profileRecent Supabase incidentsAll outages on November 5, 2026Supabase in November 2026MarkdownJSON