- Level
- confirmed
- Worst impact
- Degraded
- Regions
- in, us
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 2025-06-05 06:38 UTC and 2025-06-05 05:25 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 1
- resolved
Dear Valued Customer, We recently experienced intermittent outbound call failures affecting users in the India region during the time window specified below. The issue has since been resolved, and all services are currently operating normally. Incident Start Time: 5th June 2025 05:25 UTC Incident End Time: 5th June 2025 05:50 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.
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-10d48127bf
Is Plivo still down?
No, this incident was resolved 2025-06-05 05:25 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
0m, from 2025-06-05 06:38 UTC to 2025-06-05 05:25 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.