Date: 2025-06-12
Service Impacted: Supabase Platform (Multiple Services)
Affected Region(s): Global
Duration: ~2 hours 25 minutes (18:05–20:30 UTC)
Between 18:05 UTC and 20:30 UTC on June 12, 2025, Supabase services experienced widespread degradation caused by an outage in our upstream provider’s infrastructure. The outage impacted the majority of HTTP and Websocket traffic to Supabase APIs globally.
Direct Postgres and connection pooler access remained unaffected.
All Supabase users interacting with the platform or projects via HTTP or WebSocket, including:
Supabase relies on the upstream provider for proxying, DNS and routing across our platform services and user projects. On June 12, a bug in their Cloud Provider’s infrastructure caused Workers KV storage to fail cascading across their systems.
This caused Supabase’s API Gateway to stop responding, leading to major service degradation as it is an entry point for the vast majority of HTTP and WebSocket traffic.
Incident timeline (UTC):
Supabase services affected due to heavy reliance on upstream provider:
No action required. This incident was caused by upstream infrastructure failure. All services have returned to normal.
This was a serious outage that significantly impacted Supabase customers. While the root cause lay with our upstream provider, our own dependencies and architecture contributed to the extent of the disruption. We’ve identified concrete steps to mitigate future incidents, including reducing dependency on single infrastructure points and improving our internal and external communication during outages.
We’re grateful for the patience and understanding of our community and remain committed to building a more resilient and transparent platform.