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
8 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 history| Started | Incident | Impact | Duration |
|---|---|---|---|
| Sep 518:39 UTC | Connectivity issues with Vitess databases in GCP | major | 14m |
| Sep 216:34 UTC | Dashboard and API 500 errors for postgres databases | major | 10m |
| Jul 2414:41 UTC | Insights metrics underreporting | major | 3h |
| Jul 2018:29 UTC | Insights metrics underreporting | minor | 20h 49m |
| Jul 1820:32 UTC | Connectivity issues in us-east-1 | major | 33m |
| Jul 1716:41 UTC | API and dashboard errors | major | 28m |
Sources: vendors' own status pages, published postmortems and SEC 8-K Item 1.05 filings, read daily. Times as reported. Logos via logo.dev; trademarks belong to their owners.