Public IPTV Uptime Statistics
A transparent operational dataset built from recurring server-side checks of endpoints discovered through curated public M3U sources.
Dataset generated: Loading monitoring dataset…
Curated country, category and language M3U sources.
Unique endpoint URLs discovered in monitored public playlists.
Endpoints with at least one server-side availability check.
Endpoints returning a successful response to the latest check.
Daily observed availability
Each row summarises determinate stream checks captured on that UTC date.
Restricted and rate-limited checks are not counted as downtime when calculating availability percentages. Their status is still retained in the current-state totals.
How to interpret these IPTV uptime statistics
The Phase 4 dataset is original operational data produced by M3U.co.uk’s own checker. It begins when the cron service is first run; the site does not backfill invented historical values. The monitor rotates through discovered endpoints by oldest check time, which means the exact interval for a particular stream depends on the total number of endpoints and the configured cron batch size.
The most important distinction is between source availability and stream availability. A country M3U file can respond perfectly while several media endpoints inside it are unavailable. Conversely, an upstream playlist can be temporarily unreachable while an already discovered endpoint still works. We preserve those layers independently.
Response time is a network diagnostic rather than a video-quality score. A fast manifest response does not tell you the sustained throughput, codec compatibility or buffering behaviour of the media segments that follow. For that reason, the monitor samples a small amount of data and does not attempt to watch or record streams.
For a citable summary of the evolving dataset, see Public IPTV & M3U Statistics 2026.