Plivo reported "Voice Call Webhook Delivery Degradation" on its status page at 2026-08-25 07:25 UTC.

When did the incident start and end?

It started at 2026-08-25 07:25 UTC and ended at 2026-08-25 14:16 UTC. It lasted 6 h 51 min.

How do I get alerts for Plivo?

Subscribe to the Plivo live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Plivo. outages.live reads it every few minutes and keeps every update.

PPlivoIncident · 2026-08-25 07:25 UTC

Voice Call Webhook Delivery Degradation

Q: What is affected?

Plivo lists these components: REST APIs and XML, PSTN Calls, Voice API - REST APIs and XML, Voice API - PSTN Calls.

ResolvedOfficial update

This incident has been resolved.

The latest update from Plivo.

State

Resolved

Started

69 d ago

2026-08-25 07:25 UTC

Lasted

6 h 51 min

until 2026-08-25 14:16 UTC

Worst impact

Notice

Timeline

3 updates

07:2509:0810:5112:3414:16

NoticeUpdate postedTimes in UTC

Identified

15 min 4%

Monitoring

6 h 36 min 96%

Updates

Times in UTC

As posted by Plivo

Resolved2026-08-25 14:16 UTC

This incident has been resolved.

Monitoring2026-08-25 07:41 UTC

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

Identified2026-08-25 07:25 UTC

Dear Valued Customers, We are currently observing an intermittent issue where a subset of voice calls are not triggering status callbacks, including ringing, hangup, and call-status webhook events. Call processing itself is unaffected, and calls are connecting and completing normally. We have identified the cause as a degraded event-processing component on a subset of our media servers and are actively working on remediation. The impact is intermittent, and most calls continue to receive webhooks normally.

Affected components

REST APIs and XMLPSTN CallsVoice API - REST APIs and XMLVoice API - PSTN Calls

Plivo in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

33 min

This incident

12× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

6 h 51 min

median 33 min

90 days agoToday

Other Plivo incidents

All incidents

Plivo·Intermittent Call failures towards India

This incident has been resolved.

Resolvedresolved 23 d ago

Plivo·Intermittent Call failures towards India

This incident has been resolved

Resolvedresolved 52 d ago

Follow Plivo

Your coding agent knows when Plivo is down, and tells you when a failure is theirs, not yours. You can also get Plivo incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "plivo" and tell me if Plivo has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=plivo

Slack

/feed subscribe https://outages.cc/feed.xml?providers=plivo

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane