Skip to main content
Plivo

Service degradation - Intermittent Messaging Failures

Operational Lasted 3h 30m · started · Plivo's page

Level
confirmed
Worst impact
Operational
Components
SMS API, Verify API
Regions
us

What to do

  • Check whether you use Plivo SMS API, Verify 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 3h 30m it lasted.

    Anything that failed between 2026-02-08 13:41 UTC and 2026-02-08 17:11 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 intermittent message failures affecting a subset of Messaging traffic. Our engineering teams have identified the issue and are actively working to stabilize the service. Other platform services continue to operate normally. We are closely monitoring the situation and will provide further updates as progress is made. We apologize for any inconvenience caused and appreciate your patience while we work toward a resolution. If you have any questions, please get in touch with Plivo Support. Support portal: https://support.plivo.com/hc/en-us Sincerely, Plivo Team

    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-51b8c04612

Is Plivo still down?

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

How long did it last?

3h 30m, from 2026-02-08 13:41 UTC to 2026-02-08 17:11 UTC, by the times Plivo posted.

What was affected?

Plivo named SMS API, Verify 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.