rewindex

CompaniesPlivoIncidents

Plivo: Inbound call failure & Inbound SMS failure towards US & Canada phone numbers

MinorStatus: resolvedStarted Resolved (2.0 h)1 updatestatus.plivo.com (opens in new tab)
Part of an outage event

AWS outage, Jul 28, 2020 · 10 vendors, 11 incidents

Plivo’s incident started inside the event window. (hop 1)

Swipe sideways to see the whole diagram.

depends on AWSAWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSHoneycomb, Twilio, Chargebee1 to 4 hours later2 vendors, 1 blamed AWSStream (GetStream), Elastic CloudKnown dependency5 vendorsDatadog, Mapbox, Klaviyo, Bandwidth +1
depends on AWSAWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSHoneycomb, Twilio, Chargebee1 to 4 hours later2 vendors, 1 blamed AWSStream (GetStream), ElasticCloudKnown dependency5 vendorsDatadog, Mapbox, Klaviyo,Bandwidth +1
Plivo is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 3 blamed AWS<br/>Honeycomb, Twilio, Chargebee"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Stream (GetStream), Elastic Cloud"]:::blames
  root --> h4
  dr["Known dependency<br/>5 vendors<br/>Datadog, Mapbox, Klaviyo, Bandwidth +1"]:::hop2
  root -.->|"depends on AWS"| dr

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    This incident has been resolved.

From Plivo’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.plivo.com (opens in new tab).

Cite this

Status incident (vendor impact label: minor) posted by Plivo, started 2020-07-28 10:32 UTC, resolved after 2.0 h, 1 update(s).

Title
Inbound call failure & Inbound SMS failure towards US & Canada phone numbers
Vendor
Plivo
Date
URL
https://rewindex.com/company/plivo/incidents/1r2j4y8d53yn

Plivo profileRecent Plivo incidentsAll outages on July 28, 2020Plivo in July 2020MarkdownJSON