Packet loss in Call of Duty on South African servers is usually caused by unstable home networks, bufferbloat, or poor routing to JHB-hosted infrastructure. Diagnose using WinMTR, confirm whether loss occurs before or after local peering, then fix LAN congestion or escalate appropriately.
What the Problem Means
In Call of Duty, packet loss causes delayed hit registration, rubberbanding, sudden player position correction, and inconsistent damage output. Unlike pure latency (ping), packet loss means some data packets never reach the game server. In South Africa, most Call of Duty traffic for local matchmaking routes through Johannesburg-based infrastructure, typically via major peering exchanges such as NAPAfrica and Teraco. If loss occurs before or at these exchanges, it is usually network-related. If it occurs after, it may be server-side. Packet loss must be located, not guessed.
Why Packet Loss Happens on SA Servers
Packet loss in Call of Duty typically originates from one of four layers:
1. Home LAN Instability
- WiFi interference
- Weak signal strength
- Mesh node latency spikes
- Powerline noise
- Competitive gaming should always use Ethernet where possible
2. Bufferbloat During Upload Saturation
When uploads (cloud backups, streaming, updates) saturate the line, routers queue packets excessively. This increases latency and causes dropped packets. See: What Is Bufferbloat and How to Fix It
3. ISP Routing or Peering Instability
If packet loss appears at or before peering exchanges (NAPAfrica / Teraco), it may indicate congestion or routing inefficiency.
4. Game Server-Side Issues
If all hops are stable until the final hop (Call of Duty server), the issue is outside your ISP's network.
Step-by-Step Fix
Switch to Wired Ethernet
- Eliminate WiFi variables first.
- Avoid Powerline if possible.
- Connect directly to router LAN port.
- If loss disappears, the issue was WiFi instability.
Check for Upload Saturation
- Pause cloud backups.
- Pause game downloads.
- Stop streaming on other devices.
- Run a latency test while no one else is using the line.
- If packet loss disappears, it is likely bufferbloat.
Run WinMTR to the Game Server Region
- Download WinMTR and test toward a stable South African IP (not a random international host).
- Run for at least 5 minutes while in-game.
- Look for: consistent packet loss starting at hop 1 (LAN/router issue), loss beginning mid-route before peering (ISP path issue), or loss only at final hop (server-side issue).
- See: How to Interpret Traceroute Results for Packet Loss
Identify Where Loss Starts
- This step prevents false escalation. Use the table below to match your findings to the correct action.
Reboot Network Devices Properly
- Power off router.
- Wait 60 seconds.
- Power back on.
- Allow full sync before testing again.
- Do not repeatedly reboot during testing.
Packet Loss Location Guide
| Where Loss Begins | Likely Cause | Action |
|---|---|---|
| Hop 1 (Router) | LAN congestion | Fix router / wired connection |
| Before NAPAfrica / Teraco | Routing issue | Provide trace to ISP |
| At Peering Exchange | Congestion | Escalation may be required |
| Final Hop Only | Game server | Wait for server stabilisation |
Definition
Occurs when data packets travelling between your device and the game server fail to reach their destination. In gaming, even 1–2% sustained packet loss can cause visible rubberbanding, inconsistent hit detection, and unstable gameplay — especially in fast-paced titles like Call of Duty.
When to Escalate
Escalate only if you are on wired Ethernet, no background traffic exists, WinMTR shows sustained packet loss before or at local peering, and the issue persists across multiple sessions. Provide: WinMTR log (5+ minutes), time of testing, and server region selected in Call of Duty. If loss appears only on the final hop and other traffic is stable, escalation will not resolve it — it is likely server-side.
Additional South African Considerations
Most SA Call of Duty traffic routes through Johannesburg. CPT players will naturally see slightly higher latency due to physical distance. Evening congestion can amplify routing instability if uploads are unmanaged. International routing (if matchmaking fails to find an SA server) will increase latency dramatically but does not always cause packet loss. If you are unsure whether your latency is normal, review: How to Test Gaming Latency Properly