Plivo: Intermittent Call failures in the Mumbai region

What to do

Check whether you use Plivo PSTN Calls in apac, 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 22h 4m it lasted.
Anything that failed between 2025-05-13 14:41 UTC and 2025-05-14 12:45 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.

investigatingMay 13, 2025, 2:41 PM UTC
Dear Valued Customer, We observed partial/intermittent Call failures in the India region towards Mumbai phone numbers. Calls originating from International Caller IDs towards India were not affected. All other services are operating normally. We're actively working with our carrier partner to get this issue resolved as soon as possible. Please contact Plivo Support for any questions. Support portal: https://support.plivo.com/hc/en-us
provider
monitoringMay 13, 2025, 3:59 PM UTC
We will continue to monitor the situation and provide another update as soon as possible.
provider
resolvedMay 14, 2025, 12:45 PM UTC
This incident has been resolved.
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 2025-05-14 12:45 UTC. For Plivo's live state, see https://down.guide/plivo.

How long did it last?

22h 4m, from 2025-05-13 14:41 UTC to 2025-05-14 12:45 UTC, by the times Plivo posted.

What was affected?

Plivo named PSTN Calls in apac, 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.