Rewindex

CompaniesElastic CloudIncidents

Elastic Cloud: Connectivity issue in AWS us-east-1

MinorStatus: resolvedStarted Resolved (14 h)1 updatestatus.elastic.co (opens in new tab)
Part of an outage event

AWS us-east-1 outage, Dec 22, 2021 · 40 vendors, 40 incidents

Elastic Cloud’s incident names AWS / us-east-1 (location or integration). (hop 1, posted +36 min vs the first vendor naming AWS)

“…Connectivity issue in AWS us-east-1 This incident has been resolved.…”

Swipe sideways to see the whole diagram.

AWS us-east-1own incident not archivedWithin an hour8 vendors, 6 blamed AWSFirebolt, Bitbucket, HubSpot, CircleCI +41 to 4 hours later1 vendorConfluentElastic Cloud (this incident)posted +36 min
AWS us-east-1own incident not archivedWithin an hour8 vendors, 6 blamed AWSFirebolt, Bitbucket, HubSpot,CircleCI +41 to 4 hours later1 vendorConfluentElastic Cloud (this incident)posted +36 min
Elastic Cloud is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>8 vendors, 6 blamed AWS<br/>Firebolt, Bitbucket, HubSpot, CircleCI +4"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor<br/>Confluent"]:::names
  root --> h4
  me["Elastic Cloud (this incident)<br/>posted +36 min"]:::me
  h1 --- 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 Elastic Cloud’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.elastic.co (opens in new tab).

Elastic Cloud profileRecent Elastic Cloud incidentsMarkdownJSON