Provider
SupabaseIncident detail
Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code
Resolved incidentMinor
Timeline window
to
Outage alerts
Get alerted the next time Supabase breaks
Free email alerts for up to 5 providers. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update Supabase posted, oldest to newest, exactly as it appeared on their official status page.
Resolved
Incident Summary
A health check designed to prevent Out-of-Memory (OOM) conditions began closing some incoming connections, which led to 503 errors for a subset of users. These errors were initially surfaced under a generic SUPABASE_EDGE_RUNTIME_ERROR code.
Timeline & Actions
Sunday, 26: Issue detected as user reports of 503 errors increased. Investigation into root cause began.
Monday, 27: Introduced a more accurate error code (SUPABASE_EDGE_RUNTIME_SERVICE_DEGRADED) and implemented infrastructure changes to mitigate impact.
Tuesday, 28: Adjusted conditions for returning 503 responses to be less aggressive. Prepared a “retry-on-degraded” mechanism (not yet deployed).
Current Status
Mitigations are in place and improvements to error handling are ongoing. Further resilience enhancements will be deployed shortly.
Keep exploring
More from Supabase
Neighboring incidents on Supabase's timeline and the rest of their record on OutageDeck.