Emergency line
For a current, service-affecting network incident.
Use the emergency line for service-affecting incidents. Send configuration, maintenance, and documentation requests to the NOC email with enough context to begin diagnosis.
Calling and emailing are both useful during a critical incident: the call starts coordination, while the email carries the technical record.
For a current, service-affecting network incident.
For diagnostics, planned work, configuration, and follow-up.
This guide helps route the first contact. Contractual response and restoration targets remain defined by the applicable service agreement.
Traffic stopped, port down, or widespread route loss.
Call the NOC and send an email with the incident reference.
Partial route loss, packet loss, errors, or unstable session.
Email the NOC with timestamps and diagnostics; call if impact increases.
Filter change, maintenance coordination, new session, or documentation question.
Send a routine request to the NOC email.
A short, structured incident message is more actionable than a long narrative. Include what is known; do not delay a P1 call while collecting every field.
Your ASN and organization
Port, VLAN, or session affected
Start time and timezone
Observed impact and affected traffic
Logs, interface counters, MTR, or route output
Call for a current service-affecting incident, then email the technical record. For planned work or configuration, email is the primary channel.