Live / Supabase / Incident
Supabase: Interruption in connections to Supavisor in eu-west-2
Supabase · supabase.comResolved2026-11-08 12:35 UTC
Public — what happened
Summary
Supabase said it detected a brief interruption affecting connections to Supavisor, its connection pooling service, in the eu-west-2 region. The company reported the problem lasted from 09:42 to 09:52 GMT and may have affected connections for some users. In its first update at 10:53 UTC, Supabase said the issue had been resolved and that it was monitoring to confirm systems had fully recovered. The incident was marked resolved at 12:35, and no cause was given in the text provided.
Timeline
- Started — 2026-11-08 10:53 UTC
- Monitoring — 2026-11-08 10:53 UTC
- Resolved — 2026-11-08 12:35 UTC · 1h 42m 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 46, 2026, our weekly internet health report.