rewindex

CompaniesElastic CloudIncidents

Elastic Cloud: Delayed Elasticsearch monitoring data (logs) in AWS us-east-1

No impact listedStatus: resolvedStarted Resolved (3.7 h)1 updatestatus.elastic.co (opens in new tab)

Timeline of updates

  1. resolved

    We identified that issue related to spike in amount of ingesting monitoring data. We've added resources to impacted component. We've observed recovery in terms of delays in logs UI on Elastic Cloud Console. Incident is closed.

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).

Cite this

Status incident (vendor impact label: none) posted by Elastic Cloud, started 2020-11-27 04:39 UTC, resolved after 3.7 h, 1 update(s).

Title
Delayed Elasticsearch monitoring data (logs) in AWS us-east-1
Vendor
Elastic Cloud
Date
URL
https://rewindex.com/company/elastic-cloud/incidents/38xmvnncxsgp

Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on November 27, 2020Elastic Cloud in November 2020MarkdownJSON