Live / Supabase / Incident
Supabase: Intermittent latency in Eastern US
Supabase · supabase.comMinor incidentResolved2026-10-06 12:15 UTC
Public — what happened
Summary
Supabase said that starting on 2026-09-29 at 16:26 UTC, clients connecting from the eastern United States, including servers and serverless functions there, saw intermittent slowdowns, especially around the top and half of each hour during Eastern business hours, no matter where their project was hosted. The company linked the problem to bursty traffic at one specific network point of presence and worked with its networking partners, who applied a mitigation on October 1 that Supabase said brought significant improvement, though some users still reported slowness at peak times. Supabase said a fix was in place by October 5 and affected projects had recovered, and it marked the incident resolved on 2026-10-06 at 12:15.
Affected
API Gateway
Timeline
- Started — 2026-09-29 16:26 UTC
- Identified — 2026-09-29 16:26 UTC (8 updates)
- Monitoring — 2026-10-05 18:45 UTC
- Resolved — 2026-10-06 12:15 UTC · 7 days 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 41, 2026, our weekly internet health report.