Plivo

First posted only after it was over

20% 10 of the 50 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

Plivo: higher than most vendors.

Time to resolve

2 h 10 min median; 9 in 10 within 10 h 36 minbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

Plivo: around the middle.

Major or critical incidents

0.4 a month 5 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

Plivo: lower than most vendors.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

Plivo depends on

Who depends on Plivo

Runs in (named in its incidents): AWS ap-southeast-1 (1).

Outage events: Meta, Jun 12, AWS, Jun 13, 2023 (timing), Cloudflare, Jun 21, 2022 (timing), AWS, Mar 9, 2022 (timing), AWS us-east-1, Dec 22, 2021 (timing), AWS, Dec 15, 2021 (timing), AWS us-east-1, Dec 7, 2021 (timing), AWS, Jul 28, 2020 (timing) and 1 more.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Full Plivo change history

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

Plivo incidents, last 90 daysJSONMarkdown