Incidentsby GlyphVitess 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
6 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 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