Rewindex

CompaniesElastic CloudIncidents

Elastic Cloud: AWS EC2 Network Issues in us-east-1 region

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

AWS outage, Sep 28, 2023 · 23 vendors, 24 incidents

Elastic Cloud’s incident names AWS (location or integration). (hop 1, posted +3 h 12 min vs the first vendor naming AWS)

“…AWS EC2 Network Issues in us-east-1 region The AWS network connectivity has been restored on the us-east-1 region (use1-az2 zone). Everything is operating normally in the region.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSAbly, Temporal Cloud, Keeper1 to 4 hours later4 vendors, 3 blamed AWSDremio, Firebolt, CockroachDB, Elastic CloudLater3 vendors, 1 blamed AWSAptible, Temporal Cloud, ConfluentElastic Cloud (this incident)posted +3 h 12 min
AWSown incident not archivedWithin an hour3 vendors, 1 blamed AWSAbly, Temporal Cloud, Keeper1 to 4 hours later4 vendors, 3 blamed AWSDremio, Firebolt, CockroachDB,Elastic CloudLater3 vendors, 1 blamed AWSAptible, Temporal Cloud,ConfluentElastic Cloud (this incident)posted +3 h 12 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<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 1 blamed AWS<br/>Ably, Temporal Cloud, Keeper"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 3 blamed AWS<br/>Dremio, Firebolt, CockroachDB, Elastic Cloud"]:::blames
  root --> h4
  later["Later<br/>3 vendors, 1 blamed AWS<br/>Aptible, Temporal Cloud, Confluent"]:::blames
  root --> later
  me["Elastic Cloud (this incident)<br/>posted +3 h 12 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

    The AWS network connectivity has been restored on the us-east-1 region (use1-az2 zone). Everything is operating normally in the region.

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