The UrbanX Knowledge Hub
Structured guides on fibre diagnostics, low-latency gaming, and intelligent support — written by network engineers, specific to South Africa.
Explore by Topic
Each series covers a distinct fault domain — from physical fibre infrastructure through network performance to support processes.
FNO Troubleshooting & Fibre Diagnostics
Physical-layer fault isolation across Vumatel, Openserve, MetroFibre, and Frogfoot. ONT signal diagnostics, light-level interpretation, and escalation procedures specific to South African FNO infrastructure.
Top Guides
Gaming Performance & Low Latency
Network-layer optimisation for competitive gaming. Jitter budgets, buffer bloat mitigation, QoS configuration, and route analysis between SA game servers and international endpoints.
Top Guides
Gamer-Centric Support & Intelligent Diagnostics
Process-layer support intelligence. Automated diagnostic workflows, ticket escalation logic, self-service tooling, and structured troubleshooting frameworks built for technical users.
Top Guides
Three layers. One methodology.
Every guide in the Knowledge Hub follows a structured fault-isolation approach. We diagnose issues layer by layer — from the physical fibre infrastructure through network performance to support resolution processes.
Physical Layer
Where fibre meets hardware
The physical layer covers everything from the fibre cable entering your premises to the ONT (Optical Network Terminal) that converts light into an Ethernet signal. Most South African fibre faults originate here — dirty connectors, damaged drop cables, or degraded optical power levels that your FNO must resolve.
What you will learn
Network Layer
Where packets travel and latency lives
Once your signal is clean, performance depends on how packets traverse your home network, your ISP backbone, and international peering points. For gamers, this layer determines ping, jitter, and packet loss — the difference between a crisp 20ms connection to Johannesburg servers and an unplayable 200ms mess.
What you will learn
Process Layer
Where troubleshooting becomes resolution
Even with the right data, getting a fault resolved depends on how you engage support. This layer covers structured escalation — logging tickets with the correct diagnostics, understanding FNO vs ISP responsibility, using self-service tools, and knowing when to push for a physical line test versus waiting for a remote fix.
What you will learn
Need Help Now?
Use our diagnostic tools to identify faults, or contact support with a structured ticket for faster resolution.