Managed NOC
Managed NOC services
We monitor agreed devices and services, investigate alerts and follow your escalation runbooks. Coverage hours and response actions are set in the service agreement.
Monitoring and response
An alert follows an agreed runbook.
Coverage hours, checks, thresholds and contacts are written into the service agreement.
Coverage boundary
Standard non-transit monitoring is 12 hours a day, seven days a week. Any other coverage is agreed per order.
Defined hours
Managed NOC coverage varies by agreement. Standard non-transit monitoring is 12 hours a day, seven days a week.
Alert triage
We review alerts and follow the approved escalation or recovery steps.
Network context
The team operating AS215605 can investigate routing and reachability alongside host alerts.
Incident records
Actions and outcomes are recorded so your team can review what happened.
Defined responsibility
What the agreement covers
Included in scope
- Monitoring the agreed inventory and checks
- Alert triage and documented escalation
- Recovery actions specifically authorised in runbooks
Outside this scope
- Changes outside the approved runbooks
- Application development and product support
Onboarding
How we start
- 01
Inventory
List systems, owners, dependencies and existing monitoring.
- 02
Agree coverage
Set hours, checks, thresholds, access and escalation contacts.
- 03
Test handover
Exercise alerts and runbooks before coverage begins.
Commercial scope
What determines the quote
- Service shape
- Monitoring and escalation under a written scope
- Price drivers
- System count, coverage hours, alert volume and response actions
- Coverage
- Varies by agreement; standard non-transit monitoring is 12/7