Measuring…
The verdict for this game appears once the first full second of packets is in.
Comparing with other tests to this server…
Measuring…
The verdict for this game appears once the first full second of packets is in.
Comparing with other tests to this server…
Are you sure you want to delete all results?
| Date & Time | Duration | Avg Ping | Avg Jitter | Packet Loss | Actions |
|---|
Ghost blocks? Eating the same food twice? Delayed PvP knockback?
Minecraft servers run at exactly 20 Ticks Per Second (20Hz). Every 50 milliseconds, your client and the server exchange small data packets (around 200 bytes) to update block placements, entity movements, and combat hits. Standard internet speed tests completely miss the micro-stutters that ruin Minecraft. They test raw bandwidth, but Minecraft requires packet stability. If your connection drops a packet, the server rejects your block placement or ignores your sword swing. Our tool simulates exact 20Hz server traffic to expose the hidden packet loss causing your block lag.
What this test sends: 20 packets per second of 300 bytes, matching Minecraft rather than a generic ping. verified
Mojang's server runs a fixed 20 ticks per second (50 ms per tick); the whole game logic is defined against it.
Run the 20Hz test above for at least 60 seconds. Here is what your results mean for Minecraft:
Red vertical lines mean your connection dropped data. In Minecraft, this causes "ghost blocks"—you place a block, but it disappears a second later. It also causes the eating glitch where your character finishes eating food, but your hunger bar doesn't fill up and the animation resets.
Jitter is ping fluctuation. If your ping bounces between 30ms and 120ms, your movement will become completely unpredictable. You will take delayed damage from mobs, fail precision parkour jumps, and rubberband off edges because the server disagrees with your client's position.
High baseline ping means you are permanently behind the server's current tick. On competitive servers like Hypixel, this gives your opponent a massive advantage. Your hits simply won't register fast enough, resulting in you taking extreme knockback (KB) while dealing none.
If the tool above shows an unstable connection, try these specific fixes.
The Symptom: "Unknown Host" errors or extremely high ping to a specific server like Hypixel.
Large Minecraft networks use proxy routing. Sometimes your local DNS cache routes you to a proxy server on the other side of the country, crippling your ping.
ipconfig /flushdns. If playing Hypixel, try connecting to proxy.hypixel.net or mc.hypixel.net to force a new routing path.The Symptom: Rubberbanding and sudden "Internal Exception: java.net.SocketException: Connection reset" disconnects.
Wi-Fi naturally drops packets due to interference. The Java server architecture is notoriously unforgiving of dropped packets and will abruptly kick you if your connection hangs.
The Symptom: Massive block lag when family members are streaming Netflix or downloading files.
Your 20Hz Minecraft packets are getting stuck in your router's traffic queue. The server isn't getting your movement updates in time, causing it to freeze you in place.
The Symptom: High ping to your friend's specific Realm or third-party SMP host, but fine on other servers.
Sometimes your ISP has a highly inefficient, congested route to the specific datacenter hosting the server (like an AWS or OVH node).
What you see in game, and which number on this page explains it.
| What you see in Minecraft | Look at | What it means |
|---|---|---|
| Blocks you placed reappear a second later | loss | The placement never reached the server. Your client had predicted it. |
| You walk into a wall that is not on your screen | loss | A chunk update went missing; your view of the world is behind the server's. |
| Mobs slide and stutter while your ping looks fine | jitter | Twenty updates a second, unevenly spaced, is enough to see. |
| Only on one server, never in single player | server | The host's tick rate can drop under load. Your chart being clean is the proof. |
Mojang's server runs a fixed twenty ticks per second - one tick every 50 ms - and that figure is not an estimate but a documented constant that the entire game is built around. Redstone timings, mob behaviour and hopper throughput are all defined in ticks, which makes Minecraft one of the few games where the rate this page measures at is also a number the community argues about in build guides.
Almost everything in a multiplayer world is shared state that both sides act on. Placing a block, opening a chest, hitting a mob: your client predicts the outcome immediately and the server decides it. When a packet is lost, the prediction is not corrected gracefully - the block flickers back out of existence, the chest closes, the hit does nothing. Players call this lag, and it is specifically loss, which is a different problem with a different fix.
The packets are relatively large for this catalogue, around 300 bytes, because a chunk of world contains more than a player position. On a busy server with many entities and loaded chunks, that adds up in a way an arena shooter never does - and a connection that is fine for a small survival world can struggle on a crowded minigame server, which is worth measuring rather than guessing at.
One distinction is more useful here than anywhere else on this site: the server's own tick rate can fall. A machine that cannot keep up drops below twenty ticks and everything slows down for everyone connected, no matter how good their lines are. If the chart above is clean while the world is stuttering, you are looking at the host's hardware, and the conversation belongs with whoever runs it.
This is known as a "ghost block" and is caused by packet loss. Your client places the block on your screen, but the data packet is dropped by your internet before it reaches the 20Hz server. The server then sends an update back to your client, overriding your screen and erasing the block.
Minecraft relies on extremely small data packets sent 20 times a second, not large downloads. Standard speed tests check bandwidth (TCP), not stability (UDP). If you have high jitter or packet loss, you will experience severe block lag even if you have gigabit fiber internet.
For casual survival, anything under 100ms is perfectly fine. For competitive PvP formats (like Bedwars, Skywars, or Crystal PvP), you want your ping under 50ms. High ping causes delayed hit registration, meaning you will take knockback (KB) before your own swings register.
This happens when your router or ISP drops communication with the server for several seconds. The Java server stops receiving your 20Hz tick updates, assumes your internet completely died, and forcibly drops the connection to save server resources.