- 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 2026-06-15 07:26 UTC and 2026-06-15 06:00 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 call failures in the India region for the 911600 series numbers. After initial investigation, our carrier partner was notified, who took corrective action and the incident was resolved Incident Start Time: 15th June 2026, 11:15 IST Incident End Time: 15th June 2026, 11:45 IST 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-be4901dcdc
Is Plivo still down?
No, this incident was resolved 2026-06-15 06:00 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
0m, from 2026-06-15 07:26 UTC to 2026-06-15 06:00 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.