Where does this status come from?

From PlanetScale's own status page API at https://www.planetscalestatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are PlanetScale's words.

How can my agent or app check PlanetScale status?

Fetch https://upbutler.com/status/planetscale/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"planetscale"}, on https://upbutler.com/mcp/public.

Is PlanetScale down?

Right now

No. PlanetScale is operational.

No incidents reported.

Read from www.planetscalestatus.com 2 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/planetscale/status.agent.json

MCP: upstream_status {"service":"planetscale"}

Managed MySQL (Vitess) and Postgres.

What PlanetScale reports

Operational

Taken as is from PlanetScale's own status page API. Incident titles and component names below are theirs.

Open www.planetscalestatus.com

UpButler's independent probe

There is no keyless endpoint of PlanetScale that says anything useful, so UpButler does not probe it. To check your own PlanetScale account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

PlanetScale components

25 operational

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

PlanetScale incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10, 1 of them rated major or critical by PlanetScale.

Started (UTC)	Incident	Impact	Lasted
2026-10-09 22:53	AWS us-east-1 connectivity failures	major	26 min
2026-09-28 18:59	Branch creation delays in GCP europe-west-1	minor	2 h 3 min

Tell your outage from PlanetScale's

Declare that your project depends on PlanetScale. When one of your monitors fails while PlanetScale has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - planetscale

Ask before you retry

curl -s https://upbutler.com/status/planetscale/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "planetscale",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is PlanetScale down right now?: No. As of 2026-10-10 05:09 UTC, PlanetScale is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From PlanetScale's own status page API at https://www.planetscalestatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are PlanetScale's words.
How can my agent or app check PlanetScale status?: Fetch https://upbutler.com/status/planetscale/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"planetscale"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or PlanetScale's?: Add "planetscale" to the dependencies of your UpButler workspace. When one of your monitors fails while PlanetScale has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in databases and data

UpButler is not affiliated with PlanetScale. Status and incident text belong to PlanetScale and are read from their public status source; the probe result is UpButler's own measurement.