--- title: "Ping, jitter and packet loss: the difference in practice | StreetHosting" description: "Learn what ping, jitter and packet loss mean, how each one affects games, voice and APIs, which values are good and what to do when one goes bad." url: "https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss" type: "page" language: "en-US" --- Infrastructure · 9 min · Beginner Published on Sep 28, 2026 · Updated on Sep 28, 2026 # Ping, jitter and packet loss: what each number says about your connection Ping measures how long the network takes, jitter measures how much that time varies and packet loss measures what never arrives. Each one ruins the experience in a different way, and knowing which one is bad is what decides the fix. By [Equipe StreetHosting](https://streethosting.com.br/en/autores#equipe-streethosting) · StreetHosting infrastructure and support team [Network, DNS and domains](https://streethosting.com.br/en/guides/topics/networking) [Latency and ping](https://streethosting.com.br/en/guides/topics/latency) Summarize with: [](https://chat.openai.com/?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "ChatGPT") [](https://claude.ai/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Claude") [](https://www.google.com/search?udm=50&aep=11&q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Google AI Mode") [](https://x.com/i/grok?text=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Grok") [](https://www.perplexity.ai/search/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Perplexity") Share: [](https://x.com/intent/tweet?text=Ping%2C%20jitter%20and%20packet%20loss%3A%20the%20difference%20in%20practice&url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss "Share on X") [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss "Share on Facebook") [](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss "Share on LinkedIn") [](https://wa.me/?text=Ping%2C%20jitter%20and%20packet%20loss%3A%20the%20difference%20in%20practice%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Finfrastructure%2Fping-vs-jitter-vs-packet-loss "Share on WhatsApp") For agents: Copy as Markdown [.md](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss.md) In this guide 8 sections * [The three numbers](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#tres-numeros) * [Ping: where latency comes from](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#ping) * [Jitter: when the timing varies](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#jitter) * [Packet loss: what never arrives](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#packet-loss) * [Effects on games, voice and APIs](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#efeitos) * [Reference values](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#valores) * [What to do when it gets worse](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#o-que-fazer) * [Where to host](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#onde-hospedar) Quick answer **Ping, jitter and packet loss** measure different things. Ping is the round-trip time to the server. Jitter is how much that time varies from one packet to the next. Packet loss is the percentage of packets that never arrive. High ping gives you constant delay, high jitter gives you jumps and unevenness, and loss gives you teleporting in games, robotic voice on calls and stalls in applications. For real-time use, all three have to be good at the same time. ## The three numbers[](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#tres-numeros) A single command shows all three. On Linux, a 100-packet ping ends with a summary like this one, in an illustrative example: `$ ping -c 100 203.0.113.10 ... --- 203.0.113.10 ping statistics --- 100 packets transmitted, 98 received, 2% packet loss, time 99140ms rtt min/avg/max/mdev = 28.113/31.402/74.920/6.815 ms` * **Ping:** the `avg` column is the average round-trip latency, 31.4 ms in the example. The `min` shows the best case, close to the physical limit of the route. * **Jitter:** the `mdev` is the latency deviation, 6.8 ms here. The `max` of almost 75 ms shows there were spikes. * **Packet loss:** 2 out of 100 packets did not come back, or 2% loss. On Windows, `ping -n 100 IP` shows loss, minimum, maximum and average, but it does not calculate jitter. The gap between the minimum and the maximum already gives you a hint. To measure properly and at several points along the path, follow the guide on [how to test VPS latency](https://streethosting.com.br/en/guides/vps/test-vps-latency). If the concept of latency is still new to you, start with [what latency and ping are](https://streethosting.com.br/en/guides/infrastructure/what-is-latency-and-ping). ## Ping: where latency comes from[](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#ping) Latency has four components, and only one of them is fixed: * **Propagation:** light in fiber travels at about two thirds of its speed in a vacuum. Every 100 km of fiber between you and the server adds around 1 ms to the round-trip ping, and fiber almost never runs in a straight line. * **Route:** traffic follows the agreements between carriers, not the map. Traffic between two cities in the Northeast that goes through São Paulo still happens and adds milliseconds without being a defect; a route that crosses the ocean to reach a server in Brazil, on the other hand, is a routing problem. * **Queue:** every router holds packets in a queue when the link is busy. A full queue means extra delay, and that is where most of the jitter comes from. * **Processing:** the time routers and the server itself take to handle the packet. Usually small, it grows on overloaded equipment. The ping shown inside a game is not always the same as the `ping` command. The command uses ICMP and measures only the network. The game measures with its own packets and sometimes includes the time the server takes to process them. That is why an overloaded server can show high in-game ping on a perfect network, a difference explained in detail in [how to reduce game server ping in Brazil](https://streethosting.com.br/en/guides/infrastructure/reduce-game-server-ping-brazil). ## Jitter: when the timing varies[](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#jitter) Jitter is the variation in latency between consecutive packets. If one packet takes 20 ms, the next 22 ms and the one after 21 ms, jitter is low. If the sequence is 20, 65, 18, 90, jitter is high, even if the average looks reasonable. Different tools calculate it in slightly different ways: ping's `mdev` and MTR's StDev both measure the deviation around the average. The most common causes are always the same: * **Bufferbloat:** when someone in the house uploads a video, runs a cloud backup or downloads a big game, the router queue fills up and the latency of everything else shoots up. It is the number one cause of home jitter. * **Wifi:** interference, distance and neighboring networks on the same channel make the radio resend frames, and every resend becomes variable delay. * **ISP congestion:**at peak hours, the ISP's internal or outbound links fill up and queues grow. * **Mobile networks:** 4G and 5G vary with signal, movement and the number of people on the same tower. Real-time applications protect themselves from jitter with a buffer. Voice and video hold a few milliseconds of audio before playing it; games show other players slightly in the past to smooth out uneven arrival. That cushion has a limited size, and once jitter exceeds it the effects show up on screen and in your headset. ## Packet loss: what never arrives[](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#packet-loss) Packet loss is the fraction of sent packets that never reach the destination. A router with a full queue drops whatever does not fit; a bad cable or a dirty fiber connector corrupts frames that get thrown away; wifi gives up after several attempts; a link saturated by a DDoS attack drops everything above its capacity. The effect depends on the protocol. With UDP, the lost packet is simply missing: the game skips an update and the voice loses a chunk. With TCP, the packet is resent, and everything that arrived after it waits in the meantime. 1% loss on TCP cuts throughput and creates short stalls. The full explanation is in [TCP or UDP on servers](https://streethosting.com.br/en/guides/infrastructure/tcp-vs-udp). Not all loss that shows up in diagnostics is real. Routers in the middle of the path limit how many ICMP replies they generate per second, so an intermediate hop can show 30% loss while the final destination answers 100%. Only loss that continues to the last hop counts. The guide on [using MTR to diagnose the network](https://streethosting.com.br/en/guides/infrastructure/how-to-use-mtr) shows how to tell one case from the other. ## Effects on games, voice and APIs[](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#efeitos) The same bad number ruins each type of application in its own way. The table helps you recognize, from the symptom, which metric is the problem. | Bad metric | Action games | Voice and video | Websites and APIs | | ----------- | ------------------------------------------------------ | ------------------------------------------------- | -------------------------------------------------------------------- | | High ping | Delay to land hits, advantage to whoever attacks first | Crossed conversation, people talk over each other | Every round trip takes longer and the time adds up with each request | | High jitter | Players jump around, uneven movement | Larger buffer and choppy voice | Unpredictable response time and sporadic timeouts | | Packet loss | Teleporting, unregistered shots, disconnects | Robotic voice, clipped words | Retransmissions, stalls and slow downloads | For voice, the ITU G.114 recommendation sets 150 ms of one-way delay as the limit for a comfortable conversation. For APIs, latency multiplies: a new HTTPS call pays for the TCP handshake, the TLS handshake and the request, so a 50 ms ping turns into well over 50 ms of waiting for the user. ## Reference values[](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#valores) There is no single standard, and different games tolerate different things. The table is a practical reference for real-time applications, such as games and calls, with the server in the same region as the user. | Metric | Good | Acceptable | Problem | | ------------------ | ----------- | --------------------- | ----------------- | | Ping to the server | Up to 40 ms | 40 to 80 ms | Above 100 ms | | Jitter | Up to 5 ms | 5 to 15 ms | Above 15 ms | | Packet loss | 0% | Up to 0.5% occasional | Above 1% constant | Read all three together. A 60 ms ping with 2 ms jitter and zero loss usually delivers a better experience than a 25 ms ping with 20 ms jitter and 1% loss. Stability is worth more than the lowest possible number. ## What to do when it gets worse[](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#o-que-fazer) Before switching servers or ISPs, isolate the problem. The order below rules out what is under your control first. * Repeat the test with a cable, no wifi, to rule out the radio * Repeat it with nobody else using the internet, to rule out bufferbloat * Run ping with the upload saturated: if latency explodes, enable SQM or QoS on the router * Test another destination in the same region to see whether the problem is only with one server * Run MTR with 100 packets to the server and see where the loss starts * Repeat at peak hours and off-peak to find congestion * Take the MTR to your ISP's support or to the server provider's support High, constant ping is almost always distance or route. In that case the fix is to host closer to the people who use it and to check the path with the guide on [using traceroute to find routing problems](https://streethosting.com.br/en/guides/infrastructure/how-to-use-traceroute). Jitter is usually local or tied to peak hours. Loss that starts at the first hop is from your home; loss that starts mid-path and continues to the destination belongs to someone's network, and the MTR is the proof you need to open a ticket. ## Where to host[](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#onde-hospedar) On the server side, three things reduce the three numbers: being close to your audience, being on a network that handles peaks and being protected against attacks that saturate the link and cause loss. [StreetHosting VPS plans](https://streethosting.com.br/en/vps) sit in a data center in São Paulo, with a 1 Gbps uplink and Anti-DDoS included, and the Xeon line is advertised with an average latency of 20 ms in Brazil. * **Game server:** the [Ryzen 9 9950X VPS](https://streethosting.com.br/en/vps/ryzen) pairs the location with a clock speed of up to 5.7 GHz, which avoids the processing lag that players mistake for network lag. It ranges from R$ 40.00 (1 vCPU, 2 GB DDR5) to R$ 846.00 (14 vCPU, 64 GB), including R$ 118.00 with 4 vCPU and 8 GB. * **API, bot or website:** the Xeon VPS starts at R$ 26.00 with 2 vCPU and 2 GB and goes up to R$ 553.00 with 24 vCPU and 64 GB, with more cores per real to serve many connections at once. No server fixes a player's wifi jitter or loss on their ISP's network. What hosting delivers is a close, stable starting point, and the diagnosis in this guide shows when the problem is on the other side. In this guide * [The three numbers](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#tres-numeros) * [Ping: where latency comes from](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#ping) * [Jitter: when the timing varies](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#jitter) * [Packet loss: what never arrives](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#packet-loss) * [Effects on games, voice and APIs](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#efeitos) * [Reference values](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#valores) * [What to do when it gets worse](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#o-que-fazer) * [Where to host](https://streethosting.com.br/en/guides/infrastructure/ping-vs-jitter-vs-packet-loss#onde-hospedar) ## Frequently asked questions What is the difference between ping and jitter? Ping is the time a packet takes to reach the server and come back. Jitter is how much that time changes from one packet to the next. A steady 40 ms ping plays better than a ping that alternates between 15 and 90 ms, even if the second one has the lower average. How much packet loss is acceptable? On a healthy connection the normal value is zero or very close to it. Occasional loss below 0.5% goes almost unnoticed, but constant loss above 1% already shows up in games and voice calls. Before drawing a conclusion, confirm that the loss continues all the way to the destination and is not just at a router in the middle of the path. Does high jitter cause lag in games? Yes, and it is often what players call lag. The game expects packets at a steady pace and smooths out small variations, but once jitter exceeds that cushion, other players jump around on screen and your commands seem to respond unevenly. Why does ping vary so much on wifi? Because wifi shares the air with other devices and neighboring networks, and every collision or bit of interference makes the radio resend the frame. That shows up as jitter and latency spikes. Testing with a cable is the fastest way to find out whether the problem is the wifi or the internet. Is high ping a server problem or my internet? Compare. If other servers in the same region respond well and only one is high, the path to it or its location is the problem. If everything is high, look at your own connection. An MTR to the server shows which hop the latency climbs at and whether the loss starts on your network or further along. Next step See VPS plans Root VPS in Brazil with NVMe and Anti-DDoS. [See VPS plans](https://streethosting.com.br/en/vps) [See Ryzen VPS Ryzen 9 9950X VPS in São Paulo with root access, NVMe and gamer Anti-DDoS.](https://streethosting.com.br/en/vps/ryzen) ## Related guides [Infrastructure Beginner What is latency and ping on a server Latency and ping shape how fast your service feels to users and players. Understanding them helps you choose better infrastructure. 2 min Read guide](https://streethosting.com.br/en/guides/infrastructure/what-is-latency-and-ping) [VPS Beginner How to test VPS latency from Brazil Good latency is the latency your users measure, not what you see from your own computer. Learn how to test with ping, TCP and MTR, how to measure from other cities without owning a machine there, and how to compare the numbers fairly. 9 min Read guide](https://streethosting.com.br/en/guides/vps/test-vps-latency) [Infrastructure Intermediate How to use MTR to diagnose network problems MTR combines traceroute and ping and shows, hop by hop, where latency climbs and where packets get lost. The trick is knowing which loss is real and which is just a router rationing its replies. 8 min Read guide](https://streethosting.com.br/en/guides/infrastructure/how-to-use-mtr) [← Back to the Guide Center](https://streethosting.com.br/en/guides)