Skip to content

Outage tracker

PlanetScale: incident history

The last 24 hours in detail, PlanetScale's declared incident record, and our regional check results beside it.

← Back to PlanetScale's check readings

We started checking PlanetScale on November 2, 2026, which is 6 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me when PlanetScale reports an incident on its status page, and again when it reports it resolved.

One email when it is reported and one when it is resolved, after you confirm the address. No account, no card.

This is PlanetScale's own statement from its status page, with our regional reading beside it.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what PlanetScale's own status page declared. Below it, any public chatter we saw about PlanetScale and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what PlanetScale's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about PlanetScale in the last 24 hours, which is not evidence that nothing is wrong.
PlanetScale's status pageNo incident declared in the last 24 hours.

Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is PlanetScale's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention PlanetScale next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East0.00%582
US-West0.00%449
Europe0.00%407
Asia-Pacific0.00%247

Their declared record

PlanetScale's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.

Problems with Vitess connectivity and credential changesPartial outage
Oct 26, 2026, 9:53 PM UTC to Oct 26, 2026, 11:31 PM UTC (1h 38m)resolved
their latest update (Oct 26, 2026, 11:31 PM UTC): We've observed service restored and successful credential changes across PlanetScale's environments.
Gap in dashboard metrics for AWS us-east-1All systems operational
Oct 20, 2026, 7:38 PM UTC to Oct 20, 2026, 8:46 PM UTC (1h 8m)resolved
their latest update (Oct 20, 2026, 8:46 PM UTC): The issue has been resolved.
AWS us-east-1 connectivity failuresPartial outage
Oct 9, 2026, 10:53 PM UTC to Oct 9, 2026, 11:19 PM UTC (26 min)resolved
their latest update (Oct 9, 2026, 11:19 PM UTC): AWS us-east-1 cross-zone networking has fully recovered.
Branch creation delays in GCP europe-west-1Minor incident
Sep 28, 2026, 6:59 PM UTC to Sep 28, 2026, 9:02 PM UTC (2h 3m)resolved
their latest update (Sep 28, 2026, 9:02 PM UTC): We have resolved the branch creation issue and no further impact is expected at this time.
Connectivity issues with Vitess databases in GCPPartial outage
Sep 5, 2026, 6:39 PM UTC to Sep 5, 2026, 6:53 PM UTC (14 min)resolved
their latest update (Sep 5, 2026, 6:53 PM UTC): 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.
Dashboard and API 500 errors for postgres databasesPartial outage
Sep 2, 2026, 4:34 PM UTC to Sep 2, 2026, 4:44 PM UTC (10 min)resolved
their latest update (Sep 2, 2026, 4:44 PM UTC): 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.
Insights metrics underreportingPartial outage
Jul 24, 2026, 2:41 PM UTC to Jul 24, 2026, 5:42 PM UTC (3h)resolved
their latest update (Jul 24, 2026, 5:42 PM UTC): The incident has been resolved.
Insights metrics underreportingMinor incident
Jul 20, 2026, 6:29 PM UTC to Jul 21, 2026, 3:18 PM UTC (20h 49m)resolved
their latest update (Jul 21, 2026, 3:18 PM UTC): Query Insights functionality is restored on all Postgres development branches.
Connectivity issues in us-east-1Partial outage
Jul 18, 2026, 8:32 PM UTC to Jul 18, 2026, 9:05 PM UTC (33 min)resolved
their latest update (Jul 18, 2026, 9:05 PM UTC): Connection issues have been resolved. If you experience any further issues, please contact our support team.
API and dashboard errorsPartial outage
Jul 17, 2026, 4:41 PM UTC to Jul 17, 2026, 5:09 PM UTC (28 min)resolved
their latest update (Jul 17, 2026, 5:09 PM UTC): API and dashboard service is restored.

Showing the 10 most recent of 25 incidents PlanetScale has declared in the history we hold.

These entries are PlanetScale's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.

PlanetScale's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.

Full detail on what a probe does and does not prove is in the methodology page.