Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Vitess branch creation unavailable

Reported by PlanetScale · Databases · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Feb 24, 2026, 10:26 UTC
Vendor's clock
Resolved
Feb 24, 2026, 12:00 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
1 h 34 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • PlanetScale reports partial outage: "Vitess branch creation unavailable".[E1, E2]
  • The vendor marked it resolved at 2026-02-24 12:00 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-02-24 12:00 UTC · summary s1, evidence af5e72574a6f5ada

Evidence (7)
  1. E1PlanetScale reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Vitess branch creation unavailable". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-02-24 10:26 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-02-24 12:00 UTC. (vendor)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

PlanetScale is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Feb 24, 2026, 10:26 UTCVendor-reported startVendor time
  2. Feb 24, 2026, 12:00 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.