outages.live
Live
P

Plivo

Plivo is operational

Checked 34 s ago Operational

History

90 days agoToday

Incidents in 90 days

3

Days with an incident

3

Median duration

33 min

Longest incident

6 h 51 min

Components

45

Voice API

REST APIs and XML Operational
90 days ago1 day with an incidentToday
PSTN Calls Operational
90 days ago1 day with an incidentToday
Client Calls (Browser & Mobile) Operational
90 days agoNo incidentsToday
Conference Operational
90 days agoNo incidentsToday
Recordings Operational
90 days agoNo incidentsToday
Text-to-Speech Operational
90 days agoNo incidentsToday
Transcription Operational
90 days agoNo incidentsToday
Speech Recognition Operational
90 days agoNo incidentsToday
Endpoint calls (SIP) Operational
90 days agoNo incidentsToday
BYOC Operational
90 days agoNo incidentsToday
Answering Machine detection Operational
90 days agoNo incidentsToday
CDR (Call Detail Records) Operational
90 days agoNo incidentsToday

SIP Trunking

SIP Trunking Operational
90 days agoNo incidentsToday

Messaging API

SMS API Operational
90 days agoNo incidentsToday
MMS API Operational
90 days agoNo incidentsToday
Powerpack SMS Operational
90 days agoNo incidentsToday
Powerpack MMS Operational
90 days agoNo incidentsToday
Verify API Operational
90 days agoNo incidentsToday

Carrier Partners: Messaging API

Longcode SMS, USA & Canada Operational
90 days agoNo incidentsToday
Shortcode SMS, USA & Canada Operational
90 days agoNo incidentsToday
Toll-free SMS, USA & Canada Operational
90 days agoNo incidentsToday
MMS, USA & Canada Operational
90 days agoNo incidentsToday
SMS, Mexico & South America Operational
90 days agoNo incidentsToday
SMS, Asia Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

Oct 10, 2026

Duration26 min08:09 to 08:34Intermittent Call failures towards IndiaNotice

This incident has been resolved.

Sep 11, 2026

Duration33 min06:02 to 06:35Intermittent Call failures towards IndiaNotice

This incident has been resolved

Aug 25, 2026

Duration6 h 51 min07:25 to 14:16Voice Call Webhook Delivery DegradationNotice

This incident has been resolved.

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

Go from tracking outages to fixing production issues with Polylane.

Try Polylane