Talk to the NOC. Any hour.
Existing partner with a live incident? Call the NOC first — a network engineer picks up, day or night. Everything else — a change request, a new circuit, a billing question — has a channel below, with the response you can expect and the path it escalates on.
Everything lit, right now.
Planned maintenance is notified in advance to your registered NOC contact, and posted here with the window in IST. Backbone availability SLA: 99.9% · 4-hour MTTR target on core faults.
Pick the right desk.
Network Operations Center
- Phone+91 62832 85600
- Email[email protected]
- ForOutages · degradation · P1/P2
Sales desk
- Phone+91 83528 13528
- Email[email protected]
- ForNew circuits · quotes · upgrades
- Number+91 83528 13528
- Best forQuick questions · status
- Not forP1 incidents — call instead
Registered office
- AddressG-7, Tricity Plaza, Peer Mucchalla, Zirakpur 140603, Punjab
- GST · CINOn request via sales
When we need to see your screen.
Download the Esto Assist client.
For some faults it’s faster if an engineer can see the device with you. When the NOC asks, download the client, run it, and read back the 9-digit session code on screen — we connect only for that session, and only while you watch.
- A NOC engineer asks you to start a remote session.
- Download and run the client for your platform.
- Read the on-screen session code to the engineer.
- Watch the session; close the client to end access.
What happens after you call.
Response targets are the standard tier and apply to contracted partners; tighter targets are available per contract. All times measured in IST.
How a ticket moves.
Log
Call or email the NOC. We open a ticket, assign a severity, and give you the reference on first contact.
Triage
An engineer confirms scope from our monitoring, isolates the fault domain, and starts work inside the response target.
Escalate
If it isn’t moving, it climbs the matrix — NOC lead, then Head of Ops on P1 within the hour. You’re kept updated on cadence.
Resolve & RCA
Service restored, ticket closed with you, and a root-cause note on P1/P2 so the same fault doesn’t come back quietly.