Plivo: Inbound call failures in India region

What to do

Check whether you use Plivo in in, us. 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-05-12 11:26 UTC and 2026-05-12 10:50 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.

resolvedMay 12, 2026, 10:50 AM UTC
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
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-05-12 10:50 UTC. For Plivo's live state, see https://down.guide/plivo.

How long did it last?

0m, from 2026-05-12 11:26 UTC to 2026-05-12 10:50 UTC, by the times Plivo posted.

What was affected?

Plivo named in in, us.

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.