24x7 NOC for ISPs without Internal Team

What a NOC is and why your ISP needs one

A NOC (Network Operations Center) is the structure responsible for continuously monitoring the ISP's infrastructure, identifying failures before they become subscriber complaints, and coordinating incident response — including overnight, on weekends and holidays.

Small and mid-sized ISPs rarely manage to sustain this cycle with an internal team. The technician who installs, configures and maintains the network ends up also covering the overnight shift. This leads to burnout, unpredictable response times and operational risk concentrated in a single person.

RASYS operates as an outsourced NOC: we monitor your infrastructure using the same tools and routines as larger network operations, but on a monthly plan accessible to ISPs with 1,000 to 100,000 subscribers.

Human coverage during business hours and client-paged on-call after

Our direct human coverage hours are Monday through Friday, 8:00 to 18:30, and Saturday 8:00 to 12:00. During this window, you talk directly to a RASYS analyst already on active duty — no bots, no escalation queues.

Outside those hours — nights, Sundays and holidays — monitoring stays active. When you need us, you signal in the group: the bot relays the call to the on-call engineer via phone and message. The on-call confirms receipt and starts the response directly.

Response time: up to 30 seconds in 95% of critical alerts, always within 5 minutes. This applies both during business hours and during the overnight on-call.

How monitoring works in practice

We set up Zabbix on the ISP's own server with equipment-specific custom templates: border routers (Huawei NE, Juniper MX, Cisco ASR, MikroTik CCR), OLTs (Huawei MA5800, ZTE C320/C600, FiberHome AN5516), aggregation switches and PPPoE authentication servers.

Beyond the Zabbix inside your network, we maintain a LibreNMS instance on RASYS infrastructure for external monitoring — this ensures visibility even when your network is completely unreachable from the inside, which is common during border router failures or upstream link outages.

Grafana dashboards are provided with traffic history, per-link availability and growth trends. Alerts arrive via Telegram or Discord with enough context for the analyst to know what is failing before opening the terminal.

Internal NOC versus RASYS: a direct comparison

Maintaining a real 24x7 internal NOC requires at minimum four network analysts on rotating shifts (to cover shifts, days off and vacation), internal monitoring infrastructure and a continuous training process. Monthly cost easily exceeds R$ 30,000–50,000 between salaries, payroll taxes and tooling — not viable for regional ISPs.

The RASYS outsourced model distributes that cost across clients while maintaining technical quality. Our analysts work with multiple ISPs in parallel, generating cross-client experience: the problem you are facing today has likely already been solved at another client. This reduces diagnosis time and increases the precision of corrective actions.

Specialization is also a real differentiator. An internal NOC at a regional ISP tends to have generalists. RASYS has exclusive focus on internet service provider infrastructure — BGP, GPON, PPPoE, CGNAT, IPv6 — without divided attention across other segments.

Incident management and communication

When an incident is identified, the RASYS analyst opens the response, documents actions in real time and keeps the ISP's responsible contact informed until resolution. We do not wait for you to ask what is happening — we send updates as the situation evolves.

Incidents requiring remote access are handled via the RASYS VPN, with IPs authorized on the client's network. For actions that carry risk of impact — such as a BGP route change or restarting a critical device — we confirm verbally or in writing before executing.

Which ISP profile benefits most

The RASYS outsourced NOC model is ideal for ISPs with 1,000 to 100,000 subscribers that have moved past fully informal operations but do not yet have the scale to justify a full 24x7 internal NOC team.

We also serve ISPs that have an internal technical team focused on field work (installations, maintenance, expansion) and need a NOC back-office for core and border network — dividing responsibilities clearly without overloading the local team.

ISPs in rapid growth phases benefit especially: response capacity does not depend on hiring and training more internal analysts — it scales with the RASYS plan as the operation grows.

How we get started

The initial conversation is at no cost. We walk through how we set up active monitoring on your infrastructure and discuss the appropriate coverage scope for your size.

If it makes sense to move forward, before we start operating we run the network onboarding: we collect all access credentials, retrieve and review existing backups, rotate every password, and only then go live — with a fresh backup guaranteed. Then we set up Zabbix on the ISP's own server, integrate alerts into your channel and begin active monitoring.

We work on a monthly plan — no one-off projects. The continuous model is the only one that guarantees the full cycle of monitoring, threshold adjustment and coverage improvement over time.

Initial conversation, no commitment — see also: Zabbix monitoring, BGP for ISPs.