rewindex

CompaniesPlivoMonthly reportsFebruary 2017

Plivo in February 2017: incidents, uptime and changes

6incidents posted
5labelled major or critical
99.14%free of major/critical
98.78%free of any incident
0price changes
0notable page changes

Vendor-reported outage time 5 h 44 min, incident time 8 h 9 min. 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. Last 90 days.

By vendor label: Critical 2 · Major 3 · Minor 1

Major and critical incidents 5

IncidentImpactStartedDurationStatusDay
Network issue from our hosting providerCritical0 minresolved02-10
SIP and WebRTC registration issueCritical0 minresolved02-14
Elevated Authentication errorMajor0 minresolved02-17
Call congestion for US terminationMajor0 minresolved02-22
AWS OutageMajor7.3 hresolved02-28

Other incidents 1

IncidentImpactStartedDurationStatusDay
Inbound Carrier issueMinor2.4 hresolved02-27

Cite this

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

Title
Plivo in February 2017
Vendor
Plivo
Date
URL
https://rewindex.com/company/plivo/2017/02

All Plivo monthsRecent incidentsMarkdown