System status
Everything is running
Playback health per region, plus the licence server that hands out decryption keys.
99.929%
30-day availability
220
monitored components
3
incidents this quarter
16min
median time to mitigate
Components
Component healthall systems operational
Playback (all regions)operational
60 days ago99.911% uptimetoday
Catalogue and searchoperational
60 days ago99.949% uptimetoday
Downloads and licence issueoperational
60 days ago99.983% uptimetoday
Sign-in and accountsoperational
60 days ago99.891% uptimetoday
Billingoperational
60 days ago99.893% uptimetoday
Living-room appsoperational
60 days ago99.943% uptimetoday
Incident history
Every incident since the platform launched, including the ones customers never noticed.
Partial transit degradation via one carrier
resolved30 Jun 2026 · impact: minor
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 — border router firmware
resolved06 Jun 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.