Vitess database availability issues in GCP northamerica-northeast1
Feb 18, 20:23 UTCFeb 18, 21:06 UTC
Duration
43m
Impact
Major
Root cause
Not disclosed
PlanetScale, 90 days
8 incidents
Affected
Not listed by the vendor.
Final update
Problem has been resolved. We saw three nodes fail across three availability zones simultaneously. Impacting databases hosted on those nodes. All databases have been moved to healthy nodes and we're investigating how we can further reduce impact from similar events in the future.
Timeline
- Resolved · Feb 18, 21:06 UTC
Problem has been resolved. We saw three nodes fail across three availability zones simultaneously. Impacting databases hosted on those nodes. All databases have been moved to healthy nodes and we're investigating how we can further reduce impact from similar events in the future.
- Monitoring · Feb 18, 20:43 UTC
Impacted databases are recovering, we're continuing to monitor.
- Identified · Feb 18, 20:34 UTC
We're working on a fix for the impacted databases.
- Investigating · Feb 18, 20:23 UTC
We are currently investigating impact.
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 |
From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.