# Elastic Cloud: Connectivity issues with AWS Ohio (us-east-2)

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2022-07-28 17:11 UTC · Resolved: 2022-07-28 21:15 UTC · Duration: 4.1 h
- Updates: 1
- [Vendor status page: https://status.elastic.co/incidents/rj16ndy670qs](https://status.elastic.co/incidents/rj16ndy670qs)
- [Company: Elastic Cloud](https://rewindex.com/company/elastic-cloud.md)

## Part of an outage event

- [AWS us-east-2 outage, Jul 28, 2022: 25 vendors, 26 incidents](https://rewindex.com/events/2022-07-28-aws-us-east-2)
- This incident names AWS / us-east-2 (location or integration). (hop 1, posted +0 min vs the first vendor naming AWS)
- Evidence: “…Connectivity issues with AWS Ohio (us-east-2) All affected customer deployments have been remediated and all cluster administration tasks are operational.…”

```mermaid
flowchart LR
  root["AWS us-east-2<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>5 vendors, 2 blamed AWS<br/>Elastic Cloud, Coralogix, Confluent, Aptible +1"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor, 1 blamed AWS<br/>Stream (GetStream)"]:::blames
  root --> h4
  me["Elastic Cloud (this incident)<br/>posted +0 min"]:::me
  h1 --- 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** 2022-07-28 21:15 UTC: All affected customer deployments have been remediated and all cluster administration tasks are operational.

_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/rj16ndy670qs · Markdown: https://rewindex.com/company/elastic-cloud/incidents/rj16ndy670qs.md · JSON: https://rewindex.com/api/v1/companies/elastic-cloud/incidents/rj16ndy670qs · Generated 2026-10-20T01:31:00.873Z