Critical impactResolvedDatabases

Supabase outage: Errors impacting pause, restore, and backup operations in us-east-2 (Ohio)

Supabase reported this critical-impact incident on its official status page on Jun 2, 2026, 13:36 UTC. It was resolved after 1h 5m.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Jun 2, 2026, 13:36 UTC
started
Jun 2, 2026, 14:41 UTC
resolved
1h 5m
duration
Critical
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedJun 2, 2026, 14:41 UTC

    All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.

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 47 incidents in the last 90 days, 17 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history

← Previous: Branch creation degradation (May 21, 2026)Next: Storage users in US-West-2 experiencing increased latency on storage requests (Jun 12, 2026) →
Supabase outage on Jun 2, 2026: Errors impacting pause, restore, and backup operations in us-east-2 (Ohio) · APIStatus.watch