Traceroute shows each hop between you and a destination server. To interpret packet loss correctly, identify where loss begins and whether it continues through downstream hops. Loss that persists indicates real packet loss. Loss that stops at the next hop is usually ICMP filtering.
What Traceroute Actually Shows
Traceroute maps the path your packets take from your device to router to ISP to peering exchange to game server. Each step is called a hop. For each hop, traceroute displays latency (ms), packet response timing, and potential packet loss. In South Africa, most locally hosted gaming traffic routes through Johannesburg infrastructure. CPT players route to JHB first before reaching game servers. Traceroute allows you to see where latency increases, where packet loss begins, and whether routing exits South Africa. For tool usage guidance, see: How to Use WinMTR for Gaming Troubleshooting
Why Packet Loss Must Be Interpreted Carefully
Packet loss in traceroute can appear in two ways: real packet loss (affects gameplay) and ICMP filtering (does not affect gameplay). Many intermediate routers de-prioritise or rate-limit diagnostic traffic (ICMP). This can create false packet loss in traceroute results. The key rule: packet loss must continue through downstream hops to be considered real.
How to Interpret Packet Loss
Step 1: Identify the First Hop
- Hop 1 is usually your router.
- If packet loss appears here: LAN instability is likely, WiFi interference may be present, or router CPU congestion may exist.
- Switch to Ethernet before further interpretation.
Step 2: Look for Loss Propagation
- If packet loss appears at Hop 3 and continues through Hop 4, 5, 6, and the final hop → real packet loss.
- If packet loss appears at Hop 3 and disappears at Hop 4 → likely ICMP filtering.
- Loss must propagate forward to matter.
Step 3: Check Where Latency Spikes Begin
- At Hop 1 → local issue.
- Early ISP hops → upstream routing issue.
- After leaving South Africa → international routing.
- Only at final hop → server-side behaviour.
- See: What Is NAPAfrica and Why It Matters for Gamers
Step 4: Detect International Routing
- Signs that traffic has left South Africa: sudden 120ms+ latency jump, foreign IP addresses, submarine transit nodes.
- International routing increases baseline latency and jitter.
- If packet loss appears after international transition, it is likely transit congestion.
Step 5: Evaluate Final Hop
- If all hops are stable and packet loss appears only at the final hop, this may be server-side ICMP filtering or game server response policy.
- If gameplay remains stable, this is not actionable packet loss.
Interpretation Table
| Observation | Meaning | Action |
|---|---|---|
| Loss at Hop 1 | LAN instability | Use Ethernet / check router |
| Loss begins early and continues | Real upstream packet loss | Provide trace to ISP |
| Loss appears at one hop only | ICMP filtering | Ignore if not propagated |
| Latency spike after SA | International routing | Check server region |
| Stable route, high final hop | Server policy | Not ISP-controlled |
Understanding ICMP Filtering
Some routers de-prioritise diagnostic traffic. This can show artificial packet loss at a hop, but no real loss continues afterward. If packet loss does not persist to the final hop, it is not affecting gameplay.
Definition
Used by traceroute to measure latency at each hop. Some routers deprioritise ICMP responses, which can appear as packet loss in diagnostics but does not affect actual game traffic.
South African Routing Patterns
Typical local behaviour: gradual latency increase from CPT to JHB, stable mid-route hops, no early packet loss. International routing: sudden triple-digit latency, higher jitter, possible congestion-related packet loss. Local games hosted in Johannesburg should not show international routing patterns.
Common Misinterpretations
- Seeing 100% loss at one hop and assuming failure
- Escalating based on a 30-second test
- Testing over WiFi
- Confusing server-side filtering with network instability
- Traceroute requires propagation analysis, not single-hop interpretation
When to Escalate
Escalate only if you tested via Ethernet, the test ran 5+ minutes (preferably via WinMTR), packet loss persists across multiple downstream hops, and loss appears before local peering. Do not escalate single-hop ICMP loss, final-hop-only loss, or international routing expected for that game.