outages.live
Live

PlanetScale

PlanetScale is operational

Checked 2 min ago Operational

History

90 days agoToday

Incidents in 90 days

6

Days with an incident

6

Median duration

47 min

Longest incident

2 h 3 min

Components

25
us-east-1 (Northern Virginia) Operational
90 days agoNo incidentsToday
us-east-2 (Ohio) Operational
90 days agoNo incidentsToday
us-west-2 (Oregon) Operational
90 days agoNo incidentsToday
ap-northeast-1 (Tokyo) Operational
90 days agoNo incidentsToday
ap-south-1 (Mumbai) Operational
90 days agoNo incidentsToday
ap-southeast-1 (Singapore) Operational
90 days agoNo incidentsToday
ap-southeast-2 (Sydney) Operational
90 days agoNo incidentsToday
ca-central-1 (Montreal) Operational
90 days agoNo incidentsToday
eu-central-1 (Frankfurt) Operational
90 days agoNo incidentsToday
eu-west-1 (Dublin) Operational
90 days agoNo incidentsToday
eu-west-2 (London) Operational
90 days agoNo incidentsToday
sa-east-1 (Sao Paulo) Operational
90 days agoNo incidentsToday
us-central1 (Iowa) Operational
90 days agoNo incidentsToday
us-east1 (Moncks Corner) Operational
90 days agoNo incidentsToday
us-east4 (Northern Virginia) Operational
90 days agoNo incidentsToday
asia-northeast3 (Seoul) Operational
90 days agoNo incidentsToday
northamerica-northeast1 (Montréal) Operational
90 days agoNo incidentsToday
europe-west1 (St. Ghislain) Operational
90 days agoNo incidentsToday
europe-west4 (Eemshaven) Operational
90 days agoNo incidentsToday
centralus (Iowa) Operational
90 days agoNo incidentsToday
eastus2 (Virginia) Operational
90 days agoNo incidentsToday
westeurope (Netherlands) Operational
90 days agoNo incidentsToday
us-east-1 (Northern Virginia) Operational
90 days agoNo incidentsToday
us-east-2 (Ohio) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 26, 2026

Duration1 h 38 min21:53 to 23:31Problems with Vitess connectivity and credential changesPartial outage

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

Oct 20, 2026

Duration1 h 8 min19:38 to 20:46Gap in dashboard metrics for AWS us-east-1Notice

The issue has been resolved.

Oct 9, 2026

Duration26 min22:53 to 23:19AWS us-east-1 connectivity failuresPartial outage

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

Sep 28, 2026

Duration2 h 3 min18:59 to 21:02Branch creation delays in GCP europe-west-1Degraded

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

Sep 5, 2026

Duration14 min18:39 to 18:53Connectivity issues with Vitess databases in GCPPartial outage

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.

Sep 2, 2026

Duration10 min16:34 to 16:44Dashboard and API 500 errors for postgres databasesPartial outage

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.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane