- Level
- confirmed
- Worst impact
- Degraded
- Components
- Endpoint calls (SIP)
- Regions
- us
- Down Index
- 20of 100
What to do
Check whether you use Plivo Endpoint calls (SIP) 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 29m it lasted.
Anything that failed between 2025-04-21 02:38 UTC and 2025-04-21 03:07 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 call failures impacting inbound SIP calls. All other services remain fully operational. Our engineers are actively working to resolve the issue and restore service. If you have any questions, please contact Plivo Support. 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-9f28367f07
Is Plivo still down?
No, this incident was resolved 2025-04-21 03:07 UTC. For Plivo's live state, see https://down.guide/plivo.
How long did it last?
29m, from 2025-04-21 02:38 UTC to 2025-04-21 03:07 UTC, by the times Plivo posted.
What was affected?
Plivo named Endpoint calls (SIP) 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.