Minor impactResolvedDatabases

Supabase incident: Storage users in US-West-2 experiencing increased latency on storage requests

Supabase reported this minor-impact incident on its official status page on Jun 12, 2026, 16:00 UTC. It was resolved after 8h 40m.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Jun 12, 2026, 16:00 UTC
started
Jun 13, 2026, 00:40 UTC
resolved
8h 40m
duration
Minor
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedJun 13, 2026, 00:40 UTC

    All residual jobs have drained. Storage performance and job activity is normal.

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: Errors impacting pause, restore, and backup operations in us-east-2 (Ohio) (Jun 2, 2026)Next: Degraded Log Explorer in the dashboard (Jun 16, 2026) →
Supabase incident on Jun 12, 2026: Storage users in US-West-2 experiencing increased latency on storage requests · APIStatus.watch