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

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-02-14 00:06 UTC · Resolved: 2025-02-14 06:37 UTC · Duration: 6.5 h
- Updates: 1
- [Vendor status page: https://status.elastic.co/incidents/lbwb12jvjm4c](https://status.elastic.co/incidents/lbwb12jvjm4c)
- [Company: Elastic Cloud](https://rewindex.com/company/elastic-cloud.md)

## Part of an outage event

- [AWS outage, Feb 13, 2025: 11 vendors, 11 incidents](https://rewindex.com/events/2025-02-13-aws)
- This incident blames AWS as the cause. (hop 1, posted +1 h 33 min vs the first vendor naming AWS)
- Evidence: “…Availability issues with aws-eu-north-1c (AWS Stockholm) AWS has confirmed that they have entirely resolved the outage.…”

```mermaid
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
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2025-02-14 06:37 UTC: AWS has confirmed that they have entirely resolved the outage.

_From the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._


---
Canonical: https://rewindex.com/company/elastic-cloud/incidents/lbwb12jvjm4c · Markdown: https://rewindex.com/company/elastic-cloud/incidents/lbwb12jvjm4c.md · JSON: https://rewindex.com/api/v1/companies/elastic-cloud/incidents/lbwb12jvjm4c · Generated 2026-10-19T23:14:21.236Z