Is PlanetScale down?

Status: Investigating We are investigating internal and external reports of Vitess database connectivity problems for certain branches and long delays in credential changes (including creating new users/passwords) propagating into Vitess databases. Affected components eu-west-1 (Dublin) (Degraded performance) us-central1 (Iowa) (Degraded performance) us-east-1 (Northern Virginia) (Degraded performance) us-west-2 (Oregon) (Degraded performance) asia-northeast3 (Seoul) (Degraded performance) us-east-2 (Ohio) (Degraded performance) europe-west1 (St. Ghislain) (Degraded performance) europe-west4 (Eemshaven) (Degraded performance) ap-south-1 (Mumbai) (Degraded performance) sa-east-1 (Sao Paulo) (Degraded performance) ap-southeast-2 (Sydney) (Degraded performance) us-east4 (Northern Virginia) (Degraded performance) ca-central-1 (Montreal) (Degraded performance) eu-west-2 (London) (Degraded performance) ap-northeast-1 (Tokyo) (Degraded performance) eu-central-1 (Frankfurt) (Degraded performance) northamerica-northeast1 (Montréal) (Degraded performance) us-east1 (Moncks Corner) (Degraded performance) ap-southeast-1 (Singapore) (Degraded performance)

Status: Monitoring We've identified the resource exhaustion in credential distribution and are monitoring the restoration of service. Affected components ap-south-1 (Mumbai) (Degraded performance) eu-central-1 (Frankfurt) (Degraded performance) us-east-1 (Northern Virginia) (Degraded performance) us-central1 (Iowa) (Degraded performance) europe-west4 (Eemshaven) (Degraded performance) ap-southeast-1 (Singapore) (Degraded performance) eu-west-1 (Dublin) (Degraded performance) asia-northeast3 (Seoul) (Degraded performance) us-east-2 (Ohio) (Degraded performance) us-east1 (Moncks Corner) (Degraded performance) eu-west-2 (London) (Degraded performance) ap-northeast-1 (Tokyo) (Degraded performance) ap-southeast-2 (Sydney) (Degraded performance) us-west-2 (Oregon) (Degraded performance) northamerica-northeast1 (Montréal) (Degraded performance) sa-east-1 (Sao Paulo) (Degraded performance) us-east4 (Northern Virginia) (Degraded performance) ca-central-1 (Montreal) (Degraded performance) europe-west1 (St. Ghislain) (Degraded performance)

Status: Resolved We've observed service restored and successful credential changes across PlanetScale's environments. Affected components eu-central-1 (Frankfurt) (Operational) northamerica-northeast1 (Montréal) (Operational) ap-northeast-1 (Tokyo) (Operational) us-east-2 (Ohio) (Operational) us-east1 (Moncks Corner) (Operational) europe-west4 (Eemshaven) (Operational) ap-southeast-2 (Sydney) (Operational) eu-west-1 (Dublin) (Operational) us-east-1 (Northern Virginia) (Operational) us-central1 (Iowa) (Operational) asia-northeast3 (Seoul) (Operational) eu-west-2 (London) (Operational) sa-east-1 (Sao Paulo) (Operational) ap-southeast-1 (Singapore) (Operational) us-west-2 (Oregon) (Operational) ca-central-1 (Montreal) (Operational) europe-west1 (St. Ghislain) (Operational) us-east4 (Northern Virginia) (Operational) ap-south-1 (Mumbai) (Operational)

Status: Monitoring From 19:20 - 19:30 UTC we had a delay with metrics in AWS us-east-1. For databases in this region you may see missing metrics in the dashboard. We've made a fix and are seeing metrics recover.

Status: Resolved The issue has been resolved.

Status: Investigating We are investigating reports of connectivity failures scoped to a single AZ in AWS us-east-1 causing replica delay and connectivity issues. Affected components us-east-1 (Northern Virginia) (Partial outage)

Status: Monitoring A small number of database branches in AWS us-east-1 were impacted by cross-zone networking issues, for which the impact window has ended. If you continue to see impact, please reach out to PlanetScale support. Affected components us-east-1 (Northern Virginia) (Partial outage) us-east-1 (Northern Virginia) (Partial outage)

Status: Resolved AWS us-east-1 cross-zone networking has fully recovered. Affected components us-east-1 (Northern Virginia) (Operational) us-east-1 (Northern Virginia) (Operational)

Status: Investigating We have identified an issue and are investigating branch creation delays in GCP europe-west-1.

Status: Identified We have identified a problem relating to scheduling of database branches and are rolling out a mitigation.

Status: Resolved We have resolved the branch creation issue and no further impact is expected at this time. Please contact PlanetScale support if any of your branch operations are experiencing delays in GCP europe-west-1.

Status: Investigating We're currently experiencing issues with connectivity to Vitess databases in GCP. We're investigating the issue. Affected components us-east4 (Northern Virginia) (Partial outage) us-central1 (Iowa) (Partial outage) northamerica-northeast1 (Montréal) (Partial outage) asia-northeast3 (Seoul) (Partial outage)

Status: Monitoring We've identified an issue in our networking and deployed mitigation. Connectivity is back to normal. We're continuing to monitor. Affected components us-central1 (Iowa) (Partial outage) northamerica-northeast1 (Montréal) (Partial outage) asia-northeast3 (Seoul) (Partial outage) us-east4 (Northern Virginia) (Partial outage)

Status: Resolved We'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-east4 (Northern Virginia) (Operational) us-central1 (Iowa) (Operational) northamerica-northeast1 (Montréal) (Operational) asia-northeast3 (Seoul) (Operational)