CompaniesElastic CloudIncidents
Elastic Cloud: [Scheduled] AWS Tokyo Proxy replacement
Timeline of updates
- resolved
The scheduled maintenance has been completed.
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
Maintenance posted by Elastic Cloud, started 2018-05-08 00:30 UTC, resolved after 4.0 h, 1 update(s).
- Title
- [Scheduled] AWS Tokyo Proxy replacement
- Vendor
- Elastic Cloud
- Date
- URL
- https://rewindex.com/company/elastic-cloud/incidents/wnkzj0rxrtyx
Elastic Cloud profileRecent Elastic Cloud incidentsAll outages on May 8, 2018Elastic Cloud in May 2018MarkdownJSON