Ping14 September 2026 · Updated 8 October 20265 min read
Playing WARDOGS on 200ms
Every South African plays WARDOGS on roughly 200ms, because the nearest server is in Europe and there is no African region. Most “lower your ping” guides are written by people on 20ms who have never had to. This one is the short list of things that genuinely help from here, and the longer list of things that do not.
Season 2 · 15 October. Our servers move to South African hosts and open to the public with the WARDOGS Season 2 launch, and members and supporters keep their priority access. This guide describes how things work until then; we will update it on launch day. See the countdown.
What you cannot change
Light through fibre from Johannesburg to Frankfurt and back is about 160 to 180ms before any router touches it. That is the floor. A faster fibre package does nothing for it: bandwidth is how much you can move, latency is how long it takes to start arriving, and WARDOGS needs very little of the first. If a product promises to cut your South Africa-to-Europe ping in half, it is lying or it is measuring something else.
The number to care about is not your ping. It is the gap between your ping and the other players’. Twenty-four people on 200ms have a fair match. One person on 39ms in that lobby does not. That is the entire reason a South African community server is worth playing on, and it is the biggest “ping fix” available to you.
Check your route before you change anything
Two South Africans on the same ISP can have a 40ms difference to Frankfurt because one is being routed sensibly and the other is going via London and back. Find out which you are. On Windows, open a command prompt and trace the route to a well-known European host:
tracert -d speedtest.frankfurt.linode.comYou are reading for two things. First, the last few hops: they should settle around 160 to 200ms. Second, any single hop that jumps by 50ms or more and stays there, or a hop that flaps between wildly different numbers — that is where your problem lives, and it is usually inside your ISP or at the point they hand off to Europe. If the total is over 250ms on a wired connection, your route is the problem, not the game, and your ISP’s support line is the fix. Say the word “peering” and give them the trace.
Things that actually help
- A cable, not Wi-Fi. The single biggest improvement most people can make. Wi-Fi adds latency, but more importantly it adds jitter — inconsistent latency — and jitter is what makes 200ms feel unplayable rather than merely slow. If you must use Wi-Fi, 5 GHz, line of sight to the router, and nothing else on it.
- Stop the line being shared. A 4K stream, a console update or cloud backup in the next room shows up in your fights as sudden spikes. Pause them or, if your router has it, put your PC first with QoS.
- Make your frame rate steady rather than high. A stable 90fps beats 140 that dips to 60 in fights, because the game samples your input at whatever rate you are rendering. Cap your frame rate a little below what your machine sustains in a full lobby, and turn off V-sync, which adds input delay on top of the network delay you already have. The specs, if you are deciding whether the machine is the bottleneck.
- Watch jitter, not ping. In-game, glance at the ping readout during a fight, not in the lobby. If it is sitting still at 195, you are fine. If it is bouncing, go back to the cable and the shared-line points above.
- Play where everyone has your ping. Said above and worth saying again: a South African lobby removes the 39ms player, and the 39ms player is the one who was killing you.
Things that do not help
- Gaming VPNs. A VPN is another hop. It helps only when your ISP’s route is broken, which the traceroute above will tell you. If the route is sane, the VPN makes it worse and charges you for it.
- Changing DNS. DNS decides how you find the server, once, before you connect. It has no effect on the latency of a connection that already exists.
- “Network optimiser” software. Registry tweaks and TCP settings from 2009. WARDOGS traffic is not what they touch, and the ones that change anything usually change it for the worse.
- A faster package. See above. 50Mbps is more than the game uses; 1Gbps has the same ping.
How to take fights at 200ms
The honest part: when the whole lobby is on 200ms, the mechanics are fair but the timing is still different from a 20ms game, and playing as if it were not is how you die.
- Hold, do not peek. The player who moves around a corner is disadvantaged by exactly the latency; the player already holding the angle is not. At 200ms that is a fifth of a second of you being visible before you can react. Let them come to you.
- Trade, do not duel. A squad mate who fires half a second after you is a second gun on target during the window where the server has not yet decided the fight. Solo duels at 200ms are coin flips; two-on-ones are not.
- Lead moving targets slightly more than feels right. You are shooting at where someone was a fifth of a second ago. The game compensates for some of that; not all.
- Play the objective. Holding the zone, reviving, transporting — the things the cash economy pays for — are mostly not reaction-time contests. A high-ping player who plays the objective out-earns a high-ping player who hunts kills.
- Third-party the fight. Three factions means every duel has a third side who was not in it. At 200ms, arriving last is a much better plan than arriving first.
What we do on our side
The Boet’s World server is South African only, so the lobby shares one ping rather than one player having a 160ms edge over the rest; the score tick and match settings are tuned for a lobby that is often smaller than a hundred on a weeknight; and the admins are in the match, so “that guy is lagging through walls” is something a human can look at rather than a report that goes nowhere. And we are petitioning BULKHEAD for the only real fix, which is a server on this continent.