Measure the baseline
PingReducer sends a burst of timed probes along the default route and records round trip, jitter and loss. This is the number everything else is compared against, and it is kept in the report.
Ping has two parts: distance and congestion. Distance is physics, and the app cannot beat it. Congestion is routing, and that is the part worth fixing.
PingReducer sends a burst of timed probes along the default route and records round trip, jitter and loss. This is the number everything else is compared against, and it is kept in the report.
The same probes run against nearby backbone nodes. The app compares the full path, not just the node itself, because a close node on a bad route is still a bad route.
Only the selected game's traffic is forwarded. The rest of the machine keeps its normal connection, which is why downloads and streams are unaffected.
Outgoing packets are spaced rather than released in bursts. The average latency stays about the same, the variance drops, and the game's prediction improves.
Every sixty seconds the route is re-scored. A sustained rise in jitter or a lost path triggers a switch to the next best node without restarting the game.
No tool beats physics. If your traffic is already taking the shortest path to a nearby server, there is nothing left to remove, and the app will say so instead of pretending.
In those cases the report shows a flat or negative delta, and the app leaves the default route in place.
Shortest bar wins. The app keeps testing after it selects.
The probe takes thirty seconds and the report tells you plainly whether routing helps.