Minor incident
Supabase: Intermittent errors on Supavisor Shared Pooler in us-east-2
Nov 4, 2026, 03:48 UTC
started
04:17 UTC
resolved
29 min
duration
Current status of Supabase: Operational — live Supabase status
Timeline
- Nov 4, 2026, 03:48 UTCmonitoringBetween 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" ```
- Nov 4, 2026, 04:17 UTCresolvedErrors have subsided and connections are back to normal.
Updates as published by Supabase.
Other services with incidents at the same time
This was part of a wider event: 119 services reported incidents within the hour.
- Heap 04:30 UTC · Delayed event-data availability in the US
- Instructure 04:21 UTC · Portfolium is unavailable in the Sydney region
- Hostinger 04:05 UTC · Degraded Server web2209 Performance
- Hostinger 03:57 UTC · Degraded Server web1377 Performance
- Moonshot AI 03:52 UTC · Kimi Code K3 TTFT 响应延迟升高
- Hostinger 03:40 UTC · Degraded Server web1394 Performance
- Hostinger 03:27 UTC · Emergency Server web794 Maintenance
- Hostinger 03:13 UTC · Degraded Server web2108 Performance
- Grafana Cloud 03:02 UTC · GitHub returning 403 for all Git Sync repositories
More Supabase incidents
- November 5, 2026 Intermittent 502/503 errors for pg_net calls to Edge Functions
- November 4, 2026 Storage issues in us-east-1 and eu-central-1
- November 3, 2026 Management API Postgres config updates overwriting previous updates
- November 2, 2026 Storage uploads failing in us-east-1
- October 31, 2026 PG15 -> PG17 Upgrade Failures
- October 30, 2026 Logs degraded in multiple regions