Gamer-Centric Support & Intelligent Diagnostics

How UrbanX's automated diagnostic system collects line metrics, runs layer-by-layer checks, and classifies faults before a human agent is involved. Covers optical power polling, latency baseline comparison, and fault-domain classification.

End-to-end lifecycle of a fibre support ticket — from initial logging through automated triage, ISP-side diagnostics, FNO escalation (if required), and resolution confirmation. Includes expected timelines at each stage.

How continuous line monitoring detects degradation before users notice. Covers threshold-based alerting, proactive ticket creation, and how automated systems reduce mean time to resolution on South African fibre.

The difference between ISPs that wait for you to report a fault and those that detect it first. Explains proactive monitoring architecture, alerting pipelines, and why it matters for gamers.

How NAT type (Open, Moderate, Strict) affects multiplayer connectivity and why support agents need to know your NAT status. Covers CGNAT detection, port forwarding, and UPnP configuration on SA fibre.

The diagnostic workflow UrbanX uses to isolate gaming-specific packet loss — from home network checks through ISP backbone analysis to FNO last-mile verification. Includes the tools and thresholds used at each layer.

How support teams determine whether lag or disconnects are caused by the game server, the ISP network, or the player's home setup. Covers diagnostic markers, traceroute analysis, and server status verification.

The exact data points — game, server region, timestamps, traceroutes, speed tests, and ONT photos — that reduce gaming ticket resolution time. Structured template for filing high-quality support requests.

The criteria and process for escalating a fault from ISP-level support to the Fibre Network Operator. Covers fault-domain classification, required evidence, and what happens once the FNO accepts the ticket.

Expected repair timelines for each major South African FNO — Vumatel, Openserve, MetroFibre, Frogfoot, and Octotel. Covers SLA benchmarks, common delay factors, and what to do if your fault stalls.

Explaining the formal FNO escalation ticket — what it contains, who creates it, how it differs from an ISP support ticket, and how to track its progress through to resolution.

Understanding when and how service credits apply for fibre downtime in South Africa. Covers SLA-based credit policies, how to request credits, and what documentation is typically required.

A pre-call checklist for gathering the diagnostic data that accelerates ticket resolution. Covers ONT light checks, wired speed tests, traceroutes, and timestamps — everything support will ask for.

The specific logs, traces, and test results needed to prove packet loss to your ISP. Covers WinMTR captures, PingPlotter exports, continuous ping logs, and how to present them for fastest escalation.

Step-by-step self-service diagnostic workflow — ONT LED check, patch lead inspection, wired speed test, traceroute, and continuous ping — to classify your fault before contacting support.