Supabase incident
High connection latency via shared Pooler in us-west-1
Resolved after 1 hour 54 minutes, affecting Connection Pooler, on February 9, 2026.
The team noticed that some connection pools had workers stuck as a consequence of the previous issue. This could cause query failures. Stuck workers were now restarted.
Affected components
Update timeline
- investigating Feb 09, 2026, 05:39 PM UTC
We’re investigating high latency in us-west-1 affecting some connections to databases via our shared connection pooler.
- monitoring Feb 09, 2026, 05:56 PM UTC
We've removed the problematic cluster node and latency returned to the normal level. We are now monitoring.
- monitoring Feb 09, 2026, 06:37 PM UTC
The team noticed that some connection pools had workers stuck as a consequence of the previous issue. This could cause query failures. Stuck workers were now restarted.
- resolved Feb 09, 2026, 07:34 PM UTC
This incident has been resolved.
Your product runs on more than Supabase
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services