Supabase outage, 21 October 2026
Intermittent connection errors via the connection pooler in us-east-1
- Started
- Resolved
- 10 Oct 2026, 02:10 UTC - reported afterwards
- Impact
- Not stated
Is this still happening?
No. Supabase marked this incident resolved.
Right now: Supabase reports degraded performance on some systems. (as of 26 Oct, 03:47 UTC) Live Supabase status
Last update from Supabase
Between 22:10 and 22:51 UTC on October 9, 2026, about 1% of new database connections made through the Shared Pooler (Supavisor) in us-east-1 failed with "Failed to connect to database" timeout errors. The cause of the failures was an incident at our cloud provider which affected network traffic between availability zones. Supabase Project databases were not affected, and connections that had already been open prior to the incident remained open. The issue was resolved at 22:51 UTC. Clients that retried on connection errors would have reconnected successfully.
Similar Supabase incidents
Earlier incidents with the same affected part or wording - useful to see how long this kind of problem usually takes.