← Back to the carnage
PLANETSCALE
🟡 PlanetScale is investigating database availability issues in their Montreal region. Turns out even Canadian infrastructure needs a coffee break. The good news: it's only partial, so some of your queries are still suffering in real-time. (Auto-resolved: no updates in 24h)
// The official story
database availability issues
// Status page says
Status: Investigating We are currently investigating impact. Affected components northamerica-northeast1 (Montréal) (Partial outage)
🔗 Official status page (for the PR-approved version)
https://www.planetscalestatus.com//incidents/01KHS6R662APJCQY16T9W0Y70ZPlanetscale's Greatest Hits
🟢 PLANETSCALE
3d ago
🟡 One availability zone in us-east-1 decided to go dark, turning replicas into time travelers and connections into fiction. PlanetScale's status page is doing that thing where 'investigating' means engineers are stress-eating at their desks. (Auto-resolved: no updates in 24h)
🟢 PLANETSCALE
Sep 05, 2026
🟡 PlanetScale's Vitess clusters in GCP decided simultaneous ghosting was on brand—Iowa, Montreal, Seoul, and Virginia all taking connectivity timeouts. Investigators report the databases are present but spiritually absent. Schrödinger's data: simultaneously connected and not connected. (Auto-resolved: no updates in 24h)
🟢 PLANETSCALE
Jul 24, 2026
🟠 PlanetScale's Query Insights metrics are ghosting users—reporting fewer queries than actually happened. Your databases are fine, but the telescope measuring them needs glasses. They're deploying fixes now, probably after coffee. (Auto-resolved: no updates in 24h)
🟢 PLANETSCALE
Jul 18, 2026
🟡 PlanetScale's Northern Virginia servers discovered they don't actually need to accept connections. Engineering team now interrogating the infrastructure about its sudden commitment issues. Remediation in progress, which is consultant-speak for 'we're Googling this.'. (Auto-resolved: no updates in 24h)