Need Solution?
Contact us if you need a solution.
In-service upgrades that keep every session, one command that says what is wrong and where, and a control plane that watches the whole fleet. The subscriber edge should not need a maintenance window.
control-plane gap on a PPPoE upgrade — from 13,315 ms before this work
subscriber re-authentications
sessions preserved through the upgrade
automatic detect-and-restart after a crash
Six functions that between them remove most of the reasons an operator has to log in at all.
Forwarding-plane upgrades have no gap at all. The session plane comes back in under a second with no re-authentication — same sessions, same identities, new software. The same mechanism survives an unplanned crash, not just a planned upgrade.
One command, ten domains, one pass. Every finding is written as Symptom → Cause → Action rather than a wall of counters, so the answer arrives with the diagnosis.
There are 214 settings and you should have to think about none of them. A feature has to prove itself on your traffic before it stays enabled, and nothing is taken away — manual control always wins.
Your running config is not the config you think you have. The platform compares what is actually loaded against what was intended and tells you where they diverged — before the difference becomes an incident.
NOC2 watches every gateway you run from one place, with a five-second live console rather than a report you read afterwards. Nothing sits in the traffic path.
“Is it them, their line, or us?” answered in one search — the internet path and your own queuing separated, so the fault lands with whoever owns it.
Fifteen technical briefs cover operations in detail. These are the ones to start with.
A proof of concept runs on your own x86 against your own traffic. Send subscriber count and busy-hour throughput and we size it with you.
Contact us if you need a solution.