Call Failures in US and India regions
Resolved
This incident has been resolved.
Jun 19, 1:01 PMResolved Jun 19, 1:57 PMMajorPSTN CallsEndpoint calls (SIP)
Status Provider
Home
/
Status
/
Service
Home
/
Status
/
Service
Cloud communication platform for SMS, voice, and SIP trunking.
Source
auto
Category
Cloud
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 2h ago
51
Components
0
Active incidents
0
Maintenance
8.33%
90d uptime
Call Failures in US and India regions
Jun 19, 1:01 PM
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
Showing 1 to 25 of 51 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
Messaging API | Operational | Group | Not recorded |
Voice API | Operational | Group | Not recorded |
Zentrunk - SIP Trunking | Operational | Group | Not recorded |
Carrier Partners: Messaging API | Operational | Group | Not recorded |
Carrier Partners: Voice API | Operational | Group | Not recorded |
Carrier Partners: Zentrunk - SIP Trunking | Operational | Group | Not recorded |
Longcode SMS, USA & Canada | Operational | Component | Not recorded |
REST APIs and XML | Operational | Component | Not recorded |
SIP Trunking | Operational | Component | Not recorded |
SIP Trunking, North America | Operational | Component | Not recorded |
SMS API | Operational | Component | Not recorded |
Voice, North America | Operational | Component | Not recorded |
MMS API | Operational | Component | Not recorded |
PSTN Calls | Operational | Component | Not recorded |
SIP Trunking, South America | Operational | Component | Not recorded |
Shortcode SMS, USA & Canada | Operational | Component | Not recorded |
Voice, South America | Operational | Component | Not recorded |
Client Calls (Browser & Mobile) Browser SDK and mobile SDKs | Operational | Component | Not recorded |
Powerpack SMS | Operational | Component | Not recorded |
SIP Trunking, Europe | Operational | Component | Not recorded |
Toll-free SMS, USA & Canada | Operational | Component | Not recorded |
Voice, Europe | Operational | Component | Not recorded |
MMS, USA & Canada | Operational | Component | Not recorded |
Powerpack MMS | Operational | Component | Not recorded |
SIP Trunking, Asia | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Related status pages based on category, adapter type, and operational history.
Plivo is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
Normalized official status-page data for incidents, maintenance, components, and history.
8.33%
Known uptime
12 known history days
51
Components tracked
0 outage, 0 degraded
52
Incidents indexed
0 active right now
50
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Account & Phone Number APIs
Operational
Answering Machine detection
Operational
BYOC
Operational
CDR (Call Detail Records)
Operational
Carrier Partners: Messaging API
Operational
1
operational days
0
degraded days
7
outage days
4
maintenance days
78
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
Dear Valued Customer, We recently experienced call failures in the India region for the 911600 series numbers. After initial investigation, our carrier partner was notified, who took corrective action and the incident was resolved Incident Start Time: 15th June 2026, 11:15 IST Incident End Time: 15th June 2026, 11:45 IST If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us
This incident has been resolved.
This incident has been resolved.
Incident Summary — Elevated Call Failure Rate on 9180 Number Series. Specific number series of 9180 were impacted for outbound calls. Incident Window: 5th June 2026, 6:30 PM IST — 6th June 11:30 AM IST Impact: Outbound calls to the 9180 number series were affected throughout the incident window. The failure rate reached approximately 34% at peak. Other number series and carrier paths were unaffected. The issue appeared to partially ease during low-traffic overnight hours but fully reasserted when business-hours call volumes resumed on the morning of 6 June. Resolution: Once issue was detected engineering team analysed the issue and resolved by replacing affected routing infrastructure. Issue was resolved by 6th June 11:30 AM.
Dear Valued Customer, We recently experienced intermittent Inbound Call failures in India region. Our engineering and operations teams promptly investigated and resolved the issue. The root cause was identified, and corrective actions have been implemented to prevent recurrence. Incident Start Time: 12th May 2026 10:50 UTC Incident End Time: 12th May 2026 11:20 UTC If you have any questions or concerns regarding this incident, please contact Plivo Support. Support portal: https://support.plivo.com/hc/en-us
Dear Valued Customer, We observed some inbound calls to PHLO applications were not being processed successfully. This affected a specific configuration where a phone number rented to a sub-account was attached to a PHLO application owned by the parent account. A recent deployment introduced a change in the request authentication flow that did not account for this configuration. The issue has been identified and fixed. Customers using phone numbers and PHLOs directly under their main account were not impacted. If you have any questions or need further assistance, please don't hesitate to contact Plivo Support through our Support Portal(https://support.plivo.com/hc/en-us).
This incident has been resolved
This incident has been resolved.
This incident has been resolved.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Uptimus tracks the official Plivo status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.plivo.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
