P
Insights metrics underreporting
Status: ResolvedThe incident has been resolved.Affected components Query Insights (Operational)
P
Insights metrics underreporting
Status: ResolvedQuery Insights functionality is restored on all Postgres development branches.Affected components Query Insights (Operational)
P
Connectivity issues in us-east-1
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)
P
API and dashboard errors
Status: ResolvedAPI and dashboard service is restored.Affected components Dashboard and API Requests (Operational)
P
Single Sign On (SSO) unavailable
Status: ResolvedThe issue is resolved. SSO is working fine again.Affected components Dashboard and API Requests (Operational)
P
Development branches with MySQL Vectors not serving
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…
P
There is an incident in PlanetScale GCP us-central1 region impacting Postgres database availability. We are actively investigating and will update as soon as we have more information.
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)
P
Database operations degraded in eu-west-2
Status: ResolvedPlanetScale has remediated the issue and it is fully resolved.Affected components Database Operations (Operational)
P
AWS use1-az4 thermal event
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.
P
Errors with database webhooks
Status: ResolvedThe errors have been resolved.Affected components Dashboard and API Requests (Operational)
P
Currently experiencing issues with creating/updating/deleting Vitess credentials
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)