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 · 18 vendors, 18 incidents

Plivo’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +2 h 2 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSHoneycomb, Twilio, Chargebee1 to 4 hours later2 vendors, 1 blamed AWSStream (GetStream), Elastic CloudPlivo (this incident)posted +2 h 2 min
same windowAWSown incident not archivedWithin an hour3 vendors, 3 blamed AWSHoneycomb, Twilio, Chargebee1 to 4 hours later2 vendors, 1 blamed AWSStream (GetStream), ElasticCloudPlivo (this incident)posted +2 h 2 min
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
  me["Plivo (this incident)<br/>posted +2 h 2 min"]:::me
  root -.->|"same window"| me

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.

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

Plivo profileRecent Plivo incidentsMarkdownJSON