PlanetScale Status · History · Incident #3343
RESOLVEDVitess database availability issues in GCP northamerica-northeast1
Major · Started Feb 18, 2026 · 8:23 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
PlanetScale Status · History · Incident #3343
RESOLVEDMajor · Started Feb 18, 2026 · 8:23 PM
Duration
42m
Severity
Major
Detection lead
—
User reports
—
Summary
Started
Feb 18, 2026 · 8:23 PM
Resolved
Feb 18, 2026 · 9:06 PM
Duration
42m
Severity
Major
Event timeline
Investigating
Feb 18 · 8:23 PM PlanetScaleIdentified
Feb 18 · 8:34 PM PlanetScaleMonitoring
Feb 18 · 8:43 PM PlanetScaleResolved
Feb 18 · 9:06 PM PlanetScalePattern
There is an incident in PlanetScale GCP us-central1 region impacting Postgres database availability. We are actively investigating and will update as soon as we have more information.
May 14, 2026 · 32m
View incident →Database operations degraded in eu-west-2
May 13, 2026 · 47m
View incident →AWS use1-az4 thermal event
May 8, 2026 · 16h 59m
View incident →Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT