# Elastic Cloud: Increased DNS resolution latency in us-east-1

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2020-07-28 10:50 UTC · Resolved: 2020-07-28 12:21 UTC · Duration: 1.5 h
- Updates: 1
- [Vendor status page: https://status.elastic.co/incidents/t1f98sngm0ys](https://status.elastic.co/incidents/t1f98sngm0ys)
- [Company: Elastic Cloud](https://rewindex.com/company/elastic-cloud.md)

## Part of an outage event

- [AWS outage, Jul 28, 2020: 18 vendors, 18 incidents](https://rewindex.com/events/2020-07-28-aws)
- This incident names AWS (location or integration). (hop 1, posted +2 h 20 min vs the first vendor naming AWS)
- Evidence: “…Increased DNS resolution latency in us-east-1 The underlying issue has been mitigated, and we can see DNS resolution times have been restored to expected levels.…”

```mermaid
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>3 vendors, 3 blamed AWS<br/>Honeycomb, Twilio, Chargebee"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>2 vendors, 1 blamed AWS<br/>Stream (GetStream), Elastic Cloud"]:::blames
  root --> h4
  me["Elastic Cloud (this incident)<br/>posted +2 h 20 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** 2020-07-28 12:21 UTC: The underlying issue has been mitigated, and we can see DNS resolution times have been restored to expected levels.

_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/t1f98sngm0ys · Markdown: https://rewindex.com/company/elastic-cloud/incidents/t1f98sngm0ys.md · JSON: https://rewindex.com/api/v1/companies/elastic-cloud/incidents/t1f98sngm0ys · Generated 2026-10-20T00:50:23.975Z