outages.live
Live
PlanetScaleIncident · 2026-10-09 22:53 UTC

AWS us-east-1 connectivity failures

ResolvedOfficial update

AWS us-east-1 cross-zone networking has fully recovered.

The latest update from PlanetScale.

State

Resolved

Started

22 d ago

2026-10-09 22:53 UTC

Lasted

26 min

until 2026-10-09 23:19 UTC

Worst impact

Partial outage

Timeline

3 updates
22:5322:5923:0623:1223:19
Partial outageUpdate postedTimes in UTC

Investigating

20 min 79%

Monitoring

6 min 21%

Updates

Times in UTC

As posted by PlanetScale

Resolved2026-10-09 23:19 UTC

AWS us-east-1 cross-zone networking has fully recovered.

Monitoring2026-10-09 23:13 UTC

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.

Investigating2026-10-09 22:53 UTC

We are investigating reports of connectivity failures scoped to a single AZ in AWS us-east-1 causing replica delay and connectivity issues.

PlanetScale in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

6

Days with an incident

6

Median duration

47 min

This incident

45% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

2 h 3 min
median 47 min
90 days agoToday

Other PlanetScale incidents

All incidents

PlanetScale·Problems with Vitess connectivity and credential changes

We've observed service restored and successful credential changes across PlanetScale's environments.

Resolvedresolved 5 d ago

PlanetScale·Gap in dashboard metrics for AWS us-east-1

The issue has been resolved.

Resolvedresolved 12 d ago

PlanetScale·Branch creation delays in GCP europe-west-1

We have resolved the branch creation issue and no further impact is expected at this time.

Resolvedresolved 34 d ago

PlanetScale·Connectivity issues with Vitess databases in GCP

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.

Resolvedresolved 57 d ago

PlanetScale·Dashboard and API 500 errors for postgres databases

The incident has been resolved. Between 12:17 and 12:24 UTC, the dashboard and API were returning 500 errors for postgres database management pages and API endpoints.

Resolvedresolved 60 d ago

Follow PlanetScale

Your coding agent knows when PlanetScale is down, and tells you when a failure is theirs, not yours. You can also get PlanetScale incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "planetscale" and tell me if PlanetScale has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=planetscale
Slack
/feed subscribe https://outages.cc/feed.xml?providers=planetscale

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane