outages.live
Live
PlanetScaleIncident · 2026-10-20 19:38 UTC

Gap in dashboard metrics for AWS us-east-1

ResolvedOfficial update

The issue has been resolved.

The latest update from PlanetScale.

State

Resolved

Started

12 d ago

2026-10-20 19:38 UTC

Lasted

1 h 8 min

until 2026-10-20 20:46 UTC

Worst impact

Notice

Timeline

2 updates
19:3819:5520:1220:2920:46
NoticeUpdate postedTimes in UTC

Monitoring

1 h 8 min 100%

Updates

Times in UTC

As posted by PlanetScale

Resolved2026-10-20 20:46 UTC

The issue has been resolved.

Monitoring2026-10-20 19:38 UTC

From 19:20 - 19:30 UTC we had a delay with metrics in AWS us-east-1. For databases in this region you may see missing metrics in the dashboard. We've made a fix and are seeing metrics recover.

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

1.4× 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·AWS us-east-1 connectivity failures

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

Resolvedresolved 22 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 33 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