Rewindex

CompaniesElastic CloudIncidents

Elastic Cloud: Availability issues with aws-eu-north-1c (AWS Stockholm)

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

AWS outage, Feb 13, 2025 · 11 vendors, 11 incidents

Elastic Cloud’s incident blames AWS as the cause. (hop 1, posted +1 h 33 min vs the first vendor naming AWS)

“…Availability issues with aws-eu-north-1c (AWS Stockholm) AWS has confirmed that they have entirely resolved the outage.…”

Swipe sideways to see the whole diagram.

AWSown incident not archivedWithin an hour2 vendors, 1 blamed AWSCourier, Teleport1 to 4 hours later5 vendors, 4 blamed AWSCoralogix, SingleStore, Aptible, Snowflake +1Later1 vendor, 1 blamed AWSGrafana CloudElastic Cloud (this incident)posted +1 h 33 min
AWSown incident not archivedWithin an hour2 vendors, 1 blamed AWSCourier, Teleport1 to 4 hours later5 vendors, 4 blamed AWSCoralogix, SingleStore, Aptible,Snowflake +1Later1 vendor, 1 blamed AWSGrafana CloudElastic Cloud (this incident)posted +1 h 33 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/>2 vendors, 1 blamed AWS<br/>Courier, Teleport"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>5 vendors, 4 blamed AWS<br/>Coralogix, SingleStore, Aptible, Snowflake +1"]:::blames
  root --> h4
  later["Later<br/>1 vendor, 1 blamed AWS<br/>Grafana Cloud"]:::blames
  root --> later
  me["Elastic Cloud (this incident)<br/>posted +1 h 33 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

    AWS has confirmed that they have entirely resolved the outage.

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