-
Plivo

All Systems Operational

Uptime over the past 90 days. View historical uptime.
Messaging API Operational
90 days ago
100.0 % uptime
Today
SMS API Operational
90 days ago
100.0 % uptime
Today
MMS API Operational
90 days ago
100.0 % uptime
Today
Powerpack SMS Operational
90 days ago
100.0 % uptime
Today
Powerpack MMS Operational
90 days ago
100.0 % uptime
Today
Verify API Operational
90 days ago
100.0 % uptime
Today
Voice API Operational
90 days ago
99.99 % uptime
Today
REST APIs and XML Operational
90 days ago
100.0 % uptime
Today
PSTN Calls Operational
90 days ago
99.96 % uptime
Today
Client Calls (Browser & Mobile) Operational
90 days ago
100.0 % uptime
Today
Conference Operational
90 days ago
100.0 % uptime
Today
Recordings Operational
90 days ago
100.0 % uptime
Today
Text-to-Speech Operational
90 days ago
100.0 % uptime
Today
Transcription Operational
90 days ago
100.0 % uptime
Today
Speech Recognition Operational
90 days ago
100.0 % uptime
Today
Endpoint calls (SIP) Operational
90 days ago
100.0 % uptime
Today
BYOC Operational
90 days ago
100.0 % uptime
Today
Answering Machine detection Operational
90 days ago
100.0 % uptime
Today
CDR (Call Detail Records) Operational
Zentrunk - SIP Trunking Operational
90 days ago
100.0 % uptime
Today
SIP Trunking Operational
90 days ago
100.0 % uptime
Today
Carrier Partners: Messaging API Operational
90 days ago
100.0 % uptime
Today
Longcode SMS, USA & Canada Operational
90 days ago
100.0 % uptime
Today
Shortcode SMS, USA & Canada Operational
90 days ago
100.0 % uptime
Today
Toll-free SMS, USA & Canada Operational
90 days ago
100.0 % uptime
Today
MMS, USA & Canada Operational
90 days ago
100.0 % uptime
Today
SMS, Mexico & South America Operational
90 days ago
100.0 % uptime
Today
SMS, Asia Operational
90 days ago
100.0 % uptime
Today
SMS, Europe Operational
90 days ago
100.0 % uptime
Today
SMS, Africa Operational
90 days ago
100.0 % uptime
Today
SMS, Oceania Operational
90 days ago
100.0 % uptime
Today
Carrier Partners: Voice API Operational
90 days ago
100.0 % uptime
Today
Voice, North America Operational
90 days ago
100.0 % uptime
Today
Voice, South America Operational
90 days ago
100.0 % uptime
Today
Voice, Europe Operational
90 days ago
100.0 % uptime
Today
Voice, Asia Operational
90 days ago
100.0 % uptime
Today
Voice, Africa Operational
90 days ago
100.0 % uptime
Today
Voice, Oceania Operational
90 days ago
100.0 % uptime
Today
Carrier Partners: Zentrunk - SIP Trunking Operational
90 days ago
100.0 % uptime
Today
SIP Trunking, North America Operational
90 days ago
100.0 % uptime
Today
SIP Trunking, South America Operational
90 days ago
100.0 % uptime
Today
SIP Trunking, Europe Operational
90 days ago
100.0 % uptime
Today
SIP Trunking, Asia Operational
90 days ago
100.0 % uptime
Today
SIP Trunking, Africa Operational
90 days ago
100.0 % uptime
Today
SIP Trunking, Oceania Operational
90 days ago
100.0 % uptime
Today
Console Operational
90 days ago
100.0 % uptime
Today
PHLO Operational
90 days ago
100.0 % uptime
Today
Account & Phone Number APIs Operational
90 days ago
100.0 % uptime
Today
Number Lookup API Operational
90 days ago
100.0 % uptime
Today
Payments and Billing Operational
90 days ago
100.0 % uptime
Today
Support Ticketing System Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Scheduled Messaging Platform Maintenance Feb 8, 2026 03:30-07:30 UTC

Dear Valued Customer,

We will perform planned maintenance on our Plivo database on Sunday, 8th February 2026 to improve the overall availability of our database engines. During that time, Plivo customers may find intermittent service failure.

When is the maintenance?

08th February 2026 03:30 - 08th February 2026 07:30 UTC
07th February 2026 19:30 - 07th February 2026 23:30 PDT

What services will be affected?
During this maintenance window, you may experience intermittent failures on SMS/MMS/Verify/WhatsApp/RCS requests.

If you have any questions, please feel free to reach out to our support team.
Please click on the following link to submit a support ticket:
https://support.plivo.com/hc/en-us
Posted on Jan 20, 2026 - 08:17 UTC
System Metrics Month Week Day
API Uptime ?
Fetching
API Response Time ?
Fetching
Jan 26, 2026

No incidents reported today.

Jan 25, 2026

No incidents reported.

Jan 24, 2026

No incidents reported.

Jan 23, 2026

No incidents reported.

Jan 22, 2026

No incidents reported.

Jan 21, 2026

No incidents reported.

Jan 20, 2026

No incidents reported.

Jan 19, 2026

No incidents reported.

Jan 18, 2026

No incidents reported.

Jan 17, 2026

No incidents reported.

Jan 16, 2026

No incidents reported.

Jan 15, 2026

No incidents reported.

Jan 14, 2026

No incidents reported.

Jan 13, 2026

No incidents reported.

Jan 12, 2026
Voice API Intermittent Failures (India Region)
Resolved - Incident Summary — Intermittent Voice API Failures (India Region)

Incident Window:
12 January, 10:30 AM IST — 11:46 AM IST

Impact:
Intermittent failures were observed across multiple Voice APIs in the India region, including make call API requests returning HTTP 502 errors. The service was not continuously unavailable, but experienced periodic degradation during the incident window.

Summary
On 12th January between 10:30 AM and 11:46 AM IST, intermittent failures were observed in Voice APIs in the India region. The service remained available for most of the time, but experienced periodic spikes of failures.
The incident was triggered by a spike in CPU utilization on Plivo’s CDR database, which reached 100%, driven by a high volume of list CDR API requests.
To contain the database overload, the rate limit quota for list CDR APIs was reduced. During this containment window, some list CDR API requests returned 5xx responses intermittently. These 5xx responses interacted incorrectly with the API Gateway’s circuit breaker logic.
The circuit breaker marked the upstream service as unhealthy but failed to route traffic to the configured failover upstream. This caused traffic to be dropped instead of being rerouted, resulting in intermittent 502 errors across a wider set of APIs, including the make call API.
Jan 12, 05:00 UTC
← Incident History Powered by Atlassian Statuspage