- Level
- confirmed
- Worst impact
- Degraded
- Regions
- in
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 26m it lasted.
Anything that failed between 2026-10-10 08:09 UTC and 2026-10-10 08:34 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 Customers, We are currently observing intermittent call failures affecting outbound calls to India. Our team is actively working with our carrier partner to identify the root cause and restore service as quickly as possible. We will provide our next update within the next 30 minutes.
provider
- identified
The issue has been identified and a fix is being implemented.
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-0cdfef47e7
Is Plivo still down?
No, this incident was resolved 2026-10-10 08:34 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
26m, from 2026-10-10 08:09 UTC to 2026-10-10 08:34 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.