Network Overview

Your network operations workspace
LiveWall display ↗
NETWORK OPERATIONS

Network overview

Live health, trends and incidents across the routers, sites and probes the NOC collects from.
● Live

Fleet health

Routers with a fresh sample

Coverage counts routers that reported within three collection intervals. A router without a fresh sample is shown as not reporting, not as down.

New incidents

Opened per hour · last 24 hours · hover for detail
NETWORK QUALITY · NOC OS 0.8.0

Site collectors & ping checks

Configure checks, follow latency and loss, and monitor from your local sites.

Loading quality monitoring…

Routers & Sites

DeviceRoleCPUMemoryPPPoEStatus

Internet Experience

Active Incidents

Network Map

Every router, radio and OLT grouped by site, with the links between them. Health comes from NOC OS polling.
Loading...
Live map ↗
WHERE THINGS ARE

Sites map

Loading…

HOW IT CONNECTS

Network diagram

Loading…

UpDegradedDownNot reportingSeen by router, not confirmedWireless

AUTOMATIC TOPOLOGY

Discovered links

Devices each router sees directly on its ports (MNDP, LLDP and CDP). Matched links are drawn on the map automatically.

DeviceConnects toSeen byCheck
Loading…

Neighbours not in NOC OS

NeighbourAddressSeen by
Loading…

Only the last 30 minutes of polls are used, so an unplugged link disappears on its own. Add an unmanaged neighbour from Routers & Sites to monitor it.

INFRASTRUCTURE AUDIT

Infrastructure overview

Fleet health, PHP CVE exposure and resource pressure across every audited server, LXC, VM and Docker engine.

Fleet health

Latest result per system

The score counts systems with no flags (including partial Docker-only checks) out of all systems. A partial check is not proof of safety.

Audit history

Systems checked per audit run · hover for detail

Resource pressure

Highest usage first · amber ≥ 80%, red ≥ 90%

PHP findings by assessment

Most common warnings

Latest scan results

Select a system for full findings and trends
SystemTypeOS / PHPContainersDisk usedHealthScanned

Registered servers

Add servers, SSH keys and backups in the audit console
TargetTypeAccess
LIVE NETWORK / OPERATIONS

Network monitoring.

See the routers, interfaces and alarms that need your attention.

Waiting for collector data…
ROUTER RESOURCES

CPU & memory history

Actual samples from the past 24 hours.

Waiting for router data.
CPU MemorySelect a router to view its history.
MONITORING COVERAGE

Routers & sites

Latest known collector status.

Waiting for router data.
TRAFFIC INVESTIGATION

Interface traffic history

Follow a link over time, including its most recent measured rates.

Choose a router and interface to view traffic.
RX TXInterface names are taken from the last successful reading.
INTERFACE TELEMETRY

Traffic & interface health

RX and TX rates are calculated from consecutive device samples.

Router / siteInterfaceRXTXLink speedErrors ΔStateSample
Waiting for interface data.
Rates need two recent samples. Error changes cover the interval between those samples; unavailable or reset counters appear as —. Interface totals may overlap or omit hardware-offloaded traffic.
Make your important links actionable.Add transit, peering and backhaul circuits to monitor utilisation and unexpected link-down events.
60 GHZ / BACKHAULS / RADIOS

Wireless links

Signal, SNR, rate, capacity, loss and latency of every radio link, on a map. Click a link for its graphs.
Loading wireless links…
Loading the wiki…
LATENCY / JITTER / ROUTES

Gaming paths

Ping, jitter and loss to popular game servers, and the route each one takes out of the network: IX peering or IP transit.
Loading gaming paths…
NETFLOW / IPFIX / BGP

Traffic flows

Where core router traffic goes: IP transit versus peering, by link, BGP peer, remote network and prefix.
Loading traffic flows…
ROUTERS / PORTS / SITES

Router dashboards

Ports, link speeds and traffic by role, volts, pings, PPPoE and the security log for every router.
Loading routers…

Routers & Sites

Core, edge and site device health with latency, MTU and PPPoE context.
DeviceSiteRoleCPURAMLossLatencyMTUSessionsStatus

Onboarded Live Devices

DeviceHostSiteRoleVendorLast SeenStatusActions
No live devices onboarded yet.

OLTs & Fibre

Live SNMP OLT/ONU inventory, PON health and optical receive levels.
Loading...

OLT Fleet

OLTSiteVendorONUsAttentionPingStatusActions

PON Detail

Select an OLT.
FIBRE PLANT

Fibre layout

Every PON from the OLT port through feeders, closures and splitters to each customer drop, with live ONT status and receive levels.
OLTs & PON ports
Fibre layout
100%
Core colours (TIA-598)Leg in serviceCustomers downONT onlineONT downPower loss (dying gasp)
ONTs not yet on the layout

Add element

SFP Modules & Optics

Every SFP, SFP+ and QSFP module on your routers: make, part number and serial, receive and transmit light, temperature, and what each one connects to.
Loading...
YOUR NETWORK / NETWORK INTELLIGENCE

AI Network Engineer

Understand what needs attention and review your next checks.
◈   ADMIN VIEW
Human reviewed. Read-only.Observations come from collected monitoring data. Recommendations never make changes to your network.
STEP 1   /   SOURCE EVIDENCE

Network observations

Review current collector freshness, resources and routing checks.

No observations loaded yet.

Connect your network monitoring before running an assessment.

STEP 2   /   AI REVIEW

Ask your network engineer

Get an evidence-linked review from a configured Ollama model.

Configure a verified HTTPS Ollama endpoint and installed model in Settings. No AI request is made until you select Review with AI.

No AI review has been generated.

The AI receives a bounded set of pseudonymous monitoring observations, not customer records, device names, addresses, credentials or router configurations. Review every suggestion against the source data.

PPPOE / RADIUS / CUSTOMERS

Subscribers & RADIUS

Customers, PPPoE logins, plans and routers on the NOC OS RADIUS server. Runs beside Splynx; a router moves over only when you run its primary script.
Loading…
TICKETS / SLA / SUPPORT

Helpdesk

Customer tickets from the portal and the ones staff open: assign them, set priorities and keep inside the reply and resolve targets.
Loading…
INSTALLS / FIELD WORK / TECHNICIANS

Scheduling

Installations, repairs and site work by day and technician. Website install bookings land here by themselves.
Loading…
TR-069 / GENIEACS

Customer Routers

Every customer router that checks in with your ACS: who it belongs to, whether it is online, and remote reboot, Wi-Fi and PPPoE changes.
Loading…
HOTSPOT / PREPAID WI-FI

Hotspot Vouchers

Prepaid Wi-Fi codes for hotspots: make a batch, print the cards or hand a CSV to a reseller, and see which codes are in use.
Loading…
WHATSAPP / TEAM / DEPARTMENTS

Inbox

WhatsApp chats with customers for the whole team: departments, assignment, internal notes and saved replies.
Loading…
LEADS / PIPELINE / SALES

CRM Leads

Everyone who might become a customer, from website signups, calls and resellers, through to Convert to customer.
Loading…
CONTRACTS / E-SIGNATURE / FILES

Documents & Contracts

Send contracts for customers to sign online, and keep each customer's files in one place.
Loading…
PARTNERS / COMMISSION

Resellers

Commission terms for each partner and the monthly statements to approve and pay.
Loading…
API KEYS / WEBHOOKS / EVENTS

API & Webhooks

Let your website, accounting system or a reseller's tools work with NOC OS, and tell them when things happen.
Loading…
ADMINISTRATION

Administration

Staff, roles and partners, logs, information and reports, as in Splynx's Administration page.
Loading…
CONFIG

Config

Every setting of the Business app, grouped as in Splynx's Config page.
Loading…
CONFIG

Setup lists

Additional fields, canned responses, task and checklist templates, project types, voice and deleted customers.
Loading…
SCHEDULING

Projects

Bigger jobs made of several tasks, moving through their workflow.
Loading…
REPORTS

Reports

Customer, plan, usage, ticket and finance reports, each as CSV or a page to print.
Loading…
YOUR COMPANY / OPERATIONS

Business Operations

Customers, support, stock and calls together in your operations workspace.
◈   ADMIN VIEW
Private, read-only Splynx viewLoad current records when you need them. Customer details stay in this admin view and are not shown on the wall display.
SPLYNX   /   CUSTOMER LABELS

Customer labels

View labels configured in Splynx for customer accounts.

Customer labels have not been loaded.
Label IDCustomer label
No labels loaded.

In Settings → Splynx, use your Splynx server's base URL. Your API key needs permission to view customer labels.

SPLYNX   /   ACCOUNTS

Blocked customers

See known provider labels and fully unpaid invoices past their due date.

BLOCKED ACCOUNTS—Not loaded
PROVIDER MAPPED—From recognised labels
INVOICE COVERAGE—Fully unpaid invoices only
Connect Splynx in Settings, then load the latest records here.
CustomerProvider labelEarliest due foundUnpaid due monthsBlocked since
No customer data loaded.

A blocked account and unpaid invoices do not prove why it was blocked. Months count distinct due-date months for invoices marked not_paid; partially paid invoices are excluded. Actual blocked duration needs verified status history.

SPLYNX   /   SUPPORT

Open support tickets

Tickets currently identified as open, new, in progress or waiting.

Ticket records have not been loaded.
TicketSubjectStatusAssigned IDCreated
No ticket data loaded.

SLA timing, paused time, business hours and reopened tickets require your actual Splynx fields and support rules before a reliable breach can be shown.

INVENTORY   /   JOBS

Stock accountability

Compare equipment recorded on completed jobs against stock issues and returns, including serial numbers and the person who booked it out.

○   Stock movements and job usage not connected yet

A discrepancy needs both sources and is a review item, not proof of missing stock.

YEASTAR   /   CALLS

Call performance

Queue missed calls and calls answered by each team member.

Configure Yeastar in Settings and enter a date range using the PBX display format.
Queue / team memberAnsweredMissedAbandoned
No call report loaded.

Queue missed calls and individual missed calls measure different things. Calls outside queues are not included. Yeastar may require different API versions for older call records; its report date format must match your PBX.

SITES · EQUIPMENT · COMPLEXES

Sites & complexes

Every POP, tower and complex with the equipment installed there. For apartment complexes, see which units are live, suspended or cancelled, and who cancelled and why.
SiteEquipmentHow it's runningUnitsCancelled (90d)
Loading…
CHURN

Cancellations

Every unit marked cancelled, with when, who cancelled and the reason. Cancellations picked up from Splynx have no reason until someone adds it.

WhenUnitCustomerWho cancelledReason
Loading…

From the website cancellation form

SubmittedCustomerLast dayReasonSplynx
Loading…
INSTALLS

Install bookings

Installations customers booked on the website, from yesterday on. Each one has a Splynx ticket for the install team. Confirm a booking to put it on the Splynx calendar and email the customer; change the date when the provider gives another day.

DayCustomerPlaceNotesSplynx
Loading…
SUPPORT

Website fault reports

Faults customers logged on the website. When their site already had an outage or maintenance, they were told and no ticket was opened unless they asked for one.

ReportedCustomerPlaceProblemOutcome
Loading…
NEW CUSTOMERS

Website signups

People who checked coverage and signed up, or asked to hear when fibre reaches them. Each one becomes a Splynx lead with a ticket for sales.

SubmittedPersonPlacePackageSplynx
Loading…

Customer Trace

Trace a subscriber from ONU through OLT, access, edge, core and Internet.
Enter a subscriber and run trace.

Internet Experience Probes

Datacentre measurements for ICMP, DNS, HTTPS, PMTU and the configured streaming host.

Probe Detail

TargetTypeLatencyJitterLossStatus

PMTU Paths

NETWORK QUALITY / SITE COLLECTORS

See the network from every site.

Create ping checks, tune their thresholds and follow the history from your datacentre or a local collector.
Loading monitoring checks…
PING MONITORING

Your checks

Each check sends five pings; one lost packet equals 20% loss. Two consecutive bad readings create an incident.

Check / targetMeasured fromLatencyLossLast sampleStateActions
Loading checks…
HISTORY / NETWORK QUALITY

Ping history

Recorded round-trip time and packet loss for the selected check.

Add a check to see its history.
Gaps mean data was not available. Ping variation is not shown as jitter.
DISTRIBUTED MONITORING

Site collectors

A Raspberry Pi at each site polls its routers, switches and OLTs, runs ping checks and finds everything the site can reach. It keeps collecting when the link to the NOC is down and uploads the backlog afterwards.

Collector / siteConnectionCollectsUploadsComputerVersionActions
Loading collectors…
Collectors connect out to NOC OS over HTTPS only and update themselves. They read devices with RouterOS REST or SNMP v2c and never change their configuration. NetFlow is not collected by site collectors yet.

Alerts & Incidents

Review observed conditions and acknowledge alarms individually.
SeverityAlarm & evidenceRouter / siteWhenStatusActions
Phone alertsChecking notification status…
CPU, memory and configured circuit alarms require repeated readings. A failed monitoring check does not by itself prove a router is down. Thresholds can be changed under Settings → Alarm thresholds.

Circuits & capacity

Directional interface traffic, packet rates and configured circuit speeds.
Each circuit monitors one selected interface. RX and TX are separate; the higher direction determines utilisation. Router counters may omit hardware-offloaded traffic.
Circuit / siteCapacityRX / TXPackets/s RX / TXUtilisationLast sampleStatusActions
BILLING & COMMIT

95th percentile report

Burstable-billing rate for a circuit: 5-minute averages with the top 5% removed. Compare it with your transit or backhaul commit.

Choose a circuit and period.
ALARM GROUPING

Device dependencies

Tell the NOC which device each router is reached through. When an upstream device goes down, you get one alert for it instead of one for every device behind it.
DeviceReached through (upstream)Behind itNow
Loading…

Alarms behind a down device are still recorded and shown in Incidents, labelled with the upstream device. Their phone alerts are held. If a device is still down after its upstream device recovers, its alert is sent then. Recovery messages are never held.

UPTIME REPORTING

Availability & SLA

How long each device and site was reachable, measured from every collector poll. Planned maintenance is shown separately and does not count against the SLA.
Export CSV
PER DAY

Downtime across the network

Minutes devices were unreachable each day, added up. Hover a day for its uptime.

BY SITE

Site availability

SiteUptimeOutagesDowntime
Loading…
BY DEVICE

Device availability

Worst first. Each square is one day: green meets the target, amber is close, red is below, grey has no data.

DeviceUptimeDailyOutagesDowntimeData
Loading…
HISTORY

Outages

Every period a device stopped answering polls, newest first. Kept for two years, long after raw samples are pruned.

DeviceStartedEndedLastedSLA
Loading…

REAL TIME

Live view

Second-by-second traffic, CPU, memory and latency for one router, read directly from the router while this page is open.
Choose a router and interfaces, then press Start.
LAST 5 MINUTES

Interface traffic

Solid lines are RX, dashed lines are TX. Rates come from consecutive counter reads; a counter reset shows as a gap.

InterfaceRX nowTX nowPackets/s RX / TXLink
RESOURCES

CPU and memory

REACHABILITY

Latency from the NOC

Read-only. Each live view stops after 15 minutes; a router can have two open at once. Live readings are not stored; history comes from the regular collector.

PLANNED WORK

Maintenance windows

Mute phone alerts for a device, a site or the whole network during planned work. Alarms are still recorded.
WindowApplies toTimeStateActions
Loading…

If a problem is still open when a window ends, its held alert is sent then. Recoveries during the window are not sent. Ending or cancelling a window is recorded in the operator audit log.

CUSTOMER STATUS PAGE

Posted incidents

Loading…

IncidentAreaStartedStateActions
Loading…

Automatic incidents go up when a router suddenly loses PPPoE sessions and come down by themselves when the sessions are back. Customers see the title, area and message only, never router names or session counts.

CUSTOMER STATUS PAGE

What customers see

Loading…

Offline deviceSite fieldOn status pageFix
Loading…

A device is on the status page only when its Site matches a live site under Sites. Complexes, estates and businesses are shown by name; POPs, towers and data centres are all shown as one “Part of our network” row. A router that says online but has had no reading for 10 minutes counts as offline.

BATTERY & MAINS

Site power

Battery voltage and mains status for the sites you choose to watch, read from each site's MikroTik.
Loading…

Two readings in a row are needed to open or clear an alarm, and "not charging" needs the bank low on mains for the whole window set under Settings, Alarm thresholds. A missing reading never clears an alarm, but one that has not been seen again for hours while readings keep coming is cleared. Mains off is a warning; it turns critical, and reaches phones, when the battery is about to run out. Runtime left is a rough estimate from the last 30 minutes of voltage, and lead-acid voltage falls faster near empty.

ROUTER POWER SUPPLIES

PSU state per router

Every router that reports its power supplies. One PSU failing while another is OK means the router lost redundancy (a warning). If a router only has one feed by design, list it under Settings, Alarm thresholds, Single power feed routers.

SiteRouterPower suppliesRead
Loading…
DATA QUALITY

Collector health

Is every router being polled on time, without gaps? Routers are polled in parallel, failed polls are retried, and a stopped or overloaded collector raises an alarm.
LAST 60 CYCLES

Cycle duration

Bar height is the cycle time as a share of the poll interval. Red cycles ran longer than the interval; amber cycles had a failed router.

LAST 24 HOURS

Per-router completeness

DeviceCompletenessFailed pollsSaved by retryGapsLast good pollLast error
Loading…
SITE COLLECTORS

Collectors at your sites

Each site collector polls its own devices. While its link is down it keeps the readings and uploads them when the link returns, so they still count towards completeness.

CollectorConnectionDevicesWaiting to uploadComputer
Loading…
ALERT DELIVERY

Alert channels

Send alarms to Telegram, email, Slack, Teams, Discord, any webhook or PagerDuty (phone calls to whoever is on call), alongside Gotify phone alerts. Each channel has its own severity, site and recovery rules.
ChannelSendsLast resultStatusActions
Loading…
EVERY MORNING

Morning network report

A summary of the last 24 hours with charts: bandwidth, alarms, outages, PPPoE, OLTs and ONUs, site power and internet latency. It goes to every channel with “Send the morning network report” ticked.

Loading…
ALARM RULES

What each alarm does

Choose how serious each kind of alarm is and what happens when it fires. “Call me” sends it to every channel, including PagerDuty phone calls, whatever its severity. “Message only” never phones. Changes apply the next time the alarm fires.

AlarmLast 30 daysHow seriousWhat happens
Loading…
RECENT DELIVERIES

What was sent

The last 50 alarms and recoveries across all channels, newest first.

WhenChannelAlarmResult
Loading…
ACCESS CONTROL

Users & audit

Give each person their own sign-in and one role. The role decides which modules they see and whether they can view, edit or delete in each, like roles in Splynx. Every change is recorded below with who made it.
UserRoleTwo-factorLast sign-inStatusActions
Loading…
AUDIT LOG

Who changed what

Settings, devices, circuits, maintenance, alarm acknowledgements and user changes, newest first. The full change log with before and after for every change, and changes waiting for approval, are on Security → Change control.

WhenWhoWhatDetails
Loading…
SECURITY

Change control

What changed on your routers and when, who was signed in at the time, and an alarm when many routers change at once. Below that, every change made in NOC OS itself.
NETWORK

Router changes

Each MikroTik is read (read-only) and every change to its configuration is kept here line by line: accounts, services, firewall, NAT, routes, addresses, VLANs, PPP, DHCP, queues, scripts, the scheduler, BGP and more. Passwords and keys are never stored.

WhenRouterWhat changedWho was signed in
Loading…
WAITING FOR YOU

Changes waiting for approval

Accepting a change applies it exactly as it was asked for, in the name of the person who asked. You cannot accept your own.

Loading…

SECURITY POSTURE

How well NOC OS is locked down

Red items leave a door open. Fix them first.

Loading…

NOC OS CHANGE LOG

Who changed what in NOC OS

Entries cannot be edited or deleted, and each one is sealed with the one before it.

WhenWhoWhatResultDetails
Loading…
EXPIRY MONITORING

Certificates & domains

Get warned before an HTTPS certificate or a domain registration lapses. Expiring, expired, untrusted and unreachable certificates raise alarms.
CheckCertificateIssuer / namesDomain registrationCheckedActions
Loading…
IP REPUTATION

IP blacklists

Your routers' public addresses and public customer pools, checked on Spamhaus, Barracuda, SpamCop and other DNS blacklists. A listing raises an alarm on your alert channels.
LISTED NOW

Addresses on a blacklist

Fix the cause first (usually an infected customer device or an open mail relay), then ask the list for removal. Some lists clear by themselves once the abuse stops.

AddressListWhySinceRemove
Loading…
WATCHED

Watched addresses and ranges

Router addresses and public PPPoE/DHCP pools are found on each MikroTik automatically. Add other ranges you own, such as the prefixes you announce over BGP.

WatchRangeStateCheckedActions
Loading…
CHECK ONE ADDRESS

Look an address up now

Checks every list straight away without saving anything, for example a customer's address after they say a website blocks them.

LISTS

Blacklists checked

Spamhaus, Barracuda and SpamCop listings are critical alarms because most mail servers use them; the others are warnings.

ListWhat it meansAlarmLinks
LAST 30 DAYS

Cleared listings

AddressListListedCleared
NETWORK INTELLIGENCE

Power & routing

Inspect observed sensors and routing sessions from fresh device data.

Device health & power sensors

Mains or UPS state requires a source that reports it.
Device / siteSensorReadingObservedActions

Observed BGP sessions

Only sessions returned by monitored routers are shown.
Router / sessionRemote ASNStateUptimePrefixesObserved

ASN traffic · FastNetMon Advanced

Loads counters on demand from a configured FastNetMon HTTPS API. Values are source counters; validate their units, sampling and coverage with your detector.

Configure the FastNetMon API in Settings to use this view.
ASNReported bytesReported packetsReported flows
NETWORK SECURITY

Security & DDoS

Review router activity and detector observations. This page refreshes every minute while open.
Export CSV

Two-factor sign-in Loading…

Loading…

Sign-in activity Loading…

Loading sign-in activity…
Swipe tables sideways to see all columns.

Local security collectors

A router sends syslog to a collector on its private network. The collector forwards supported events outbound to NOC OS; router HTTPS is optional. Map the router’s exact outgoing IP below.

Router / siteCollectorRouter source IPCollector statusLast event receivedMapping
Loading collector mappings…

UDP syslog can be lost or spoofed. Restrict the collector listener to the private network and trusted router IPs. Silence does not confirm that logging is working. Remapping or disabling a source can reject older queued events.

Approved router access Monitoring only

Choose the accounts and source networks expected on each router. These lists classify new observations; they do not change router access rules.

Router / sitePolicyApproved accountsApproved networks
Loading policies…

Router configuration changes Unknown

Receives supported security logs through a site collector, or through optional RouterOS HTTPS polling.

First seen by NOCRouter / siteChangeRouter accountSource / methodPolicy / feed
No configuration observations loaded.

Only supported formats are shown. The router account does not prove who used it or whether a change was authorised. Source and method are shown only when present; command text is not stored.

Router login observations Unknown

Receives supported security logs through a site collector, or through optional RouterOS HTTPS polling.

ObservedRouterAccountSourceMethodEventAccount policySource policyFeed
No login observations loaded.

Router hardening Loading…

Loading…

DDoS attacks Loading…

Loading…

Router block lists Loading…

Loading…
FastNetMon reports
These reports record what FastNetMon sent. With Drop at the edge when FastNetMon reports a ban on (Settings → DDoS protection) a ban also goes on the router block list above.

Recent detector reports

ReceivedTargetReported actionSeverityIncoming trafficIncoming PPSSource
Open this page to load reports.

Router administrator accounts Unknown

Optional direct RouterOS HTTPS is needed for a complete visible account snapshot. Local syslog can report supported account changes without HTTPS, but cannot list all existing accounts. The first snapshot is a baseline to review.

Router / siteVisible accountsLast checkReview

Recent account changes

ObservedRouterAccountChangeBefore → after

Active management sessions Optional

Optional direct RouterOS HTTPS snapshot. This is not needed for local syslog collection. Short sessions can start and end between checks; the monitoring account may appear.

Router / siteAccountSourceMethodPolicySnapshot received
No sessions loaded.

Router address lists

Read a named RouterOS address list on demand. Being on a list does not prove that an address is currently blocked.

AddressCommentDisabledDynamicTimeout reported
Choose a router and enter a list name.

Full Network Audit

Read-only diagnostics across reachability, interfaces, optics, MTU, routing, PPPoE, streaming and compliance.

Audit Stages

Audit Console Ready

Ready. No configuration changes are made by this audit.

Config Compliance

Compare devices against your network standard.

Configuration Fingerprints

Track hashes and summaries for change detection. These records are not restorable backups.
DeviceCapturedSourceHashChange

Integrations

Bring Zabbix, Splynx, MikroTik and Gotify into one operational view.

Settings

Grouped by job. Each box says what it is for, and each field shows a tip and its default. Changes take effect at the next reading; nothing on a router is changed.
Loading settings...
Passwords and tokens
Stored encrypted and never shown again. Leave a password box empty to keep the saved one.

Servers & Platforms

Operational view of application, monitoring and billing systems.
DATA SAFETY

Database backups

Every site, unit, fibre layout, alarm history and setting lives in the NOC database. It is backed up every night and test-restored once a week.

Loading…

Sign in to NOC OS

Network operations centre