Minor impactResolvedDatabases

Supabase incident: Project create and unpause errors in eu-west-1

Supabase reported this minor-impact incident on its official status page on Jun 23, 2026, 15:16 UTC. It was resolved after 1h 16m.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Jun 23, 2026, 15:16 UTC
started
Jun 23, 2026, 16:32 UTC
resolved
1h 16m
duration
Minor
impact

Timeline

updates from Supabase's status page ↗
  1. resolvedJun 23, 2026, 16:32 UTC

    Project create and unpause operations have returned to normal and remained stable for the past 30 minutes.

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: Increased latency for Management API requests (Jun 23, 2026)Next: Degraded performance of the Shared Pooler cluster in ap-southeast-1 (Jun 24, 2026) →
Supabase incident on Jun 23, 2026: Project create and unpause errors in eu-west-1 · APIStatus.watch