Plivo: Voice and Zentrunk partial outage

What to do

Check whether you use Plivo REST APIs and XML, SIP Trunking, PSTN Calls, Client Calls (Browser & Mobile) and 2 more. 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 27m it lasted.
Anything that failed between 2026-02-01 11:04 UTC and 2026-02-01 11:31 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.

investigatingFeb 1, 2026, 11:04 AM UTC
We are currently investigating call degradation for the Voice API and Zentrunk services.
provider
investigatingFeb 1, 2026, 11:26 AM UTC
We are continuing to investigate this issue.
provider
resolvedFeb 1, 2026, 11:31 AM UTC
We observed elevated latency for approximately 10 minutes, which may have briefly affected performance for some users. The underlying issue was identified and addressed, and the system has since returned to normal operation.
provider

Reports count in aggregate; nothing about you is shown.

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Is Plivo still down?

No, this incident was resolved 2026-02-01 11:31 UTC. For Plivo's live state, see https://down.guide/plivo.

How long did it last?

27m, from 2026-02-01 11:04 UTC to 2026-02-01 11:31 UTC, by the times Plivo posted.

What was affected?

Plivo named REST APIs and XML, SIP Trunking, PSTN Calls, Client Calls (Browser & Mobile) and 2 more.

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.