CompaniesElastic CloudIncidents
Elastic Cloud: Automated snapshot failures
Timeline of updates
- resolved
We’ve set up an automated process to snapshot affected clusters. The permanent fix for affected clusters will be going out with our next scheduled deployment. As the impact is now remediated, we’re closing this incident. If you have any additional concerns, please reach out to your support team! Thank you for your patience!
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 2020-03-04 21:04 UTC, resolved after 22 h, 1 update(s).
- Title
- Automated snapshot failures
- Vendor
- Elastic Cloud
- Date
- URL
- https://rewindex.com/company/elastic-cloud/incidents/739vlmfl3mcj
Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on March 4, 2020Elastic Cloud in March 2020MarkdownJSON