Live / Supabase / Incident
Supabase: Edge Function Degradation
Supabase · supabase.comMinor incidentResolved2026-10-13 18:24 UTC
Public — what happened
Summary
Supabase reported a minor incident starting at 19:49 UTC on 2026-10-12 in which its Edge Functions slowed down considerably, with deploying functions and fetching function code hit hardest. The company said it had found the underlying cause from the start but did not describe it, and error rates had dropped by 20:23 UTC, with deployments back to normal by 21:07 UTC. Supabase then said it was checking for background jobs that failed during the problem, possibly including backups, so it could run them again, and it asked customers who saw unusual job failures to contact support. After a period of monitoring that began at 02:24 UTC on 2026-10-13, the incident was marked resolved at 18:24 that day.
Timeline
- Started — 2026-10-12 19:49 UTC
- Identified — 2026-10-12 19:49 UTC (3 updates)
- Monitoring — 2026-10-13 02:24 UTC
- Resolved — 2026-10-13 18:24 UTC · 22h 36m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Supabase against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Supabase: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Supabase report →
More from Supabase
Covered in The Squid’s Ink, Week 43, 2026, our weekly internet health report.