PlanetScale outage: us-east-1 connection errors

1. resolvedMar 11, 2026, 14:52 UTC

   This incident has been resolved.

2. monitoringMar 11, 2026, 14:17 UTC

   We're continuing to monitor. We've updated the status history to reflect the time periods where customers experienced connection issues.

3. resolvedMar 11, 2026, 13:19 UTC

   At **12:51 PM UTC** and **1:38 PM UTC** some Vitess databases in us-east-1 were impacted by connection errors for approximately 5 minutes due to an issue in our edge network. We resolved the issue and are no longer seeing errors. We will be taking action to protect customers from this issue happening again in the future and apologize for the error.

4. identifiedMar 11, 2026, 13:04 UTC

   We're investigating an issue with connection errors to Vitess databases in us-east-1.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in PlanetScale's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Snowflake: AWS - Middle East (UAE): INC0152681Critical · Mar 1, 2026, 13:33 UTC
• Grafana Cloud: Complete outage in prod-me-central-1Critical · Mar 2, 2026, 06:43 UTC
• Smartsheet: Brandfolder Monthly Reports DelayedMajor · Feb 27, 2026, 21:55 UTC
• MongoDB Atlas: Impaired Cluster Operations – AWS me-central-1 (United Arab Emirates) and AWS me-south-1 (Bahrain)Major · Mar 1, 2026, 19:30 UTC
• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Mar 2, 2026, 07:19 UTC

How often does PlanetScale have incidents?

PlanetScale reported 9 incidents in the last 90 days, 5 of them major or critical. A typical incident lasted 1h 21m. See PlanetScale's uptime and incident history