Rewindex

CompaniesHeapIncidents

Heap: Potential Impact from AWS Outage

No impact listedStatus: resolvedStarted Resolved (6.0 h)1 updatestatus.heap.io (opens in new tab)
Part of an outage event

AWS outage, Nov 25, 2020 · 28 vendors, 29 incidents

Heap’s incident blames AWS as the cause. (hop 1, posted +3 h 47 min vs the first vendor naming AWS)

“…Potential Impact from AWS Outage All clear.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour1 vendor, 1 blamed AWSPipedream1 to 4 hours later4 vendors, 4 blamed AWSHubSpot, Xero, Lattice, HeapLater2 vendors, 2 blamed AWSConfluent, PipedreamHeap (this incident)posted +3 h 47 min
AWSown incident not archivedWithin an hour1 vendor, 1 blamed AWSPipedream1 to 4 hours later4 vendors, 4 blamed AWSHubSpot, Xero, Lattice, HeapLater2 vendors, 2 blamed AWSConfluent, PipedreamHeap (this incident)posted +3 h 47 min
Heap 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/>1 vendor, 1 blamed AWS<br/>Pipedream"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed AWS<br/>HubSpot, Xero, Lattice, Heap"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed AWS<br/>Confluent, Pipedream"]:::blames
  root --> later
  me["Heap (this incident)<br/>posted +3 h 47 min"]:::me
  h4 --- 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

    All clear.

From Heap’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.heap.io (opens in new tab).

Heap profileRecent Heap incidentsMarkdownJSON