Connectivity monitoring and fault management should combine clear service ownership, appropriate alarms, documented carrier contacts, remote diagnostics, escalation thresholds, engineering access and structured incident communication. The scope must state support hours, response targets and the boundary between carrier service, customer equipment, power, internal network and specialist OT or cyber systems.
Define the monitoring scope
Identify every service and device that needs monitoring, the required hours, alarm thresholds, polling method, data retention and who is responsible for responding. Monitoring can range from simple reachability and interface state to latency, packet loss, utilisation, optical levels and service-specific alarms.
Separate fault domains quickly
Remote diagnostics should distinguish likely carrier failure from customer equipment, local power, internal cabling, optics, routing, configuration or third-party systems. A good evidence pack reduces the time lost repeating basic tests with different suppliers.
- Service state, alarms and last-known-good time
- Power and environmental status
- Interface, optical and error counters
- Reachability, latency and packet-loss tests
- Recent changes or maintenance
- Known route or area incidents
Create a carrier escalation process
Record service references, fault portals, telephone numbers, severity definitions, escalation contacts, maintenance windows and communication expectations. For multi-carrier services, appoint one party to coordinate the whole incident rather than asking the client to manage several disconnected updates.
Coordinate access and engineering
Confirm who can attend, how they gain access, what spares or test equipment are available and who can approve changes. Remote diagnostics are valuable, but some failures require physical inspection, fibre testing, equipment replacement or civils work.
Use incidents to improve the service
A structured incident timeline should record detection, diagnosis, carrier actions, site attendance, restoration, communications and outstanding risks. Follow with root-cause review, service-credit administration and actions to prevent recurrence.
Agree the commercial and service boundary
Consolidated billing and lifecycle review can sit alongside monitoring, but the contract should distinguish invoice administration from connectivity resale and define who remains the carrier’s customer.
Frequently asked questions
Common questions
Can CROSS monitor any carrier service?
Potentially, subject to technical access, the agreed monitoring method and the carrier or customer interfaces available.
Does monitoring guarantee restoration within a fixed time?
No. Monitoring helps detect and coordinate faults, but any restoration commitment must be expressly agreed and supported by carrier and engineering arrangements.
Can CROSS manage service credits?
Yes, where agreed. Incident evidence, outage duration and carrier SLA terms can be reviewed and claims administered.
Does this include cybersecurity monitoring?
Not by default. Connectivity monitoring and carrier fault management are distinct from SOC, cyber, OT or SCADA monitoring.
Apply this to a live site
Send us the location, existing position and required outcome.
CROSS will identify the most useful next step without requiring you to choose the technology first.