Affiliate disclosure · IPTVDB may earn commission on some links — it never affects rankings. Q2 2026 test cycle · 18 services tracked

Uptime, precisely defined

Uptime for IPTV is not "did the server respond" — it is "did a real stream play without interruption". Here is our exact definition.

Our uptime definition

We define a service as "up" for a given 60-second poll window if: (1) the Xtream Codes API (or M3U endpoint) responded with a 200 in under 5 seconds, (2) the primary playlist URL returned a valid M3U body, and (3) a sample channel played without buffering for the entire 60-second window.

All three conditions must pass. A service whose API responds 200 but whose streams stutter is not scored as up.

Peak-window weighting

Monday 11am local time and Saturday 8:30pm local time are not equal for IPTV users — peak congestion periods reveal provider infrastructure quality in ways daytime polling hides. We weight peak-window uptime 3x in the composite score.

  • Peak windows (3x weight): Sat 18:00–23:00 local, Sun 12:00–22:00 local, Mon–Fri 19:00–23:00 local.
  • Off-peak windows (1x weight): all other hours.

Why not 99.9% SLA-style reporting?

SLA-style "99.9% uptime" numbers are marketing-friendly but mostly meaningless for IPTV. 99.9% uptime is 8.76 hours of downtime per year. If all 8.76 hours fall during peak Saturday sports, the service is unusable. We report separate peak-window and off-peak uptime figures so subscribers can see both.

Up criterion
API 200 + M3U valid + 60s playback no-buffer
Poll interval
60 seconds
Peak window weight
3x in composite score
Reporting format
Separate peak + off-peak percentages
Minimum cycle
30 days (43,200 polls per rig per channel)