CompaniesElastic CloudIncidents
Elastic Cloud: Problem with warm and cold instances (only in sa-east-1)
Timeline of updates
- resolved
We have applied the fix for the UI to stop allowing the warm/cold selection when creating or modifying deployments in the 'sa-east-1' AWS region. There were a small handful of deployments we had to run individual fixes against (7 in total) to correct their backing data in light of the UI change so you may see a recent plan run by us in your activity feed, this is nothing to worry about. This issue is now resolved, however please don't hesitate to reach out to us via our support channels if you have any issues or questions, and we would like to thank you for your patience as we sorted through this.
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 2021-02-15 13:22 UTC, resolved after 2 d, 1 update(s).
- Title
- Problem with warm and cold instances (only in sa-east-1)
- Vendor
- Elastic Cloud
- Date
- URL
- https://rewindex.com/company/elastic-cloud/incidents/8krht894b08l
Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on February 15, 2021Elastic Cloud in February 2021MarkdownJSON