UrbanX diagnoses gaming packet loss by isolating where loss begins — LAN, ISP core, peering, international routing, or access layer — using WinMTR logs, traceroute analysis, and ACS telemetry before determining whether escalation is required.
Why Packet Loss Must Be Classified Before Escalation
Packet loss can originate from multiple layers:
- Customer LAN
- Router instability
- ISP core congestion
- Peering or routing instability
- International transit
- Access-layer fibre fault
- Game server filtering
Escalating without classification causes FNO rejection, delayed repair, and misdiagnosis. UrbanX follows a structured diagnostic flow before escalation.
Step-by-Step Packet Loss Isolation Workflow
Validate Testing Method
- Support first confirms: testing performed via Ethernet, WinMTR run for 5–10 minutes, no heavy upload during test, and correct destination selected.
- Incorrect testing produces false packet loss.
- For interpretation guidance, see How to Interpret Traceroute Results for Packet Loss.
Identify Where Loss Begins
- UrbanX analyses the WinMTR output: Loss at Hop 1 → LAN/router instability. Loss begins at early ISP hops → ISP core issue. Loss appears mid-route near peering → routing instability. Loss appears after international transition → transit congestion. Loss only at final hop → server-side filtering.
- Loss must propagate through downstream hops to be considered real.
Cross-Check ACS Telemetry
- Support validates: router CPU load, WAN sync state, reconnect frequency, interface error counters, and historical disconnect logs.
- If telemetry shows stable WAN and no interface errors, access-layer fault is unlikely.
Determine Routing Context
- In South Africa: locally hosted games route through Johannesburg infrastructure. CPT players route to JHB before reaching servers. International routing shows triple-digit latency jumps.
- If packet loss appears after leaving South Africa, it is not an access-layer fibre fault.
Classify the Packet Loss
- Classification determines escalation path. Escalation occurs only if access-layer fault conditions are confirmed.
- See escalation boundary: When Does an ISP Escalate to an FNO?
Packet Loss Classification
| Packet Loss Location | Classification | Escalation Required |
|---|---|---|
| Hop 1 | LAN instability | No |
| Early ISP hops | ISP core | Internal resolution |
| Peering exchange | Routing issue | Internal investigation |
| International transit | Transit congestion | No FNO escalation |
| Access-layer sync failure | Fibre fault | Yes |
Key Term: Packet Loss
Occurs when data packets fail to reach their destination. In gaming, even small sustained packet loss causes rubberbanding, desync, and hit registration issues. Loss must be persistent and propagate through downstream hops to indicate a true network fault.
When Packet Loss Is NOT a Fibre Fault
Packet loss does not justify FNO escalation if:
- It appears only on one hop
- It stops at the next hop
- It occurs only internationally
- It occurs only at the final hop
- WAN sync remains stable
Access-layer faults usually include WAN sync failure, device unreachable state, and persistent connectivity drop. Packet loss alone does not equal fibre break.
South African Multi-FNO Context
UrbanX operates across infrastructure owned by:
- Vumatel
- Openserve
- Frogfoot
- MetroFibre
FNOs require validated evidence of access-layer instability before accepting escalation. Incorrect packet loss classification leads to ticket rejection, repair delay, and repeat diagnostics. Structured isolation prevents unnecessary dispatch.
When Escalation Is Triggered
Escalation to FNO occurs only if:
- Packet loss coincides with WAN sync instability
- ACS telemetry confirms signal degradation
- Loss begins before ISP core routing
- Access-layer evidence is consistent
If these criteria are not met, the issue is resolved internally or classified as server-side.
Common Misinterpretations
Classification requires propagation analysis and telemetry cross-checking:
- 1% loss at a single hop is not always real
- Final-hop loss may be ICMP filtering
- International loss does not indicate fibre damage
- Strict NAT does not cause packet loss