01NOC · 24/7 SNS-IX · AS43268 · TASHKENT

Operational support
when the network needs it

Use the emergency line for service-affecting incidents. Send configuration, maintenance, and documentation requests to the NOC email with enough context to begin diagnosis.

01 · NOC operations
24/7
02 · exchange ASN
AS43268
03 · points of presence
3
04 · service target
99.9%
02Choose the channel

Match urgency to the right action.

Calling and emailing are both useful during a critical incident: the call starts coordination, while the email carries the technical record.

01 · P1
Immediate coordination

Emergency line

+998 (71) 205-9-205

For a current, service-affecting network incident.

02 · NOC
Technical record

Email the operating team

noc@sns-ix.uz

For diagnostics, planned work, configuration, and follow-up.

03Incident priority

Describe impact before assigning urgency.

This guide helps route the first contact. Contractual response and restoration targets remain defined by the applicable service agreement.

  1. 01 P1

    Service-affecting incident

    Traffic stopped, port down, or widespread route loss.

    Call the NOC and send an email with the incident reference.

  2. 02 P2

    Degraded connectivity

    Partial route loss, packet loss, errors, or unstable session.

    Email the NOC with timestamps and diagnostics; call if impact increases.

  3. 03 P3

    Planned or configuration request

    Filter change, maintenance coordination, new session, or documentation question.

    Send a routine request to the NOC email.

04Diagnostic packet

Send what the engineer needs to begin.

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.

  1. 01ASN

    Your ASN and organization

  2. 02PORT

    Port, VLAN, or session affected

  3. 03TIME

    Start time and timezone

  4. 04IMPACT

    Observed impact and affected traffic

  5. 05DATA

    Logs, interface counters, MTR, or route output

NOC contact

If traffic is affected, start the conversation now.

Call for a current service-affecting incident, then email the technical record. For planned work or configuration, email is the primary channel.