Why a speed test is the wrong tool
A speed test measures how much data you can move in a short burst. Live television does not need much data — it needs it to arrive steadily.
That is why a connection can pass a speed test convincingly and still stutter. The speed test never measured the thing that was wrong. Ping and traceroute measure delay and loss, which is closer to what live streams actually experience.
Running a ping
On Windows, open Command Prompt and type ping -n 50 1.1.1.1. On a Mac or Linux, open Terminal and type ping -c 50 1.1.1.1.
That sends fifty small messages and reports how long each took. Fifty is enough to see a pattern; four, which is the Windows default, is not.
Reading the result
The summary at the end gives minimum, maximum and average times, and a packet loss figure. What matters:
- Packet loss above zero on a wired connection to a nearby address is a genuine problem. Even one or two per cent disrupts live video badly.
- A large gap between minimum and maximum is jitter. A connection averaging 20 ms but ranging from 8 to 300 is unstable, and that instability is exactly what live streams cannot absorb.
- A high average alone matters less than people think. Consistent delay is manageable; varying delay is not.
Separating your network from everything beyond
This is the most useful thing these tools do, and it takes two pings.
First, ping your own router. Its address is usually 192.168.1.1 or 192.168.0.1. This traffic never leaves your house.
Loss or jitter here means the problem is inside your home — Wi-Fi, a cable, or the router itself. Nothing beyond your front door can be responsible, and no change of provider will help. Start with Wi-Fi optimisation or move to a cable.
Then ping something on the internet, such as 1.1.1.1.
Clean to the router but poor to the internet means your home network is fine and the problem is your connection or the path beyond it. That is a conversation with your provider rather than a reason to buy equipment.
This single comparison resolves the most common uncertainty in streaming troubleshooting: whose problem is it.
Running a traceroute
Traceroute shows each step between you and a destination. On Windows, tracert 1.1.1.1. On Mac or Linux, traceroute 1.1.1.1.
You get a numbered list of hops with timings. Reading it:
- Hop 1 is your router. High times here mean a local problem.
- The next few hops are your provider's network.
- Later hops are the wider internet.
The mistake almost everyone makes
A single hop showing high times or asterisks is usually not a problem. Routers deprioritise replying to traceroute in favour of forwarding real traffic, so an intermediate hop can look terrible while passing data perfectly.
What matters is whether high times or loss appear at one hop and continue at every hop after it. That pattern indicates a real problem starting there. A spike at one hop that clears immediately afterwards is noise.
Testing while the problem is happening
Both tools measure the moment you run them, which makes timing everything.
Run them while the stream is stuttering, not afterwards. If the problem is intermittent, leave a ping running continuously — ping -t 1.1.1.1 on Windows, or plain ping on Mac and Linux — and watch it while you watch television. Spikes that coincide with visible stutter are your answer.
If a long-running ping stays clean while the picture breaks up, the network is not the cause, and the problem is more likely the device or the source. That is a genuinely useful negative result.
What the results point at
- Loss or jitter to your own router — your Wi-Fi, cable or router. Fixable by you.
- Clean locally, poor beyond — your line or provider. Worth reporting with the figures.
- Everything clean during a stutter — not the network. Look at the device or the channel, using the buffering guide.
- Problems only at certain times — contention rather than a fault.
Numbers also make a support conversation far more productive than a description of symptoms, whoever you are talking to.
Frequently asked questions
What ping is good enough for IPTV?
Consistency matters more than the figure. A steady 40 ms is better than one averaging 20 ms but ranging from 8 to 300. Packet loss above zero on a wired local connection is the clearest warning sign.
How do I know if a streaming problem is my network or my provider?
Ping your own router, then ping something on the internet. Loss or jitter to the router means the problem is inside your home. Clean locally but poor beyond means the line or the path.
One hop in my traceroute shows high times. Is that the problem?
Usually not. Routers deprioritise replying to traceroute while forwarding real traffic normally. Only worry when high times or loss start at a hop and continue at every hop after it.
Why does my speed test look fine when streaming stutters?
A speed test measures a short burst of throughput. Live streams need steady delivery, so jitter and packet loss break them while leaving speed-test results untouched.