Project Lifecycle Issues in eu-west-1
Sep 24, 15:36 UTCSep 24, 17:38 UTC
Duration
2h 2m
Impact
Major
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
DatabaseManagement APIeu-west-1Compute capacity - eu-west-1
Final update
This incident has been resolved.
Timeline
- Resolved · Sep 24, 17:38 UTC
This incident has been resolved.
- Monitoring · Sep 24, 17:12 UTC
We are continuing to monitor to ensure ongoing stability.
- Identified · Sep 24, 17:03 UTC
The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability.
- Identified · Sep 24, 16:56 UTC
Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon. This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available.
- Identified · Sep 24, 16:23 UTC
All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible.
- Identified · Sep 24, 15:50 UTC
We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.
- Investigating · Sep 24, 15:36 UTC
We are investigating project lifecycle operation issues in eu-west-1.
More from Supabase
Full historyInterruption in connections to Supavisor in eu-west-2lasted 1h 42mIncreased Errors with Project Lifecycle Operations in US-West-2lasted 2h 28mIntermittent 502/503 errors for pg_net calls to Edge Functionslasted 42mStorage issues in us-east-1 and eu-central-1lasted 16h 18mIntermittent errors on Supavisor Shared Pooler in us-east-2lasted 29mManagement API Postgres config updates overwriting previous updateslasted 2h 8m