terawiz Network · NOC · Hosting
Live wall · replayed Johannesburg · since 2009

Networks,
watched.
Systems, run.

Terawiz designs, builds and operates networks for wireless ISPs, transit operators and integrators, and monitors them so the numbers can be trusted. Hosting, email and the software that comes out of running all of it.

Start a conversation → See the work →

What we run

01 / 04
01

Networks & NOC

MikroTik and Ubiquiti estates: fibre, 60 GHz and licensed backhaul, OSPF and BGP, WireGuard, service tunnels per client, and the watching.
02

Monitoring & reporting

LibreNMS, dashboards for the wall, an hourly report that reasons about root cause, monthly availability in the carrier’s format.
03

Hosting & email

A Debian server in South Africa we patch and answer for. Migrations, DKIM and DMARC, backups, incident response.
04

Software & apps

Dashboards, collectors and APIs in Python and Node. iOS and Android apps since 2011.

Selected work

02 / 04
Service-tunnel health model2026 One event, not 125 faults Regional wireless ISP, North West The operator's dashboard kept reporting 125 of 126 client services down. Thirty-nine of them were. We built a state model that needs a second witness before it calls a fault, and carried it through to the hourly report and the WhatsApp dispatch. 39real faults, out of 125 reported Read the case → Availability dashboard2026, ongoing A dashboard built for the wall Bus rapid transit operator, Johannesburg Station switches, cameras, biometric readers, fare collection and microwave links on one screen in the monitoring centre, with the measurement rules written down and the raw data a click away for staff. 94stations · 408 devices placed Read the case → Configuration recovery2026 Rebuilding a core router from yesterday's recon PoP router anchoring 128 client tunnels The PoP router died with no current export on file. The previous morning's read-only recon had 48 sections of its configuration. We turned that into a restore script, with every assumption and gap written down. 128tunnels restored with their IDs Read the case →

All work, including the smaller things →

How we work

03 / 04
P—01

The same engineers, start to finish.

The engineers who scope the job design it, build it and carry the phone for it afterwards. Nothing is lost between a sales team and a delivery team, because there isn’t one.

P—02

Read-only until it isn’t.

On a live network we look before we touch. Changes are staged as files, backed up and reversible, and the operator applies them unless they’ve asked us to.

P—03

Numbers you can check.

A dashboard that says 125 sites are down when 39 are is worse than no dashboard. Every state needs a second witness, carries a confidence, and links to the raw data.

P—04

Built to be handed over.

Repos, runbooks and the reasons behind decisions ship with the work. You should be able to run it without us, and most clients choose not to.

Next step 04 / 04

Something that needs looking at?

Tell us what you’re building, or what keeps breaking. You’ll get a straight answer on whether we’re the right people for it, and a first look is usually read-only.

Start a conversation →