Plivo Outage History
41 incidents recorded over the last 365 days, 25 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Plivo Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 13, 2026 | Planned maintenance - India carrier layerScheduled maintenance is currently in progress. We will provide updates as necessary. | 2h 0m | Scheduled |
| Aug 5, 2026 | Planned maintenance - India carrier layerThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jul 31, 2026 | Call failures towards IndiaThis incident has been resolved. | 10h 36m | Resolved |
| Jul 20, 2026 | Intermittent Call failures towards IndiaThis incident has been resolved. | 3h 9m | Resolved |
| Jul 17, 2026 | Planned Maintenance: Intermittent Voice Call Failures to IndiaThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jul 16, 2026 | Planned Maintenance: Intermittent Voice Call Failures to IndiaThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Jul 11, 2026 | Outbound MMS Failures on Toll-Free Numbers (US & Canada)This incident has been resolved. | 2h 9m | Resolved |
| Jul 2, 2026 | Outbound Call FailuresThis incident has been resolved. | 2h 49m | Resolved |
| Jun 30, 2026 | Outbound Call Failures for Specific 9180 Caller IDsThis incident has been resolved. | 1h 44m | Resolved |
| Jun 19, 2026 | Call Failures in US and India regionsThis incident has been resolved. | 56 min | Resolved |
| Jun 15, 2026 | Call failures for 911600 series numbers in India regionDear Valued Customer, We recently experienced call failures in the India region for the 911600 series numbers. After initial investigation, our carrier partner was notified, who took corrective action and the incident… | -86 min | Resolved |
| Jun 12, 2026 | WhatsApp Business API — Elevated Errors and DelaysThis incident has been resolved. | 50 min | Resolved |
| Jun 12, 2026 | Intermittent Outbound call failures in India region for 9180 seriesThis incident has been resolved. | 3h 52m | Resolved |
| Jun 8, 2026 | Elevated Call Failure Rate on 9180 Number Series(India Region)Incident Summary — Elevated Call Failure Rate on 9180 Number Series. Specific number series of 9180 were impacted for outbound calls. Incident Window: 5th June 2026, 6:30 PM IST — 6th June 11:30 AM… | -2437 min | Resolved |
| May 16, 2026 | Maintenance on Plivo DatabaseThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| May 12, 2026 | Inbound call failures in India regionDear Valued Customer, We recently experienced intermittent Inbound Call failures in India region. Our engineering and operations teams promptly investigated and resolved the issue. The root cause was identified, and… | -36 min | Resolved |
| May 10, 2026 | Maintenance on Plivo ConsoleThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| May 3, 2026 | Maintenance on Plivo Voice DatabaseThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Apr 26, 2026 | Maintenance on Plivo DatabaseThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Apr 8, 2026 | PHLO: Inbound call failures — sub-account numbers on main account PHLO appsDear Valued Customer, We observed some inbound calls to PHLO applications were not being processed successfully. This affected a specific configuration where a phone number rented to a sub-account was attached to a… | 0 min | Resolved |
| Mar 28, 2026 | Missing Web hook Events for Voice Calls in India RegionThis incident has been resolved | 1h 29m | Resolved |
| Feb 9, 2026 | Voice calls are impacted due to infrastructure issue in US region.This incident has been resolved. | 1h 0m | Resolved |
| Feb 9, 2026 | Failures to retrieve CDRs in India RegionThis incident has been resolved. | 27 min | Resolved |
| Feb 8, 2026 | Service degradation - Intermittent Messaging FailuresThis incident has been resolved. | 3h 29m | Resolved |
| Feb 8, 2026 | Scheduled Messaging Platform MaintenanceThe scheduled maintenance has been completed. | 4h 0m | Scheduled |
| Feb 5, 2026 | Outbound call failures in India region for 160 seriesThis incident has been resolved. | 4h 21m | Resolved |
| Feb 1, 2026 | Carrier degradation IndiaThe carrier has resolved the issue. | 25 min | Resolved |
| Feb 1, 2026 | Voice and Zentrunk partial outageWe 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… | 27 min | Resolved |
| Jan 14, 2026 | Voice API Intermittent Failures (India Region)Incident Summary — Intermittent Voice API Failures (India Region) Incident Window: 12 January, 10:30 AM IST — 11:46 AM IST Impact: Intermittent failures were observed across multiple Voice APIs in the India region… | -3406 min | Resolved |
| Jan 7, 2026 | Delivery issue with outbound SMS to the US from certain 10DLC campaigns.This incident has been resolved. | 26h 36m | Resolved |
| Oct 29, 2025 | Intermittent Message FailuresWe experienced intermittent SMS message failures between 13:50 UTC and 13:59 UTC on 29th Oct 2025 due to an underlying infrastructure failure. The issue was auto-recovered, and all systems have since… | 0 min | Resolved |
| Oct 29, 2025 | Outbound call failures in India Bangalore RegionThis incident has been resolved. | 2h 28m | Resolved |
| Oct 26, 2025 | Intermittent SMS failures in India RegionThis incident has been resolved. | 12h 38m | Resolved |
| Oct 7, 2025 | Intermittent Message failures in India RegionDear Valued Customer, We recently experienced intermittent SMS failures. Our engineering and operations teams promptly investigated and resolved the issue. The root cause was identified, and corrective actions have… | -1009 min | Resolved |
| Sep 20, 2025 | Maintenance on Plivo DatabaseThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Sep 14, 2025 | Maintenance on Plivo ConsoleThe scheduled maintenance has been completed. | 3h 0m | Scheduled |
| Sep 8, 2025 | Maintenance on Plivo ConsoleThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Sep 5, 2025 | Maintenance on Plivo Number Porter DatabaseThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Sep 4, 2025 | Maintenance on Plivo Number DatabaseThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
| Sep 3, 2025 | Maintenance on Plivo ConsoleThe scheduled maintenance has been completed. | 2h 0m | Scheduled |
| Aug 29, 2025 | Maintenance on Plivo PHLO DBThe scheduled maintenance has been completed. | 1h 0m | Scheduled |
How to Read This Plivo Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Plivo acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Plivo outage in this window ran 1d 2h, against a mean recovery of 3h 12m. If you depend on Plivo in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.