Field note · Updated · Jay Fan
A flat number, a jump, and a hole are not the same fault.
High ping is a large delay that stays large. A spike is a short jump that returns while packets are still arriving. Packet loss is data that never shows up, which can snap a character or punch holes in voice even when the delay number looks ordinary. Name the shape on one screen before you change a setting. This note does not publish a packet-loss capture from our line.
Symptom
What does a flat high delay look like next to a hole in the stream?
The delay figure sits up and barely moves. You can still play, but everything arrives late by roughly the same amount: shots feel heavy, movement feels late, the whole session feels far. If the game has a loss mark, it stays quiet. Friends in another city may not share your number, because their path length is different. Until a later check says otherwise, that pattern is distance, server placement, or a long route. It is not, by itself, a dropped-packet story.
A hole looks different even when the delay figure is modest. The loss mark ticks. Voice drops syllables. A hit that looked clean on your screen is denied. The character snaps backward. The delay figure can stay calm because the packets that did arrive were on time. People then photograph only the delay figure and argue about a problem that figure was not measuring.
Both can be true in one match. A far server plus a dirty last hop gives you a high baseline and a loss mark together. Write both. Do not let the larger number erase the other one, and do not invent a percentage you did not read off the client.
What does a spike look like when the packets still arrive?
A spike is a jump and a return. The trace sits in a band, leaps, and comes back, often in the same few seconds as a hitch you felt. If the loss mark does not move during that leap, you do not yet have a loss finding. You have unstable delay. Unstable delay has its own usual leads: a radio link that retries, a queue in front of a bulk upload, a route that changed for a moment. Those leads are not interchangeable with “the line is dropping packets.”
The evening-queue note is the page for a jump that lines up with a backup, a livestream, or a console install. The Wi-Fi versus Ethernet note is the page for a jump that might be the last hop inside the house. This page stops at the naming. If you run both experiments in the same ten minutes, you will not know which one moved the trace.
A single leap during one fight is not a finding. The shape has to repeat under a condition you wrote down, or it stays an anecdote. Keep the failed moment in the log. Deleting it is how a clean story gets invented.
Troubleshooting steps
What do you write down before you touch a setting?
- The shape, in words someone else could check. Flat and high, jump and return, or a loss mark, a voice hole, or a position snap. If you cannot pick one, write “mixed” and list the parts. “Lag” is not a shape.
- The session the game actually showed. Server, region, realm, or host name. Solo or party, and whether you were the host. Mode or activity. A line that only says “online” cannot be repeated.
- The link, as one phrase. Cable, wireless in the usual room, or wireless next to the access point. Do not also change this while you test something else.
- What else the house was sending. Idle, a call, a cloud backup, a game update, or someone else’s stream. Name the transfer. “Busy” is too vague to retest.
- The clock, including the timezone. A flat number at noon and a jumpy number after dinner are not one fault. The evening note is for the clock. This list is so you do not mix that clock into a loss story by accident.
Leave measurement cells blank until that session exists. Do not convert a blank into zero. Zero on a loss mark and “I did not look” are opposite facts. The table below is a reading guide, not a result from this desk.
Which single change matches which shape?
Use one row. Make that change. Play a comparable moment with the same server name. Then stop, even if you are curious about the next idea. A second change in the same sitting voids the row. Keep the void row anyway.
| Shape you can point at | What the counters are doing | The one change that matches | What that change cannot prove |
|---|---|---|---|
| Flat and high, loss quiet | Delay stays large. The loss mark stays quiet. | Confirm the server, realm, or host, and whether a party moved you. Repeat the same choice once. | It cannot show a bad cable, and it cannot show that a routing product will shrink the distance. |
| Jump and return, loss quiet | Delay leaps and recovers. Packets still arrive. | Pause one bulk transfer, or move one radio condition, not both. Keep the server name fixed. | A calmer next match on a different server is not evidence about the transfer you paused. |
| Loss mark, voice holes, or snaps | Something is missing. The delay figure may look ordinary. | Quiet the house and, if you have a cable, repeat on that cable. Watch the loss mark, not a throughput grade. | A healthy speed grade does not mean the game packets arrived. |
| Mixed | You can see more than one row at once. | Split them. Record the flat baseline first. Record the jump or the hole in a second pass. | One screenshot cannot be asked to prove two mechanisms. |
A blank row you can copy
| When | Session held still | Shape | One change | Loss mark after | Delay figure after | Void? |
|---|---|---|---|---|---|---|
| Example shape | Server or host name, solo or party | Flat, jump, hole, or mixed | Server check, one pause, or one cable | Quiet, ticking, or not shown | Still flat, still jumpy, or calmer | Yes if two things changed |
| Pass 1 | ||||||
| Pass 2 |
How do you walk the checks without mixing them?
- Freeze the server or session name. If a party can move you, write the host before you queue.
- Watch a short stretch of actual play, not a menu. Note whether the delay figure is flat, jumpy, or sitting beside a loss mark.
- If the shape is flat and the loss mark is quiet, the next check is the server choice. It is not the cable, and it is not a NAT screen. The console NAT note is for invites and voice, not for a number that is already on screen.
- If the shape is a jump and the loss mark is quiet, pick either the upload pause or the radio comparison. Open the other note and do not run it in this pass.
- If the loss mark moves, or voice holes line up with the snaps, keep the loss mark in the notes and run the quiet pass. Use a cable when you have one. The delay figure is allowed to stay ordinary. That is the point of watching the loss mark.
- Play a comparable moment again. If the matchmaker changed the host, mark the row void. A calmer second match on a new host did not test your change.
Command syntax for a Windows gateway echo and a public control already lives on the methodology page. This note does not restate those commands. Restating them into every page is how the site started to sound like one template. Consoles do not have that command prompt. Their built-in network screen is a different instrument, covered in the next section.
Which pair of readings is allowed to disagree?
Two instruments that disagree are useful. Two instruments that you treat as the same measurement are how a router purchase gets justified by the wrong number. None of the cells below are results from this site.
| Pair | Agreement that matters | Disagreement that should stop you | Instrument you are actually using |
|---|---|---|---|
| Game delay figure vs game loss mark | Both calm, or both upset, under the same server name. | Delay calm while the loss mark moves, or the reverse. Do not crop one of them out. | The game’s own counters. This is the primary instrument while the match exists. |
| Game loss mark vs a local gateway echo | Both worsen on the bad link and both ease when you change only that link. | The gateway stays quiet while the game marks loss. The house echo is not the game. | ICMP to the router. Some routers never answer. Silence is not proof of a broken cable. |
| Game delay figure vs a public echo | You only asked whether the wider path moved at the same time. | The public echo improves and the game does not, or the game improves because you were handed a different host. | ICMP to a public address. It is not the match, and it is not a loss mark. |
| A throughput grade vs any row above | Almost none. Bulk transfer and the game shape answer different questions. | You were about to buy something because the grade moved and the loss mark did not. | A bulk transfer toward a nearby test server. Put it down if the complaint is a loss mark or a flat delay. |
When to switch measurement method
When do you put the in-game counter down?
Stay on the game’s counters while they move in a way you can describe. Switch instruments only when those counters cannot see the complaint, or when they disagree and you need a second view to say which layer moved.
Switch to a local gateway echo, using the steps already written on the methodology page, when you need to know whether the house link is involved and the game will not show a loss mark. Remember the limit printed there: a router may ignore the echo, and an echo is not a game packet. If the gateway stays quiet and the loss mark keeps ticking, you have not cleared the house, and you have not proved the provider either. You have learned that this echo cannot see the hole.
Switch to a public control when the gateway looks steady and the question is whether the wider path moved. If the public control moves and the game does not, you learned that the control and the game are different destinations. Go back to the game’s server name. Do not keep retesting the public address hoping it will confess for the match.
Switch away from network counters entirely when the picture hitches and every network mark stays still. That is a client frame problem. A loss story will waste the evening. Valorant and Tarkov already talk about a calm network graph beside a hitch, in those games’ own HUD words. Use them for the labels. Do not treat them as a second copy of this note. WoW is the page where Home and World can move separately. Genshin is the page where a phone and a co-op session can be the same moment. Those are session facts, not the shape definitions on this page.
Switch to the console NAT note when the match never forms, the invite fails, or voice is one-way, and the delay figure is not the complaint. A NAT letter will not explain a loss mark on a match that already connected. Switch to the evening-queue note when the jump is locked to a transfer. Switch to the Wi-Fi note when the only question left is the last hop inside the house.
Do not cite the August 19 web-edge record as a loss measurement. That file counted replies from web and control hosts on one tunnel. It is one page, for a different question, and it did not include a game loss mark.
Stop the pass when any of these happened
- You changed the server, the radio, and an upload in the same sitting. The row is void.
- People who do not live in your house see the snap at the same second. Your cable is a weak explanation. Keep the match or instance id for the publisher, not for a router receipt.
- The throughput grade improved and the loss mark did not. The grade was the wrong instrument. Stop tuning it.
- The picture hitched and the network marks stayed still. Leave the network checks. You are in a client problem.
If you want a short private classification before you fill the blank log, Diagnose lag asks you to pick a shape first. It does not watch your loss mark, and it does not store the answers.
Questions readers ask after mixing the labels up
Can a high delay and missing packets show up in the same match?
Yes. A far server can sit on top of a link that also drops traffic. Write down both shapes. Clearing one does not automatically clear the other, and a cropped screenshot of the delay figure hides the loss mark.
Does a throughput grade measure missing game packets?
No. A speed test moves bulk data toward a nearby test server. The grade can look healthy while a game drops small, frequent packets, and it can look poor while a game that needs little throughput stays steady.
Is delay variation the same thing as packet loss?
No. Variation means the delay is uneven. Packet loss means some data never arrives. A spike is a delay jump. You can have an uneven delay with every packet still delivered.
If only one game shows a loss mark, is the whole line at fault?
Not from that alone. Keep the server or session name, then see whether a second real-time app fails in the same minute. One title and one session, with everything else calm, is a weak case against the provider.
Did the August 19 collection measure in-game packet loss?
No. It counted ICMP replies from web and control hosts on one tunnel. Missing game packets were not in that file. The record has its own page and is the wrong instrument for a hole in a match.
Editorial log
November 5, 2026. First publication by Jay Fan. No packet-loss capture is attached. The tables are reading guides. Corrections: [email protected].