- Level
- confirmed
- Worst impact
- Degraded
- Components
- Voice, Asia, SIP Trunking, Asia
- Regions
- apac, in
What to do
Check whether you use Plivo Voice, Asia, SIP Trunking, Asia in apac, 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 25m it lasted.
Anything that failed between 2026-02-01 13:53 UTC and 2026-02-01 14:19 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 3
- investigating
One of our carrier in India is observing minor call failures towards India phone numbers. A small percentage of phone numbers may experience call failures. 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
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
The carrier has resolved the issue.
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-48faf2d3bf
Is Plivo still down?
No, this incident was resolved 2026-02-01 14:19 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
25m, from 2026-02-01 13:53 UTC to 2026-02-01 14:19 UTC, by the times Plivo posted.
What was affected?
Plivo named Voice, Asia, SIP Trunking, Asia in apac, 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.