Elevated error rates with Dashboard and API due to AWS us-east-1 outage
Oct 20, 07:25 UTCOct 20, 09:36 UTC
Duration
2h 11m
Impact
Minor
Root cause
Not disclosed
PlanetScale, 90 days
6 incidents
Affected
Not listed by the vendor.
Final update
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.
Timeline
- Resolved · Oct 20, 20:48 UTC
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.
- Monitoring · Oct 20, 20:08 UTC
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.
- Monitoring · Oct 20, 18:56 UTC
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.
- Monitoring · Oct 20, 17:39 UTC
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.
- Monitoring · Oct 20, 17:06 UTC
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.
- Monitoring · Oct 20, 15:59 UTC
Database creation in AWS us-east-1 is currently disabled.
- Resolved · Oct 20, 09:36 UTC
Dashboard and API are back fully operational
- Identified · Oct 20, 07:36 UTC
There is a [AWS us-east-1 outage](https://health.aws.amazon.com/health/status). Existing databases are unaffected - new databases cannot be created.
- Investigating · Oct 20, 07:27 UTC
SSO is affected
- Investigating · Oct 20, 07:25 UTC
We are investigating elevated error rates with Dashboard and API
More from PlanetScale
Full historyProblems with Vitess connectivity and credential changeslasted 1h 38mGap in dashboard metrics for AWS us-east-1lasted 1h 8mAWS us-east-1 connectivity failureslasted 26mBranch creation delays in GCP europe-west-1lasted 2h 3mConnectivity issues with Vitess databases in GCPlasted 14mDashboard and API 500 errors for postgres databaseslasted 10m