- Level
- confirmed
- Worst impact
- Degraded
- Components
- SMS API
- Regions
- us
What to do
Check whether you use Plivo SMS API 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 1d 2h it lasted.
Anything that failed between 2026-01-07 08:25 UTC and 2026-01-08 11:01 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 2
- investigating
We are currently investigating reports of delivery issues affecting a subset of 10DLC traffic. Impacted customers may observe messages marked as DELIVERED in logs, even though these messages may not have been successfully delivered to the handset. This issue has been escalated to our carrier partners, and we are awaiting an update on the routing path.
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-4b2ec0182f
Is Plivo still down?
No, this incident was resolved 2026-01-08 11:01 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
1d 2h, from 2026-01-07 08:25 UTC to 2026-01-08 11:01 UTC, by the times Plivo posted.
What was affected?
Plivo named SMS API 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.