some databases stuck in reparenting
Oct 15, 18:29 UTCOct 16, 01:52 UTC
Duration
7h 23m
Impact
Major
Root cause
Not disclosed
PlanetScale, 90 days
6 incidents
Affected
Not listed by the vendor.
Final update
No further disruption is expected, please contact support with any further issues.
Timeline
- Resolved · Oct 16, 01:52 UTC
No further disruption is expected, please contact support with any further issues.
- Monitoring · Oct 15, 20:31 UTC
All databases have recovered, but we are continuing to watch the situation closely.
- Monitoring · Oct 15, 19:44 UTC
We are continuing to investigate
- Monitoring · Oct 15, 19:30 UTC
PlanetScale experienced the failure of VMs across multiple availability zones, causing a small number of branches to need rescheduling before recovery was possible. We expect all branches in this state have recovered, and we are continuing to monitor for further failures.
- Identified · Oct 15, 18:45 UTC
We are continuing to investigate and recover.
- Identified · Oct 15, 18:29 UTC
A small number of databases in GCP us-central1 are stuck with "primary is not serving, there may be a reparent operation in progress".
More from PlanetScale
Full historyProblems with Vitess connectivity and credential changeslasted 1h 38mGap in dashboard metrics for AWS us-east-1lasted 1h 8mAWS us-east-1 connectivity failureslasted 26mBranch creation delays in GCP europe-west-1lasted 2h 3mConnectivity issues with Vitess databases in GCPlasted 14mDashboard and API 500 errors for postgres databaseslasted 10m