← Back to the carnage
PLANETSCALE

🟡 PlanetScale's identity verification decided to ghost everyone trying to log in. Your databases still work fine, but good luck proving you own them. The irony of a database company losing track of who people are is *chef's kiss*. (Auto-resolved: no updates in 24h)

⏰ Jul 16, 2026 Fixed (for now) spotted via status_rss

// The official story

Single Sign On (SSO) unavailable

// Status page says

Status: Investigating SSO login to the PlanetScale website and API is unavailable. We are investigating. Database operations are unaffected. Affected components Dashboard and API Requests (Degraded performance)

🔗 Official status page (for the PR-approved version)

https://www.planetscalestatus.com//incidents/01KXN4794175X3A72R9SSG3Q8Q

Planetscale'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)