Guides
What Is Latency?
Latency is communication delay. A ping result usually describes the round-trip time to a specific destination.
Latency is delay in communication. Ping commonly measures round-trip time, RTT, to a particular destination in milliseconds; 1 ms is 0.001 seconds. One-way delay is a different measurement. Do not simply halve RTT: the forward and return routes and queues can differ. No universal 30, 60 or 100 ms threshold guarantees a good game or call.
Distinguish latency from throughput
Mbps describes data per second; ms describes time. High throughput does not guarantee quick responses. Check timing variation, packet loss and the affected app as well. Slow frame processing or a slow server response need not be a network-delay problem.
What can affect the result?
- Distance and routing can affect delay. The number of router hops alone does not determine the time.
- Wi-Fi interference, weak reception or shared airtime can affect a measurement. There is no fixed millisecond increase for every wireless connection.
- Queues during uploads or downloads can increase delay. A high reading does not identify the responsible queue.
- The device, measurement software and destination response can affect the observation. Router age alone is not evidence of a fault.
Understand the VMAXCHECK reading
When NDT data is available, we show an estimated RTT from server-side TCP measurements. This is not a separate ICMP ping or a dedicated idle, loaded-latency or jitter measurement. It describes the path to the test server, which need not match your game or call. NDT generates traffic: run it separately from important calls and record the server.
Make controlled comparisons
- Record the time, device, app, destination, connection and other traffic. Save app statistics and relevant router events before restarting equipment. Change one condition at a time.
- Compare Wi-Fi and Ethernet with the same device, destination and time window. Consistently better wired results justify investigating the local wireless link; they do not prove a specific component is faulty.
- Choose a method that explicitly distinguishes idle and loaded latency. Outside important calls, compare readings with the same method before, during and after an allowed transfer of your own. Record direction and rate. Repeated deterioration under load is a clue, not a fault location.
- Compare another time, an allowed alternative destination or another device under similar conditions, then check the actual app again. If a restart is justified, save the evidence first and follow the maker’s instructions.
A bounded Windows ping check
On Windows you can use ping /n 4 HOST. Replace HOST with a name or address you are allowed to test. Four ICMP requests are only a short sample; record replies and times. A missing reply may reflect filtering or the timeout rather than an app failure. Keep network protection enabled. Share diagnostic details privately with support.
Common questions
- What ping is good for gaming? Compare the same game server and method, timing variation and actual play. A low average can hide spikes; one number is not a guarantee.
- Why is it high only in the evening? Repeat comparable checks and record household traffic. The time of day alone does not prove provider congestion.
- Can a faster plan help? More capacity may reduce queueing when your own traffic fills the connection. It need not change distance, routing or app response. Investigate the limit before buying.