CompaniesElastic CloudIncidents
Elastic Cloud: Memory issues in all regions
Timeline of updates
- resolved
We are confident we've isolated the problems that have contributed to the conditions triggering OOM errors. Please reach out via https://discuss.elastic.co/c/cloud (opens in new tab) if you have any problems.
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: minor) posted by Elastic Cloud, started 2017-02-02 05:13 UTC, resolved after 14 d, 1 update(s).
- Title
- Memory issues in all regions
- Vendor
- Elastic Cloud
- Date
- URL
- https://rewindex.com/company/elastic-cloud/incidents/gv1dsth7xdv0
Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on February 2, 2017Elastic Cloud in February 2017MarkdownJSON