Access • Core & Peering • NOC • Revenue Systems
ISP Operations
This is the home turf of the practice. We have spent two decades inside operator networks across Africa — starting on the NOC floor, moving through core design and peering, and into the billing stack that turns packets into revenue.
We run ISPs end-to-end — because we have.
01 — One System
An ISP Is One System
An ISP is not a collection of departments — it is one system. The access network, the core, the operations discipline, and the revenue stack live or die together. A clean BGP design does not save you if RADIUS drops sessions at peak; a capable NOC cannot compensate for a last mile that was never engineered; billing leakage quietly erases the margin that good network engineering earned.
Most consultancies pick one layer and stop there. We support every layer, because the failures that hurt operators almost never respect the boundaries between them. When we trace a churn problem, we are as likely to end up in a duplicate NAS entry or an unmonitored backhaul link as in the access gear the ticket blamed.
The pages in this section map the operational areas we work in. Each one stands alone, but they are written from the same conviction: the operators that win are the ones that treat the whole ISP as a single engineering problem.
24/7/365 Technical & Monitoring Support for MikroTik-Powered ISPs
A long-term monthly retainer — your NOC, your escalation path, and your RouterOS specialists, on contract.
Most WISPs and fibre ISPs across the region run on MikroTik/RouterOS — and most run it with a small team that cannot credibly cover nights, weekends, and public holidays. That gap is where subscriber churn is made: the 2 a.m. BGP flap nobody sees until morning, the queue tree that quietly throttles the whole estate, the upgrade that bricks a CCR at the core.
As a MikroTik partner we close that gap contractually. HCS provides round-the-clock technical and monitoring support on a long-term monthly basis — engineers who know RouterOS at the config-line level, backed by our own Helix Cloud NMS platform for fleet monitoring, automated configuration backup, versioned upgrades, and secure remote access. You get a NOC without building one.
Monitoring & Response — Round the Clock
- 24/7/365 monitoring of routers, links, and services with alerting to a staffed escalation path
- Incident response under agreed SLA — acknowledgement, diagnosis, and remediation targets in the contract
- Proactive fault detection: link degradation, CPU and memory pressure, interface errors, and capacity ceilings
- Outage handling with root-cause write-ups, not just service restoration
- Emergency change support during maintenance windows, weekends, and holidays
RouterOS Engineering & Operations
- RouterOS configuration, hardening, and version-managed upgrades across the fleet (CCR, CRS, RB, CHR)
- Routing engineering: BGP, OSPF, MPLS/VPLS, route filtering, RPKI and IRR hygiene
- Subscriber-plane operations: PPPoE, hotspot, RADIUS/AAA, address pools, and session troubleshooting
- Traffic engineering and QoS: queue trees, CAKE/FQ-CoDel, bandwidth management, and peak-hour tuning
- Firewall, NAT, and security hardening — including management-plane isolation and DDoS mitigation at the edge
- Automated configuration backup, change tracking, and rapid restore via Helix Cloud NMS
Growth, Advisory & Enablement
- Capacity planning and traffic forecasting ahead of the congestion, not after the complaints
- Network expansion design: new PoPs, backhaul, last-mile, and upstream/peering strategy
- Migration and upgrade planning — including MikroTik-to-carrier-grade transitions where growth demands it
- Second-line escalation for your own support team, with knowledge transfer built in
- Mentoring and structured training so your engineers grow rather than stay dependent
- Quarterly network health reviews with a prioritised remediation list
- Monthly retainer
- Long-term contract
- Defined SLA & response targets
- Named engineers
- Remote-first, on-site when needed
- MikroTik partner
Scoped to your fleet size and coverage requirements. Commercials are discussed privately — start with a conversation about what you are actually running.
02 — Operations
What We Support
The operational layers of an ISP — each with its own page
03 — Track Record
Why HCS for ISP Work
None of this is theoretical. Every claim below traces to work we have done inside operator networks.
- We started where ISPs actually run: on the NOC floor at EdgeNet in 2005, working live subscriber networks before ever drawing an architecture slide.
- Satellite upstream operations at InterSAT, coordinating connectivity across Nairobi, London, and Washington hubs.
- As team lead at KDN/Liquid, we delivered the first Google Global Cache in East & Central Africa, planned submarine capacity on SEACOM and TEAMS, and built peering at KIXP, JINX, and LINX — growing transit from 60 Mbps to over 3 Gbps in 18 months.
- At Belgium Satellite Services, we supported ISPs across West, East, and Central Africa, ran distribution for 73 BBC partner stations, and recovered a 7.3m earth station for the UNSOA mission.
- We redesigned the network of SkyTrend, a CAK NFP-licensed ISP, for nationwide expansion.
- For DSI in the DRC, we delivered a full carrier-grade network overhaul — including AfriNIC IP and ASN origination — and trained the team to run it.
- Our delivery is backed by partnerships with Cisco, MikroTik, Cambium Networks, Microsoft, Google Cloud, and AWS — the vendors ISP networks are actually built on.
Start With Your Network as It Actually Is
A Phase 0 Review looks at your ISP as one system — access, core, operations, and revenue — and tells you where the real problem lives before anyone proposes a fix.