Supabase incident
Edge Function Degradation
Resolved after 22 h 35 min.
- Started
- Ended
- Worst state
- Degraded
- On Supabase’s status page
- Source
- Components
- ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-1, eu-west-2, eu-west-3, sa-east-1, us-east-1, us-east-2, us-west-1, us-west-2
Timeline
- Supabase status page · Reported Edge Function Degradation
- Supabase status page · Identified We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.
- Supabase status page · Identified We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.
- Supabase status page · Identified Edge Functions deployments have returned to normal levels. We're now reviewing worker jobs that failed during the incident, including any backups that may have been affected. We'll re-queue these jobs once we've identified them, and we'll share more details on the status page. If you're noticing particular job failures that are unusual, please reach out to support.
- Supabase status page · Monitoring Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.
- Supabase status page · Resolved Edge function deployments have remained stable. We are closing the incident.
Cite this incident
Site Qwality, “Edge Function Degradation,” Oct 12, 2026, https://siteqwality.com/is-supabase-down/incidents/supabase-202610121949/
Free to quote with a link to this page.