Minor impactResolvedDatabases

Supabase incident: Intermittent errors on Supavisor Shared Pooler in us-east-2

Supabase reported this minor-impact incident on its official status page on Nov 4, 2026, 03:48 UTC. It was resolved after 29 min.

Right now Supabase is operational. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Nov 4, 2026, 03:48 UTC
started
Nov 4, 2026, 04:17 UTC
resolved
29 min
duration
Minor
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedNov 4, 2026, 04:17 UTC

    Errors have subsided and connections are back to normal.

  2. monitoringNov 4, 2026, 03:48 UTC

    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" ```

What APIStatus.watch saw

  • Nov 4, 2026, 03:49 UTCoperational → degraded
  • Nov 4, 2026, 04:19 UTCdegraded → operational

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Supabase have incidents?

Supabase reported 59 incidents in the last 90 days, 22 of them major or critical. A typical incident lasted 2h. See Supabase's uptime and incident history

← Previous: Storage uploads failing in us-east-1 (Nov 2, 2026)Next: Storage issues in us-east-1 and eu-central-1 (Nov 4, 2026) →