AdvertisementLeaderboard / responsive slot
Protocol-level monitoring data

IPTV Stream Reliability by Protocol

See how discovered public stream endpoints are distributed and how their observed 7-day availability compares by supported protocol or media type.

Dataset generated: Loading monitoring dataset…

Protocol analysis

Observed stream reliability by protocol

Endpoints are grouped as HLS when a discovered HTTP/HTTPS location is an M3U8 manifest; other supported groups use their URL protocol.

Protocol / media typeDiscovered streams7-day availabilityChecks
Protocol reliability data will appear after stream discovery and monitoring have run.

What the monitor can and cannot compare

Phase 4 actively checks HTTP and HTTPS endpoints because they can be sampled safely using ordinary web requests. HLS is identified when the URL appears to reference an M3U8 manifest. The discovery database can record RTSP, RTP or UDP URLs found in playlists, but those protocols are not included in the default HTTP monitor batch and should not be interpreted as failed merely because they lack HTTP checks.

Availability also differs from sustained media performance. HLS may return a valid manifest while a later segment fails, and a direct HTTP media endpoint can respond quickly yet buffer during playback. Phase 4 intentionally measures endpoint reachability rather than turning the monitor into a playback or rebroadcast service.

For format background, read HLS explained, HTTP vs HTTPS IPTV and the HLS Inspector.

Non-HTTP protocols

Discovery is not the same as active monitoring. The public statistics distinguish unsupported/unmonitored protocols rather than treating them as downtime.

Measured availability

Explore M3U.co.uk public stream monitoring.

Open live status