How we test Live Streaming Status
Why we test from multiple countries
Blocks are not universal. A service can be OK from one region and blocked from another. So we run the same reachability checks through multiple VPN exit regions (US, UK, France, Spain, Canada and more). This helps us spot regional patterns and avoid misleading “it works for me” results.
How to read the results
- OK: the site loaded on the last probe (usually HTTP 200).
- Degraded: we got a response but it looked restricted/unstable (for example 403/429). Try another exit IP.
- Down: the probe failed (timeout, DNS/TLS fail, or a hard block).
- N/A: not checked yet for that run, or the data point is missing.
- HTTP N/A: we could not capture an HTTP status code.
- Exit IP: the public IP we used for the probe. It can rotate as VPN servers change.
What the widget shows
How probes work
Our monitor runs automated checks from a dedicated VPS. Each run routes traffic through an active VPN WireGuard tunnel. For each service we perform DNS resolution, a TLS handshake and an HTTP GET request. We store only technical probe results.
How reliability 24h is calculated
Each probe run appends one JSON line to a local history file on the monitor VPS. For every service we count OK samples in the last 24 hours divided by total samples. This produces reliability_24h and samples_24h.
Limitations
- This is a reachability monitor, not a guarantee of playback quality.
- Status can change between checks. Streaming providers may update rules without notice.
- Regional catalogs differ. We test endpoint access, not content availability.
Data format
The widget reads a public JSON file updated automatically: /data/live/streaming-status.json.
Author: Denys Shchur · LinkedIn