Structured guides on fibre diagnostics, low-latency gaming, and intelligent support — written by network engineers, specific to South Africa.
Each series covers a distinct fault domain — from physical fibre infrastructure through network performance to support processes.
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.
Network-layer optimisation for competitive gaming. Jitter budgets, buffer bloat mitigation, QoS configuration, and route analysis between SA game servers and international endpoints.
Process-layer support intelligence. Automated diagnostic workflows, ticket escalation logic, self-service tooling, and structured troubleshooting frameworks built for technical users.
LAN-layer optimization for South African gamers. Ethernet infrastructure, WiFi 6/7 deployment, brick-wall penetration, router CPU bottlenecks, and home network architecture for zero packet loss.
Throughput-layer mastery for SA creators. Symmetrical fibre architecture, OBS bitrate calibration, NAS editing workflows, FUP navigation, and zero-latency streaming under heavy household load.
Edge-layer hardening for SA gamers. CGNAT navigation, port forwarding security, DDoS mitigation, DNS optimization, Mini-UPS dimensioning, and surviving load reduction reconnect storms.
Understand fibre coverage, orders and home installations in South Africa. Prepare your property and know what to check before handover.
Understand fibre migrations, line releases, moving address, contracts, cancellation, billing and complaints in South Africa.
Practical South African guides to browsing privacy, phishing, passwords, passkeys, MFA, account recovery, data breaches and safer gaming.
Every guide in the Knowledge Hub sits at a known layer, and each layer answers a different question. We work outward from the fibre itself — through home network, bandwidth and the network edge — to the coverage, installation and account processes around it, and finally to the person using it.
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.
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.
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.
Where your own hardware decides the outcome
A clean line still has to cross your house. Cabling, radio bands, router silicon and heat all sit between the ONT and the device you actually play on, and every one of them can undo a perfect fibre connection. This layer covers the part of the network you own outright.
Where uploads and households compete
Streaming, uploading and a house full of devices ask a different question of a line than gaming does. This layer covers upload capacity, concurrency and the shaping myths that surround them — matching an encoder bitrate to a real line, and stopping one download from taking the whole house down.
Where your network meets the public internet
The edge is the boundary your router defends. NAT type, open ports, DNS choice and power continuity all live here, and each one is a trade between reachability and exposure. This layer covers hardening that boundary without breaking the connectivity a game needs.
Before the service exists at all
Everything above assumes a working line. This layer covers how one gets built — what a coverage result actually confirms, who owns each step between the FNO and the ISP, what permissions a build needs, and what to check before the installer leaves your property.
Where the account changes, not the cable
Switching provider, moving house or changing package is an administrative event on a line that already exists. This layer separates the physical connection from the contract attached to it — migrations, line releases, equipment ownership, notice periods and where a billing dispute goes next.
Where people, not packets, are targeted
The most damaging incidents rarely involve the network at all. A convincing message, a reused password or an exposed recovery address does the work instead. This layer covers what an ISP can and cannot see, how to recognise impersonation, and what to do in the hours after an account or dataset is compromised.
Use our diagnostic tools to identify faults, or contact support with a structured ticket for faster resolution.