Plivo: Voice API Intermittent Failures (India Region)

What to do

Check whether you use Plivo in in. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.
Anything that failed between 2026-01-14 13:46 UTC and 2026-01-12 05:00 UTC may need a replay.
Subscribe to Plivo's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=plivo works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

resolvedJan 12, 2026, 5:00 AM UTC
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.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Plivo still down?

No, this incident was resolved 2026-01-12 05:00 UTC. For Plivo's live state, see https://down.guide/plivo.

How long did it last?

0m, from 2026-01-14 13:46 UTC to 2026-01-12 05:00 UTC, by the times Plivo posted.

What was affected?

Plivo named in in.

What caused it?

Plivo hasn't published a root cause. If it does, it shows here.

Where does this come from?

Plivo's official status page, https://status.plivo.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.