How to test your internet connection for jitter and packet loss
A fast broadband plan can still deliver poor performance for video calls, online games, cloud backups and voice services. Two useful measures explain why: jitter is the variation in packet arrival time, while packet loss occurs when data fails to reach its destination and must be resent.
Testing these conditions at different times gives a more realistic picture than relying on a single speed-test result. In Australia, an NBN connection may behave differently during the evening, when households in Sydney, Melbourne, Brisbane and other cities are streaming video, gaming and working online at the same time.
Understand what the numbers mean
Jitter is measured in milliseconds and represents inconsistency rather than raw delay. A connection with 10 ms latency and 2 ms jitter will usually feel stable. A connection with 10 ms latency that suddenly varies between 10 and 100 ms can cause robotic audio, frozen video or delayed game controls.
Packet loss is generally shown as a percentage. Occasional loss below 1% may go unnoticed during ordinary web browsing, but real-time applications are less forgiving. Sustained loss above 2% can make calls unreliable, while higher levels often produce disconnections and severe audio or video distortion.
Prepare a fair test
Start by connecting a computer to the router with an Ethernet cable. Wi-Fi interference from neighbouring networks, microwaves, walls and crowded apartment buildings can make the result look like an NBN or internet service problem. Run a second test over Wi-Fi later to measure the experience people actually have around the home.
Pause large downloads, cloud synchronisation and streaming on other devices. Record the date, time, connection type and test server. An evening test after work may reveal congestion that a quiet weekday morning test misses, particularly when several household members are online.
Use practical testing tools
A browser-based speed test can provide latency, upload and download figures, but it may not clearly report packet loss or jitter. Tools such as Ping, Traceroute, MTR and WinMTR send repeated test packets and show whether trouble begins inside the home network, at the modem, or farther along the provider’s route.
Run at least 50 to 100 pings to the router’s local address, then repeat the process against a reliable public address. Local packet loss suggests a cable, router or Wi-Fi issue. Loss only beyond the router may indicate a provider, peering or wider network problem. Avoid treating one failed ping as proof of a fault because some servers deliberately deprioritise diagnostic traffic.
| Testing method | Best use | Useful result | Main limitation |
|---|---|---|---|
| Browser speed test | Quick general check | Latency, download and upload speed | May hide intermittent loss |
| Ping | Repeated delay test | Average latency, variation and loss | Depends on the target server |
| Traceroute | Finding the route | Identifies likely problem hops | Some hops do not reply |
| MTR or WinMTR | Long observation period | Shows recurring loss and delay | Requires careful interpretation |
Compare wired and wireless results
If Ethernet is stable but Wi-Fi shows jitter, move the router to an open, central position and test the 5 GHz or 6 GHz band where supported. Mesh systems can improve coverage, although wireless backhaul between nodes may add delay. Changing channels may help in dense housing, but it will not fix congestion outside the property.
Check whether the issue affects every device. If a television, phone and laptop all show packet loss at the same time, the router or service is more likely to be involved. If only one old laptop struggles, update its wireless driver or test its network adapter before contacting the provider.
Interpret results for everyday services
Video meetings need consistent delivery more than maximum download speed. A connection with modest bandwidth but low jitter can outperform a much faster service with repeated spikes. For gaming, test to a nearby Australian server when possible; a server overseas can add unavoidable distance and make the result less representative.
Interactive websites and services can expose instability quickly, including wild symbols in casino games, where delayed responses may interrupt a session. Similarly, cloud applications and hosted business systems can feel sluggish when acknowledgements are lost, even if a later speed test reports an impressive download rate.
Document faults and protect your data
Keep screenshots and logs from several times of day, including the exact test target. When contacting an Australian internet provider, this evidence is more useful than saying the connection is “slow”. Ask whether there is planned maintenance, a known local outage, congestion or a fault between the premises and the NBN equipment.
Store results with clear filenames, using a method similar to organising and labelling files. Avoid publishing your public IP address, full address or device identifiers in screenshots. Under Australia’s Privacy Act, personal information should be handled carefully, even when a diagnostic record seems harmless.
A good test separates local Wi-Fi trouble from broader service faults, compares quiet and busy periods, and measures consistency as well as speed. The key point to remember is that a dependable internet connection delivers packets regularly, with low jitter and little or no loss.