A playlist can look perfect on paper — thousands of entries, tidy categories, logos everywhere — and still be a ghost town when you press play. Structure tells you how a list is built; liveness tells you whether anyone's home.

The free health checker below samples channels from your M3U playlist and knocks on each one's door, measuring which servers respond and how fast. In about a minute you get a reachability score that separates healthy services from zombie lists.

Structure vs. Liveness: What Each Tells You

CheckAnswersTool
Structural analysisIs the list organized? Duplicates? EPG?M3U Analyzer
Liveness probe (this tool)Do servers answer right now?Health Checker
Real playbackDoes the actual video decode & play smoothly?Your player + trial period

All three matter, in that order. A structurally clean list that's half-dead is worthless; a messy list with rock-solid servers can still deliver.

The Free Playlist Health Checker

Stream Liveness Tester

Samples your playlist and pings each stream host directly from your browser.

Sample size
Starting…0%
Reachability Score
0Responding
0Timed Out
0No Response
Avg Response
Fastest
0Channels Tested
StatusChannelCategoryResponse
Read Results With Context

Browsers can't fully verify video streams: requests are opaque, and pages served over HTTPS can't reach plain-HTTP stream servers at all (mixed-content blocking). So treat this as a reachability signal — a channel marked failed may still play fine in VLC. Patterns matter more than individual results: 90% responding = healthy infrastructure; 30% = trouble.

How the Check Works

  1. Parse — your playlist is read locally; nothing is uploaded anywhere.
  2. Sample — a random slice of your chosen size is drawn so results represent the whole list without testing every entry.
  3. Probe — up to 8 channels are tested in parallel, each with an 7-second timeout. A response within the window counts as alive. Methodology aligns with Netflix's ISP Speed Index and the FCC's broadband speed guide.
  4. Score — responding ÷ tested × 100, plus per-channel timings for spotting slow providers.

Interpreting Your Score

Pro Workflow

Run the structural analyzer first, then this health check, then judge stability across a full trial week — including one prime-time evening. Three data points beat any single test.

Frequently Asked Questions

Why do some obviously-working channels fail here?

CORS and mixed-content rules stop browsers from reading many stream responses, and HTTPS pages can't call HTTP servers outright. Failures are strongest when they cluster; single failures deserve a manual VLC check before condemnation.

Can I test the whole playlist?

You can select 100 as the sample size. Testing tens of thousands of entries would take hours and effectively attack the provider's servers — sampling gives the same confidence in a fraction of the time.

Does checking use much bandwidth?

No. The probe opens a connection and reads the initial response, then stops — kilobytes per channel, not megabytes of video.

Should I tell my provider about dead channels?

Yes — good providers re-source or migrate lines quickly. Bring the percentage and a few example names from the table; it turns "it doesn't work" into an actionable report.

Conclusion

Availability is the foundation everything else sits on. A two-minute sample check tells you whether a provider's infrastructure deserves your monthly fee — before buffering, support tickets, and refunds become your teacher.

Earnest IPTV runs load-balanced servers monitored around the clock. Get a trial line, run this exact check against it, and compare the score yourself.