Minor impactResolvedDatabases

Supabase incident: Increased rates of Pooler connection timeouts in us-east-1

Supabase reported this minor-impact incident on its official status page on Aug 24, 2026, 15:26 UTC. It was resolved after 1h 12m.

Right now Supabase is operational. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Aug 24, 2026, 15:26 UTC
started
Aug 24, 2026, 16:38 UTC
resolved
1h 12m
duration
Minor
impact
  1. resolvedAug 24, 2026, 16:38 UTC

    This incident has been resolved.

  2. monitoringAug 24, 2026, 15:38 UTC

    We have identified a degraded Supavisor node and we have rolled out a fix. We are monitoring to ensure continued stability. Confirmed Impact: On Aug 24, 2026 between 14:30 and 15:20 UTC we observed increased rates of connection timeouts connecting to Supavisor in us-east-1 due to a degraded node.

  3. investigatingAug 24, 2026, 15:26 UTC

    We are aware of reports of increased rates of connection timeouts for users connecting to Projects in us-east-1 via Supavisor.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

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