- Level
- confirmed
- Worst impact
- Degraded
- Components
- SMS API, Verify API
- Down Index
- 9of 100
What to do
Check whether you use Plivo SMS API, Verify API. 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-10-29 14:33 UTC and 2025-10-29 14:33 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
We experienced intermittent SMS message failures between 13:50 UTC and 13:59 UTC on 29th Oct 2025 due to an underlying infrastructure failure. The issue was auto-recovered, and all systems have since stabilized. Message processing has fully recovered, and the platform is operating normally. Incident Start Time: 29th Oct 2025 13:50 UTC Incident End Time: 29th Oct 2025 13:59 UTC
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-f87da0860b
Is Plivo still down?
No, this incident was resolved 2025-10-29 14:33 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
0m, from 2025-10-29 14:33 UTC to 2025-10-29 14:33 UTC, by the times Plivo posted.
What was affected?
Plivo named SMS API, Verify API.
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.