System status
Everything is running
Component health for the delivery path, the control plane and the log pipeline. Probes run from nine independent networks.
99.938%
30-day availability
235
monitored components
5
incidents this quarter
6min
median time to mitigate
Components
Component healthall systems operational
Edge delivery (global anycast)operational
60 days ago99.942% uptimetoday
Shield tieroperational
60 days ago99.908% uptimetoday
Control plane APIoperational
60 days ago99.969% uptimetoday
Purge pipelineoperational
60 days ago99.978% uptimetoday
Real-time log deliveryoperational
60 days ago99.954% uptimetoday
Certificate issuanceoperational
60 days ago99.914% uptimetoday
Incident history
Every incident since the platform launched, including the ones customers never noticed.
Partial transit degradation via one carrier
resolved21 Jul 2026 · impact: no data loss
14:52 UTC
Root cause identified: a faulty line card on one of two upstream ports. Traffic was drained from the affected device.
14:21 UTC
We are investigating elevated p99 latency reported by monitoring in a single facility.
15:40 UTC
The device was replaced and traffic re-balanced. Metrics are back to baseline; we are keeping the incident open for another hour to confirm.
Scheduled maintenance — storage rebalance
resolved11 May 2026 · impact: none
02:00 UTC
Maintenance window opened. Requests were served by the standby control plane throughout.
03:12 UTC
Upgrade completed with no customer-visible impact.
About this page
Synthetic probes run from nine independent networks on three continents. A component counts as down when at least three probes on different networks fail two consecutive checks.
Anything that degrades a customer-visible SLO: availability, error rate, or the latency budget for the affected component.
Yes — the status API returns the same data as JSON, and every component exposes a Prometheus-compatible metrics endpoint.