Operate · Alarms & incidents
An alarm counts against a datacenter only when it belongs there.
Every alarm is scoped: inside the site, on an edge link leaving it, on something it depends on, or downstream. Downstream symptoms never count on their own; they show under the incident that caused them. Each incident arrives with affected services and customers, ranked root-cause hypotheses and actions.
Why teams open Alarms & incidents
Three questions Alarms & incidents answers.
What people ask in the first minutes, and who asks it. Alarms & incidents puts the answer on one screen, for Colocation and NeoCloud operators.
Capabilities
What Alarms & incidents does.
Scope model
Site, edge (counted at both ends), dependency and downstream. Edge redundancy is redundant, redundancy-lost or isolated.
Correlation and RCA
Ranked hypotheses with evidence. A completed change cited by the leading hypothesis is marked as having caused an incident.
Impact on every incident
Services, customers, premium customers and money, the same figures you see on the customer and revenue screens.
Severity in words
Critical, High, Medium, Low for incidents; Critical, Major, Minor, Warning for alarms.
On call and communications
Rota per region, the paging chain, the next escalation, and customer notices with their update cadence.
Problems
Incidents grouped by a shared cause, such as one optics lot behind several link failures.
See your own estate in it.
Bring the fault your team keeps dealing with. We walk it end to end on a demo estate shaped like yours, then agree what a one-site pilot should prove.