Skip to main content
Plivo

Outbound Call Failures

Degraded Lasted 2h 49m · started · Plivo's page

Level
confirmed
Worst impact
Degraded
Components
REST APIs and XML, PSTN Calls, Client Calls (Browser & Mobile), Conference, Recordings, Text-to-Speech, Transcription, Speech Recognition, Endpoint calls (SIP), BYOC, Answering Machine detection
Regions
us
Down Index
25of 100

What to do

  • Check whether you use Plivo REST APIs and XML, PSTN Calls, Client Calls (Browser & Mobile), Conference and 7 more 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 49m it lasted.

    Anything that failed between 2026-07-02 13:40 UTC and 2026-07-02 16:29 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

  1. investigating

    Dear Valued Customer, We are currently experiencing a full outbound call outage. Our team is actively engaged and working to identify the root cause and restore service as quickly as possible. We will share our next update within 30 minutes, or sooner if there is a material change. For urgent concerns, please contact Plivo Support: https://support.plivo.com/hc/en-us

    provider

  2. monitoring

    A fix has been implemented and we are monitoring the results.

    provider

  3. 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-af0130dc92

Is Plivo still down?

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

How long did it last?

2h 49m, from 2026-07-02 13:40 UTC to 2026-07-02 16:29 UTC, by the times Plivo posted.

What was affected?

Plivo named REST APIs and XML, PSTN Calls, Client Calls (Browser & Mobile), Conference and 7 more 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.