PlanetScale reported this minor-impact incident on its official status page on Oct 20, 2025, 09:53 UTC. It has since been resolved.
Right now PlanetScale is operational. Live PlanetScale status →
PlanetScale is continuing to monitor the condition of AWS us-east-1. At this point we do not see any further impact, and have re-enabled database and branch creation in the region.
PlanetScale is continuing to monitor the condition of AWS us-east-1. We have seen networking conditions and compute availability in us-east-1 continue to improve. Out of caution, database and branch creation continues to be disabled in AWS us-east-1.
PlanetScale is continuing to monitor the condition of AWS us-east-1. At this time database and branch creation continues to be disabled, and we are seeing some degraded network performance between components inside of us-east-1 and inbound connectivity into the region.
PlanetScale is continuing to monitor the condition of AWS us-east-1. At this time database and branch creation continues to be disabled, and connectivity may be disrupted into the AWS region.
PlanetScale is seeing degraded network connectivity across AWS us-east-1 components reaching both MySQL and PostgreSQL databases. We are currently monitoring the situation and will continue to update the status page.
Database creation in AWS us-east-1 is currently disabled.
Dashboard and API are back fully operational
There is a [AWS us-east-1 outage](https://health.aws.amazon.com/health/status). Existing databases are unaffected - new databases cannot be created.
SSO is affected
We are investigating elevated error rates with Dashboard and API
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.
Overlapping incidents aren't necessarily related.
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