# Plivo in February 2026: incidents, uptime and changes

> Plivo in February 2026: 6 incidents on its status page (1 major or critical), 99.35% free of major or critical incidents (vendor-reported). From Rewindex’s archive of Plivo’s status, pricing and policy pages.

Canonical: https://rewindex.com/company/plivo/2026/02
Last updated: 2026-03-01T00:00:00Z

- Incidents posted: 6 (major/critical: 1) · Maintenance: 1
- By vendor impact label: critical 1, minor 2, none 3
- Uptime (vendor-reported): 99.35% free of major/critical incidents, 99.13% free of any incident; outage time 4 h 21 min, incident time 5 h 49 min
- Price changes: 0 · Pricing/legal/trust page changes: 0 · Deprecations: 0 · CVEs: 0
- Previous month: [January 2026](https://rewindex.com/company/plivo/2026/01.md) · Next: [March 2026](https://rewindex.com/company/plivo/2026/03.md) · [All months](https://rewindex.com/company/plivo/reports.md) · [Plivo](https://rewindex.com/company/plivo.md)

_Uptime: Derived from the incidents the vendor posted on its own status page, not measured by us. A minute counts as an outage minute when a major or critical incident (as the vendor labelled it) was open; incident minutes include minor ones too. Maintenance and incidents marked "no impact" are left out, overlapping incidents are merged, a resolved incident counts for at most 7 days, and one still open with no resolution counts for at most 24 hours._

## Major and critical incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Outbound call failures in India region for 160 series](https://rewindex.com/company/plivo/incidents/r2trzxz056dp.md) | critical | 2026-02-05 08:39 UTC | 2026-02-05 13:01 UTC | 4.3 h | resolved |

## All incidents

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [Voice and Zentrunk partial outage](https://rewindex.com/company/plivo/incidents/bm7s8j5m9yzv.md) | none | 2026-02-01 11:04 UTC | 2026-02-01 11:31 UTC | 27 min | resolved |
| [Carrier degradation India](https://rewindex.com/company/plivo/incidents/dp7s9k3c1gyy.md) | none | 2026-02-01 13:53 UTC | 2026-02-01 14:19 UTC | 25 min | resolved |
| [Outbound call failures in India region for 160 series](https://rewindex.com/company/plivo/incidents/r2trzxz056dp.md) | critical | 2026-02-05 08:39 UTC | 2026-02-05 13:01 UTC | 4.3 h | resolved |
| [Service degradation - Intermittent Messaging Failures](https://rewindex.com/company/plivo/incidents/cxsj0gsz0b13.md) | none | 2026-02-08 13:41 UTC | 2026-02-08 17:11 UTC | 3.5 h | resolved |
| [Failures to retrieve CDRs in India Region](https://rewindex.com/company/plivo/incidents/9mp420ndxr91.md) | minor | 2026-02-09 12:25 UTC | 2026-02-09 12:52 UTC | 28 min | resolved |
| [Voice calls are impacted due to infrastructure issue in US region.](https://rewindex.com/company/plivo/incidents/86yzvvc6718y.md) | minor | 2026-02-09 14:59 UTC | 2026-02-09 15:59 UTC | 1.0 h | resolved |

## Maintenance

| Incident | Impact (vendor label) | Started (UTC) | Resolved (UTC) | Duration | Status |
| --- | --- | --- | --- | --- | --- |
| [\[Scheduled\] Scheduled Messaging Platform Maintenance](https://rewindex.com/company/plivo/incidents/tj5mhb7667mk.md) | maintenance | 2026-02-08 03:30 UTC | 2026-02-08 06:48 UTC | 3.3 h | resolved |

## Cite this

Plivo posted 6 status incidents in February 2026 (1 major or critical); 0 price changes and 0 notable page changes observed.

- Canonical URL: https://rewindex.com/company/plivo/2026/02
- Citation: Plivo, “Plivo in February 2026” (2026-02-01 00:00 UTC). Archived by Rewindex: https://rewindex.com/company/plivo/2026/02 (CC BY 4.0).
- Markdown link: `[Plivo: Plivo in February 2026 (2026-02-01)](https://rewindex.com/company/plivo/2026/02)`


---
Canonical: https://rewindex.com/company/plivo/2026/02 · Markdown: https://rewindex.com/company/plivo/2026/02.md · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-04T10:25:47.442Z
