A noisy neighbor on the build cluster pushed deploy times from 7s → 24s median. Mitigated by draining the affected pod and rebalancing. No customer data affected.
System status · updated just now
All systems operational.
Static snapshot of runtime health across every region. Figures below reflect the last published check — not live polling.
This page is a curated status snapshot for the marketing site. For live monitoring, use your project console.
Edge runtime
global · 12 regions
99.995%
p50 0.4ms
KV storage
replicated mesh
99.992%
p50 0.5ms
Deploy pipeline
eu‑central‑1
98.41%
elevated latency
Console & API
global
99.998%
p50 42ms
Log ingest
global · 12 regions
99.990%
backlog 0
Billing & metering
eu‑central‑1
100.000%
—
Incident history
INC‑0047
Apr 15, 2026 · 14:22 UTC · 11m
Elevated deploy latency — eu‑central‑1
INC‑0046
Mar 29, 2026 · 03:10 UTC · 4m
KV read timeouts — us‑west‑1
Brief replication lag after a region partition. Read‑your‑writes was preserved for every request — reads from other sessions saw ~60s of eventual consistency during the window.
INC‑0045
Feb 12, 2026 · 22:04 UTC · 18m
Cold‑start regression
A bad router build rolled out globally. Cold starts jumped from 0.6ms → 12ms median. Rolled back automatically once our SLO alarm tripped at minute 2 — the rest was drain time.