CompaniesElastic CloudIncidents
Elastic Cloud: Issues searching for deployments in AWS Frankfurt region
Timeline of updates
- resolved
Deployments created in the AWS Frankfurt region are now searchable and visible again in the UI. We have traced it back to an issue where the component responsible for making deployments searchable was not being notified about new or modified deployments. Existing deployments were fully functional during the incident. We will continue the investigation into the root cause behind this incident.
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-01-24 12:02 UTC, resolved after 2.0 h, 1 update(s).
- Title
- Issues searching for deployments in AWS Frankfurt region
- Vendor
- Elastic Cloud
- Date
- URL
- https://rewindex.com/company/elastic-cloud/incidents/8lwnyy9hgh71
Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on January 24, 2020Elastic Cloud in January 2020MarkdownJSON