outages.live
Live
PlanetScaleIncident ·

Vitess - development branch delays in us-east-1

DegradedOfficial update
0

PlanetScale reports delays when users create Vitess development branches in us-east-1. PlanetScale made a fix and now monitors the result. PlanetScale reports that branch creation times return to normal.

State

Monitoring

Started

Ongoing for

21 min

Worst impact

Degraded

Timeline

2 updates
18:3218:3718:4318:4818:53
DegradedUpdate postedTimes in UTC

Investigating

10 min 46%

Monitoring

12 min 54%

Updates

Times in UTC

As posted by PlanetScale

Monitoring

We’ve made a fix and are seeing branch creation times return to normal.

Investigating

We are seeing issues with Vitess development branches in us-east-1 being delayed on creation. We’re working on a fix.

PlanetScale in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

7

Days with an incident

7

Median duration

47 min

This incident

54% 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.

Resolved

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

The issue has been resolved.

Resolved

PlanetScale·AWS us-east-1 connectivity failures

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

Resolved

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.

Resolved

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.

Resolved

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.live/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.live/feed.xml?providers=planetscale
Slack
/feed subscribe https://outages.live/feed.xml?providers=planetscale

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane