Ping, Latency and Tick Rate Explained (and Why Server Location Matters)
Quick answer
Ping is the round-trip time for data to travel from your device to a server and back, measured in milliseconds; latency is the general term for that delay. Jitter is how much ping varies, packet loss is data that never arrives, and tick rate is how many times per second the server updates the game world. Physical distance sets the lowest ping you can get, because signals in fibre cover only about 200 km per millisecond one way, so choose a server close to your players.
What is ping?
Ping is the round-trip time (RTT) a small packet needs to travel from your computer to a server and back, measured in milliseconds. The name comes from the ping command, which sends ICMP echo requests and times the replies. The ping on a game's scoreboard measures the same idea over the game's own connection, but each game calculates and displays it a little differently, so the in-game number and a command-line ping will not always match exactly.
Latency is the broader word for delay anywhere in the chain. The total delay you feel is more than the network ping: the server waits for its next tick, your client buffers a little for smooth interpolation, and your display and input devices add their own delay. That is why a low ping alone does not guarantee a responsive game, while a high ping always makes it worse.
What are jitter and packet loss?
Jitter is how much your latency changes from one packet to the next, and packet loss is the share of packets that never arrive. Both often hurt more than a high but stable ping. A steady ping feels predictable and your brain adapts to it; a connection that keeps swinging up and down makes other players appear to teleport, and your shots register late or not at all.
Most real-time games send their traffic over UDP, which, unlike TCP, does not resend lost packets. Minecraft Java Edition is a well-known exception that uses TCP. Game netcode hides small gaps with interpolation and prediction, but as loss grows you get rubber-banding, where your character snaps back to an earlier position, delayed hits and sudden disconnects. Wi-Fi interference, overloaded home routers, bufferbloat on a saturated upload and congested links along the route are the usual causes.
What is tick rate, and how is it different from ping?
Tick rate is how many times per second the server updates the game world, while ping is how long data spends traveling. On each tick the server processes all player inputs received since the previous tick, simulates movement and game logic, and sends out updates. A 64-tick server updates roughly every 15.6 ms and a 128-tick server roughly every 7.8 ms. Higher tick rates capture fast actions more precisely, but they cost more CPU time and bandwidth.
Different games use different names for the same idea. Counter-Strike 2 servers run at 64 ticks per second and use a sub-tick system that also records the exact timing of actions such as shooting and moving between ticks. Minecraft targets 20 ticks per second, shown as TPS, which gives each tick a 50 ms budget; the MSPT value (milliseconds per tick) shows how much of that budget is used. Some survival games report server FPS instead, which means the same thing: how many simulation steps the server completes each second.
Tick rate is where the server's CPU shows up in gameplay. If the main thread cannot finish a tick within its budget, the tick rate drops: Minecraft TPS falls below 20, a shooter misses its target rate, and everyone on the server feels lag at the same moment, even players with a perfect ping. That is why single-thread CPU performance matters so much for game servers.
What do the numbers mean, and what counts as good?
Good values depend on the genre, but the ranges below are widely used rules of thumb among players and server admins. Fast competitive shooters are the most sensitive; turn-based, co-op and building games tolerate much more. Treat these figures as general guidance for reading your own test results, not as a guarantee or as a measurement of any particular server.
| Metric | What it measures | Generally good | Noticeable problems |
|---|---|---|---|
| Ping (RTT) | Round trip from you to the server and back | Under about 50 ms for competitive shooters, under about 100 ms for most other games | Above about 100–150 ms: late hits, delayed actions |
| Jitter | How much ping varies between packets | A few milliseconds | Swings of tens of milliseconds: stutter, teleporting players |
| Packet loss | Share of packets that never arrive | 0% | Around 1% and above: rubber-banding, missed inputs |
| Tick rate / TPS | Server world updates per second | Steady at the game's target (20 TPS in Minecraft, 64 ticks in CS2) | Below target: server-wide lag for everyone |
| CPU time per tick | How much of the tick budget is used | Comfortably below budget (under 50 ms MSPT in Minecraft) | At or above budget: TPS drops |
Why does physical distance affect ping?
Distance affects ping because data cannot travel faster than light, and in optical fibre it moves at only about two-thirds of the speed of light in a vacuum. That is roughly 200,000 km per second, or 200 km per millisecond one way. A round trip therefore costs about one millisecond for every 100 km of fibre, before a single router, queue or server adds anything.
Real routes make it worse. Cables follow roads, coastlines and seabeds rather than straight lines, and traffic often passes through exchange points in other cities before it reaches the server. A server 2,000 km away in a straight line may sit at the end of a fibre path of 2,500 km or more, which alone adds around 25 milliseconds of round-trip time that no hardware upgrade can remove. Distance is the part of latency you cannot optimize away, only avoid.
This is why a well-placed server beats a more powerful one far away. Moving a server closer to its players can cut ping more than any tuning, while jitter and packet loss depend mostly on route quality and on each player's own home connection.
How do you test ping, route and packet loss?
Use three tools: ping for round-trip time and loss, traceroute to see the path, and mtr to combine both over time. On Windows the commands are ping and tracert, and pathping adds per-hop loss statistics. On macOS and Linux you use ping and traceroute, and mtr can usually be installed from the package manager, for example with Homebrew on macOS.
Read the results carefully. Many routers give low priority to answering ICMP, the protocol ping uses, so a middle hop that shows loss or high times while later hops are clean is usually not a problem. Loss that starts at one hop and continues all the way to the destination is real. Also remember that some servers and firewalls do not answer ping at all; in that case the in-game ping is the better measure.
What should players in Türkiye look for?
Players in Türkiye get the most consistent results from a server located inside the country, ideally in a well-connected hub such as İstanbul. Keeping traffic domestic avoids the extra distance and cross-border hops a server abroad adds, and it usually reduces variation during busy evening hours. For mixed communities that also include players from Europe, the Middle East or the Caucasus, a server in Türkiye is often a sensible middle ground.
Beyond location, check the basics on your own side: a wired connection instead of Wi-Fi, a router that is not overloaded, and no large uploads running while you play. If ping to a nearby server is still high or unstable, run mtr or pathping and share the output with your internet provider or with the host's support team; hop-by-hop data makes the problem much easier to locate.
TheCrewHost runs its game servers and VDS in its İstanbul data center, its only location, which keeps connections domestic for players across Türkiye. If you already have a server, run the test steps below against its address to see the route from your own connection.
How can server owners keep latency and tick rate stable?
Server owners control the server side of the equation: keep the tick rate at the game's target and avoid adding delay. The most common causes of server-side lag are CPU-heavy plugins or mods, too many entities or loaded areas, oversized view or simulation distances, and autosaves on slow storage. These show up as tick or TPS drops rather than higher ping, and they hit every player at once.
Use the game's own tools to find the cause: timing and profiler reports, entity counts and the CPU graph in your control panel. Lowering view distance, pre-generating the world where the game supports it, limiting entity farms and removing unused plugins usually help more than adding RAM. Hardware matters too, which is why TheCrewHost game servers run on AMD Ryzen 9 9950X processors with strong single-thread performance and NVMe SSD storage.
How to test your connection to a game server
- 1
Use a wired connection
Plug into your router with a cable for the test. Wi-Fi adds its own jitter and packet loss, which hides what the route itself is doing.
- 2
Run a long ping
Ping the server address for at least a minute or two (ping -t on Windows, plain ping on macOS and Linux) and note the average, the spread and any lost replies.
- 3
Trace the route
Run tracert on Windows or traceroute on macOS and Linux to see each hop. Look for a sudden large jump in time that persists all the way to the end.
- 4
Measure over time with mtr
mtr, or pathping on Windows, sends repeated probes to every hop and reports loss and latency per hop, which is exactly what support teams ask for.
- 5
Test again at peak hours
Repeat the test in the evening, when home networks are busiest. A route that is fine at noon can congest at night.
- 6
Test your line under load
Run the test again while someone at home streams video or uploads files. If ping jumps sharply under load, bufferbloat on your router is the likely cause, not the server.
- 7
Compare with the in-game number
Check the scoreboard or network graph in the game. If the command-line ping is low but the game still feels laggy, look at the server's tick rate or TPS next.
Frequently Asked Questions
Is ping the same as latency?
Almost. Latency is any delay in delivering data, while ping is a specific measurement of round-trip latency, from you to the server and back. In everyday gaming talk the two words are used interchangeably. The overall delay you feel also includes the server's tick interval, client-side buffering and your display, so it is always somewhat higher than the network ping alone.
What is a good ping for online games?
As a general rule of thumb, under about 50 ms feels excellent in competitive shooters, under about 100 ms is fine for most other genres, and above about 150 ms becomes clearly noticeable. Stability matters as much as the number: a steady, moderate ping often plays better than a low ping that comes with jitter and packet loss.
Does a higher tick rate lower my ping?
No. Tick rate and ping are separate things. Ping is travel time across the network; tick rate is how often the server updates the world. A higher tick rate shortens the wait between updates and makes fast actions register more precisely, but it cannot shorten the distance to the server. It also needs more CPU time, so it only helps if the server can hold it steadily.
Why is my ping fine but the game still lags?
If ping is low and stable but everyone on the server lags at the same moment, the server is probably struggling to keep its tick rate, for example because of heavy plugins, too many entities or a CPU that is slow per core. If only you lag, check your Wi-Fi, background downloads, packet loss and your own computer's frame rate.
Will a VPN or gaming VPN lower my ping?
Usually not. A VPN adds an extra stop on the way to the server, which normally increases distance and latency. It can only help in the rare case where your internet provider routes traffic to a particular server very badly and the VPN happens to take a shorter path. Test with and without it using the steps above before you rely on one.
Why does my ping go up in the evening?
Evening is peak time for home internet use, so links inside your provider's network and along the route to the server get busier and queues grow. That adds latency and jitter, and sometimes packet loss. Running ping and mtr at different times of day shows whether the problem is congestion on the route or something constant, such as distance.
Does server RAM affect ping?
No. RAM does not change how long data takes to cross the network. Too little RAM can cause stutters, crashes and, on Java-based servers, frequent garbage-collection pauses that feel like lag, but these show up as tick rate drops rather than higher ping. Check the server's TPS or tick timings before you blame the network.
