{"meta":{"version":"v1","pricing":{"public":{"label":"Public","description":"Read-only API access for lightweight status checks and public integrations."},"premium":{"label":"Premium (early access)","description":"API keys with higher hourly quotas are available now; webhooks, alerting, and exports are on the roadmap."}},"generatedAt":"2026-07-08T01:30:05.302Z"},"data":{"id":"incident_statuspage_supabase_f258dnpx3ss2","slug":"supabase-edge-functions-several-users-reported-503-errors-with-supabase-edge-2026-04-28-dnpx3ss2","title":"Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code","summary":"Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code","status":"resolved","severity":"minor","startedAt":"2026-04-28T20:34:39.966+00:00","updatedAt":"2026-04-28T20:34:40.023+00:00","resolvedAt":"2026-04-24T10:00:00+00:00","provider":{"slug":"supabase","name":"Supabase"},"affectedServices":[],"links":{"html":"/incidents/supabase-edge-functions-several-users-reported-503-errors-with-supabase-edge-2026-04-28-dnpx3ss2","api":"/api/v1/incidents/supabase-edge-functions-several-users-reported-503-errors-with-supabase-edge-2026-04-28-dnpx3ss2","providerHtml":"/providers/supabase"},"impactSummary":"Supabase reported a none event for the affected tracked services.","source":{"id":"source_supabase_status","kind":"official_api","name":"Supabase Status","checkedAt":"2026-07-08T01:25:01.39+00:00","officialUrl":"https://status.supabase.com","statusPageUrl":"https://status.supabase.com"},"updates":[{"id":"update_statuspage_supabase_f258dnpx3ss2_82ssqwlz54pt","status":"resolved","body":"Incident Summary\nA 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.\n\nTimeline & Actions\nSunday, 26: Issue detected as user reports of 503 errors increased. Investigation into root cause began.\nMonday, 27: Introduced a more accurate error code (SUPABASE_EDGE_RUNTIME_SERVICE_DEGRADED) and implemented infrastructure changes to mitigate impact.\nTuesday, 28: Adjusted conditions for returning 503 responses to be less aggressive. Prepared a “retry-on-degraded” mechanism (not yet deployed).\n\nCurrent Status\nMitigations are in place and improvements to error handling are ongoing. Further resilience enhancements will be deployed shortly.","createdAt":"2026-04-28T20:34:40.014+00:00"}],"access":{"plan":"public","keyed":false}}}