- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 24of 100
What to do
Check whether you use Plivo 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 2h 39m it lasted.
Anything that failed between 2025-06-20 18:09 UTC and 2025-06-20 20:48 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
Dear Valued Customer, We are currently experiencing intermittent issues impacting SMS and Verify requests. Our engineering team is actively investigating and working to resolve the issue as quickly as possible. If you have any questions, please get in touch with Plivo Support. Support portal: https://support.plivo.com/hc/en-us
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-310000ca4d
Is Plivo still down?
No, this incident was resolved 2025-06-20 20:48 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
2h 39m, from 2025-06-20 18:09 UTC to 2025-06-20 20:48 UTC, by the times Plivo posted.
What was affected?
Plivo named 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.