Field note · October 31, 2026 · Jay Fan
When ping spikes in the evening, name the queue before you name the ISP.
"It gets bad after dinner" can be three different mechanisms wearing one sentence. A full uplink in the house, a busy hour on the path beyond the house, and a game server that was always far away do not respond to the same next check. This note separates them. It does not publish an evening trace from our own line. We have not kept one.
Three patterns that should not share a fix
- Pattern A — locked to an upload
- The game is playable until a cloud backup, a livestream, a video call or a console install starts sending. The in-game graph jumps while that transfer runs and settles when the transfer stops. The selected server did not change. This is the classic shape of a queue at the slowest outbound link: small game packets wait behind a large send. People call the standing version of that problem bufferbloat. The bufferbloat project introduction is a useful definition. It is not a score we adopt, and a third-party test site is not our measurement.
- Pattern B — locked to the clock, house already quiet
- Nothing large is uploading. The same game, on the same server choice, is calm at lunch and spiky at the same evening hour across more than one day. Wired and wireless look similar. The lead is outside the house: other customers, a peering path, or a game region that is simply busier. Pausing a backup that was not running will not touch it. Repeating the session on a weekend morning tells you whether the clock is real.
- Pattern C — high and steady all day
- The number is large at noon and large at night, and it does not jump when the house is idle. That is distance or server placement until proven otherwise. Valorant's picker, WoW's realm, Genshin's account server and a Tarkov launcher region are the first facts to write down. An evening story is the wrong story. A queueing fix will not move a stable far-away baseline.
Pattern A and Pattern B can stack. A house that uploads in the evening on a path that is also busy will look terrible, and a single pause test will only explain the part you paused. Write both observations instead of forcing one label.
The only experiment this page trusts for Pattern A
Pick the game moment that just failed. Confirm the server, realm, map or co-op host, and that you can play a comparable moment again within a few minutes. Start the upload that you suspect, or catch it while it is already running, and watch the game's own spike, loss mark or rollback. Then pause that one transfer. Leave the radio, the VPN and the server picker alone. Play the comparable moment again.
If the graph settles while the server name stays put, Pattern A earned the lead. Turn the transfer back on later, when you can stand it, and see whether the spike returns. A result that only happens once is a hint. A result that returns with the upload is a reason to keep large sends off the uplink during play, or to look at whether the router can schedule small packets ahead of bulk ones. This page does not rank firmware and does not tell you a specific box will do it. If the vendor documents a queue or SQM control, that document is the source for the knob. Your before-and-after note is the source for whether your symptom cared.
If the graph does not settle, you do not have Pattern A for that session. Stop toggling unrelated settings. Move to the timetable and ask whether the clock, not the upload, is the pattern.
A blank evening timetable
Fill one row per session for a few days. Do not convert empty cells into zeroes. The point is the clock and the house, side by side, so Pattern B cannot disguise itself as Pattern A.
| Local time | Game and server context | What the house was sending | Link | What the game showed | Pattern you suspect |
|---|---|---|---|---|---|
| Example shape | Name the picker, realm, map or host | Idle, call, backup, or install | Cable or wireless | Steady, spike, loss mark, or hitch | A, B, C, or mixed |
| Day 1 | |||||
| Day 2 | |||||
| Day 3 |
Stop rules
The picture hitches and the network graph does not
That is a client frame problem. An upload pause is the wrong tool. Tarkov's freeze-without-a-warning branch and Valorant's flat network graph inside utility are the game-shaped versions of this stop.
The number is high before anyone uploads, every time of day
Treat it as Pattern C. Write the server choice. A queue story will waste the evening.
Everyone in the raid or the party sees it at the same second
Your uplink is a weak explanation for a shared timestamp unless the whole party is in your house. Keep the instance, the map or the match id for the game's support channel.
You changed region, radio and an upload in the same ten minutes
The timetable row is void. Keep it, mark it void, and do not let it decide a router purchase.
Where this meets a specific game
Use the game page when the vocabulary of the HUD matters. Use this page when the question is the house and the clock. Valorant cares whether Network RTT jumped on the same Riot server while a housemate uploaded. Tarkov cares whether rollback lined up with a send, or with one raid and a shared timestamp. WoW cares whether Home and World climbed together under a backup, which is a different sentence from World climbing inside one dungeon. Genshin cares whether a phone download and a co-op session were the same moment.
A wireless comparison is a separate protocol, written up in Wi-Fi versus Ethernet. Do not run that protocol in the same pass as the upload pause. The August 19 web-edge file is also the wrong citation here: it was a tunnel on Ethernet, it did not include an evening series, and it did not include a bulk upload. It lives at one URL for a different question.
If you want a short private classification before you build the timetable, start with Diagnose lag and pick spikes rather than a stable high number. The tool does not watch your uplink and it does not store the answers.
Editorial log
October 31, 2026. First publication by Jay Fan. Added so "pause the upload" would have one long explanation instead of a repeated sentence inside every game guide. No household evening capture is attached. If we run one later, it will get its own dated file, the way the August collection did. Corrections: redmedia24@yeah.net.