Network status.
Live health of the website and API on this page, and the way the NOC publishes incidents and planned maintenance for the voice, SMS, numbering, API, portal and connectivity platforms.
Current status.
Website and API checks run from your browser against this origin. Platform components are reported by the NOC - automated component feeds are being integrated.
Website and API operational
Running first check · refreshes every 60 s
- Operational
Websitelive
dollu.com - this page loaded from the origin
- Checking
APIlive
/api/health
Platform components
Published by the NOC
Voice core · Operational
SIP interconnects, A-Z routing, media
SMS gateway · Operational
A2P/P2P SMPP and HTTP delivery
Numbers platform · Operational
DID provisioning, porting, inbound routing
APIs · Operational
Voice, SMS, Verify, Video and Email APIs
Portal · Operational
Customer portal, tickets, CDRs and reports
Connectivity backbone · Operational
PoP-to-PoP transport and internet edge
Component status is published by the NOC; automated feeds are being integrated - for incidents see your portal notifications or email [email protected].
How incidents and maintenance are communicated.
A status page is only as good as the process behind it. This is how the 24×7 NOC detects, notifies and closes out events.
24×7 NOC monitoring
Engineers on shift watch route quality (ASR, ACD, PDD), SMS delivery rates, trunk registrations, circuit telemetry and platform health around the clock, and open incidents before most customers notice.
Incident notifications
Incidents affecting your services are notified by email and in the customer portal, with impact, affected destinations or components, workaround and next-update time. P1 updates every 30 minutes.
Planned maintenance
Planned works are notified at least 5 business days ahead. Standard windows are 22:00-04:00 local PoP time; emergency maintenance is notified as early as possible with the reason and expected impact.
Subscriptions per service
Choose which contacts receive which notices - voice, SMS, numbers, APIs, connectivity or all - in the portal, or ask your account manager to configure them for you.
Post-incident reports
Every P1 incident receives a written post-incident report within 5 business days: timeline, root cause, customer impact and the corrective actions we have committed to.
Talk to an engineer
If something looks wrong and you have not heard from us, call +91 777-500-2222 (NOC option) or email [email protected]. Tickets are acknowledged with an ID within minutes.
What the status labels mean.
Consistent wording across the portal, notification emails and this page.
| Operational | Service performing within SLA targets. Routine changes and minor, non-impacting works may still be in progress. |
|---|---|
| Degraded performance | Service available but with reduced quality or capacity - for example elevated PDD on a destination, slower SMS delivery or higher API latency. Workaround or reroute in place where possible. |
| Partial outage | A subset of customers, destinations or features is unavailable. Engineers are working the incident 24×7 with updates every 30 minutes for P1. |
| Major outage | A platform component is unavailable for most customers. Executive escalation is engaged, and a post-incident report follows within 5 business days. |
| Maintenance | Planned works within a notified window. Impact, duration and back-out plan are stated in the notice; most maintenance is hitless thanks to geo-redundant pairs. |
Support & NOC
Severity levels, response times, escalation matrix and how to raise a ticket.
Support & NOCTrust & compliance
Resilience, security controls, data protection and responsible disclosure.
Trust centreGet incident and maintenance notices.
Ask your account manager to add contacts to notifications for the services you use, or email [email protected] with the addresses and services to subscribe.
