Project Lifecycle Issues in ap-northeast-1
Nov 11, 16:44 UTCNov 11, 21:32 UTC
Duration
4h 48m
Impact
Minor
Root cause
Not disclosed
Supabase, 90 days
56 incidents
Affected
Not listed by the vendor.
Final update
All operations have returned to normal and have remained stable.
Timeline
- Resolved · Nov 11, 21:32 UTC
All operations have returned to normal and have remained stable.
- Monitoring · Nov 11, 18:39 UTC
We are seeing recovery of project operations. We will continue to monitor to ensure all project lifecycle functions stabilize.
- Identified · Nov 11, 18:14 UTC
Our upstream provider is reporting improvements to project lifecycle actions. We are internally validating the recovery of our systems. We will re-enable functionality after we have confirmed recovery.
- Identified · Nov 11, 17:05 UTC
The issue has been identified by our upstream provider and is being addressed.
- Investigating · Nov 11, 16:44 UTC
Project lifecycle operations have been impacted by an issue in ap-northeast-1. We are investigating along with our upstream provider.
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