Supabase incident
Intermittent errors on Supavisor Shared Pooler in us-east-2
Resolved after 29 min.
- Started
- Ended
- Worst state
- Degraded
- On Supabase’s status page
- Source
- Components
- us-east-2
Timeline
- Supabase status page · Reported Intermittent errors on Supavisor Shared Pooler in us-east-2
- Supabase status page · Monitoring Between 2026-11-04 00:02 and 00:50 UTC there were elevated errors on Supavisor Shared Pooler in the us-east-2 region. Errors have subsided and things are back to normal. Example errors were ClientHandler: (ECHECKOUTFAILED) checkout failed due to %{"C" => "08006", "M" => "Failed to connect to database: {:error, :timeout} DbHandler: Connection failed {:error, :timeout} to ~c".......us-east-2.compute.internal"
- Site Qwality checks · Degraded Official status: Intermittent errors on Supavisor Shared Pooler in us-east-2
- Supabase status page · Resolved Errors have subsided and connections are back to normal.
- Site Qwality checks · Operational Checks clean again
Cite this incident
Site Qwality, “Intermittent errors on Supavisor Shared Pooler in us-east-2,” Nov 4, 2026, https://siteqwality.com/is-supabase-down/incidents/supabase-202611040349/
Free to quote with a link to this page.