Status: ResolvedWe've identified an issue with database connectivity for Vitess databases in GCP. We've taken steps to resolve the issue and are making immediate improvements to address root-causes and detection. Databases connectivity is now restored.Affected components us-central1 (Iowa) (Operational) northamerica-northeast1 (Montréal) (Operational) asia-northeast3 (Seoul) (Operational) us-east4…
Status: ResolvedThe incident has been resolved. Between 12:17 and 12:24 UTC, the dashboard and API were returning 500 errors for postgres database management pages and API endpoints.Affected components Dashboard and API Requests (Operational)
Status: ResolvedThe incident has been resolved.Affected components Query Insights (Operational)
Status: ResolvedQuery Insights functionality is restored on all Postgres development branches.Affected components Query Insights (Operational)
Status: ResolvedConnection issues have been resolved. If you experience any further issues, please contact our support team.Affected components us-east-1 (Northern Virginia) (Operational)
Status: ResolvedAPI and dashboard service is restored.Affected components Dashboard and API Requests (Operational)
Status: ResolvedThe issue is resolved. SSO is working fine again.Affected components Dashboard and API Requests (Operational)
Status: ResolvedAll impacted branches are recovered. PlanetScale upgraded development Vitess branches with Vectors enabled from MySQL 8.0.x to 8.4.x. PlanetScale runs an internal fork containing support for PlanetScale's MySQL Vectors indexes. A bug in the 8.4.x version of our Vectors builds resulted in the upgrade immediately failing on startup. Because Vitess development branches only have one i…
Status: ResolvedThe changes we applied are effectively preventing further unexpected restarts to the high availability component shared by Postgres clusters. We have not seen further restarts to this component nor unplanned failovers in Postgres clusters since applying these changes. Affected components us-central1 (Iowa) (Operational)
Status: ResolvedPlanetScale has remediated the issue and it is fully resolved.Affected components Database Operations (Operational)
Status: ResolvedPlanetScale is not observing any database impact resulting from the AWS use1-az4 thermal event. Please contact support if you have any questions or notice any disruption.
Status: ResolvedThe errors have been resolved.Affected components Dashboard and API Requests (Operational)
Status: ResolvedSome percentage of new credential creates, updates, and deletes errored or were very slow for approx 35 minutes.Affected components Dashboard and API Requests (Operational)