- Level
- confirmed
- Worst impact
- Degraded
- Components
- REST APIs and XML, PSTN Calls
- Regions
- in
What to do
Check whether you use Plivo REST APIs and XML, PSTN Calls 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 10h 36m it lasted.
Anything that failed between 2026-07-31 17:01 UTC and 2026-08-01 03:37 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.
Updates from Plivo 4
- investigating
Dear Valued Customer, We are observing outbound call failures in the India region. Our team is investigating the issue.
provider
- identified
We have identified the issue with our cloud service provider. Our team is working closely with them to resolve the issue, and we will provide another update as soon as more information becomes available.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-084613b7db
Is Plivo still down?
No, this incident was resolved 2026-08-01 03:37 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
10h 36m, from 2026-07-31 17:01 UTC to 2026-08-01 03:37 UTC, by the times Plivo posted.
What was affected?
Plivo named REST APIs and XML, PSTN Calls 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.