CompaniesElastic CloudIncidents
Elastic Cloud: Increased DNS resolution latency in us-east-1
AWS outage, Jul 28, 2020 · 18 vendors, 18 incidents
Elastic Cloud’s incident names AWS (location or integration). (hop 1, posted +2 h 20 min vs the first vendor naming AWS)
“…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.…”
Swipe sideways to see the whole diagram.
Mermaid source
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 --- meFull 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
- resolved
The underlying issue has been mitigated, and we can see DNS resolution times have been restored to expected levels.
From Elastic Cloud’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
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