← Back to PlanetScale History
minor✓ Resolved

Elevated error rates with Dashboard and API due to AWS us-east-1 outage

PlanetScale•
Status
resolved
Duration
Duration unavailable
Updates
10
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
resolved
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
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
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
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
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
Database creation in AWS us-east-1 is currently disabled.
resolved
Dashboard and API are back fully operational
identified
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
SSO is affected
investigating
We are investigating elevated error rates with Dashboard and API

📊 TECHNICAL DETAILS

Internal ID
3e17f183-2c0a-4b47-a248-ddae6aeeb226
External ID
01K80GK6Z4RJEBDJZSNMTGR3BX
🕐 First reported
🔄 Last Updated
✓ Resolved
MINOR
Impact Level
Duration unavailable
Total Duration
10
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed