Skip to content

Managed operations

Remote NOC

Continuous monitoring of network and services, incident lifecycle management and severity-based escalation.

Architecture

Architecture

  1. 01MonitorMetrics, logs, synthetics
    • Zabbix
    • Prometheus
    • Blackbox
  2. 02DetectThresholds and anomalies
    • Alertmanager
    • Grafana Alerts
  3. 03TriageSeverity, impact, owner
    • Runbook
    • On-call
  4. 04RespondIsolate and restore
    • Change window
    • Rollback
  5. 05ResolveVerify and report
    • RCA
    • SLA report
  6. 06ImproveRules, automation
    • Alert tuning
    • Runbook update
Incident lifecycle — from monitoring through to improvement

Operator consoles

Operator consoles

These exact systems run on the group's own infrastructure — the screenshots are processed before publication.

Blurred Grafana dashboard showing traffic gauges for upstreams and peering sessions.

Bandwidth and peering in real time

Every upstream and every peering session is measured separately, with global and local traffic split apart. Capacity and peering decisions come from this view — not from a hunch.

GrafanaZabbixper-peerIXP
Blurred AS Upstream analyser showing a per-prefix visibility table across three transits.

BGP visibility per upstream

Each prefix and how visible it is through each transit — which upstream propagates which prefix, and in what share. This is how a route leak, a missing announcement or a mis-built policy becomes visible before it becomes an incident. The tool is public on noc.com.ge.

BGPper-prefixRPKIpublic tool
An automated BGP report from four locations — loss and latency per prefix, with a priority verdict at the end.

Global BGP Report — automatic, every day

From four international vantage points — Sofia, the USA, Amsterdam, India — every one of our prefixes is measured for reachability, loss and latency. No human assembles this: the system compares a 3-hour window against a 24-hour baseline, picks out the direction that is degrading and assigns the priority itself — in this frame P1 is India, where RTT passes 190 ms.

BGPpacket lossRTTautomated
A network map of wireless links — each node showing client count, CCQ, noise floor, airMAX quality and capacity, distance and frequency; hostnames removed.

One map — MikroTik, Ubiquiti and Cambium together

A small or mid-sized operator's network is rarely single-vendor: MikroTik in the core, Ubiquiti on the wireless links, Cambium at the access layer. This map carries, per link, what operations actually runs on — wireless clients on the sector, CCQ, noise floor, airMAX quality and capacity, distance, frequency, Rx/Tx and uptime. The tower power nodes sit on the same map: battery voltage is a metric like any other here, and it explains half of the night-time outages.

MikroTikUbiquitiCambiumairMAXSNMP
Blurred LibreNMS dashboard with a device availability map and alert history.

Network inventory and health

Over 130 devices and thousands of ports in one system: an availability map, alert history and the top errored interfaces — including the GPON/EPON access layer, where a fault shows up on the port before the subscriber notices it.

LibreNMSSNMPGPON/EPONalerting
A Zabbix graph for a single circuit — inbound and outbound traffic over time.

One circuit, one graph — QoS in real time

This is what one business circuit looks like in Zabbix: inbound and outbound traffic, peaks, the real use of the committed rate, and history. It is the graph that answers "is the link actually enough" — and the customer can see that answer too, not only us.

ZabbixQoSSNMPper-circuit
Blurred OpenPath NOC console showing service status, latency sparklines and an incident feed.

OpenPath — our own NOC console

Live path monitoring on a 15-second refresh: latency and packet loss to each service, including cache servers hosted inside individual operators. A path change is recorded as its own incident, with filters by ASN, ISP and customer. We wrote this tool ourselves because no off-the-shelf product answered the question.

in-houselatency / losspath changeper-ASN

Capabilities

Capabilities

Every item is marked: verified production experience, or engineering capability.

24/7 network monitoring

Proven

The group's own ISP and datacenter run continuously — same processes, same tooling.

  • Zabbix
  • Prometheus
  • Grafana

Severity-based incident response

Proven
  • Runbooks
  • On-call rota

SOC — event correlation

Capability

SIEM rules, detection content and incident response playbooks.

  • Wazuh
  • Graylog
  • OpenSearch

Co-managed mode

Capability

Your team keeps control; we cover the shifts and the escalation path.

ITSM integration

Capability

Two-way sync with your ticketing system.

  • Webhooks
  • REST API

Telegram / PagerDuty escalation

Proven
  • Telegram Bot API
  • Alertmanager

Path monitoring and loss detection

Proven

Latency and packet loss to every critical destination — including cache servers hosted inside individual operators. That is how you tell whether the fault is in our network, in transit, or at the content provider.

  • OpenPath
  • ICMP / TCP probes
  • per-ASN

Technology stack

Technology stack

Monitoring
ZabbixLibreNMSPrometheusGrafanaBlackbox
In-house tooling
OpenPathnoc.com.ge
Logging
GraylogOpenSearchLokiVector
Security
WazuhFortiGateSuricata
Alerting
AlertmanagerTelegramPagerDuty

Engagement model

Engagement model

Co-managed

NetWizard and your in-house team together, with split responsibility.

Fully managed

We own the agreed operational scope end to end.

Critical operations

24/7 monitoring, response and severity-based escalation.

Retainer

Monthly engineering hours — specialist access on demand.

FAQ

FAQ

How do you access our infrastructure?

Named accounts only, with MFA, logged sessions and agreed change windows. Details are in the Trust Center.

What SLA do you offer?

The SLA is defined per service plan: severity-based acknowledgement, response and escalation targets are fixed in the contract.

Can you work with our existing tools?

Yes. If you already run Zabbix, Prometheus, Grafana or a SIEM we operate on it, correcting the configuration where needed.

Tell us about your infrastructure