Elastic Cloud: Total customer request outage to AWS Frankfurt

No impact listedStatus: resolvedStarted 2019-05-21 20:43 UTCResolved 2019-05-21 20:43 UTC (0 min)1 updatestatus.elastic.co

Timeline of updates

resolved2019-05-21 20:43 UTC
Due to a misconfigured deployment job, rather than removing a percentage of the proxies from the load balancer, the job removed all proxies from the load balancer. All traffic in aws-eu-central-1 (AWS Frankfurt) was impacted from Tues May 21 2019 20:09 to 20:15 UTC. The deployment job was manually updated to decrease deployment time. We're taking immediate action to prevent such a thing from happening again by not changing the default for this deployment job in the future and will add a second layer of verification when it changes. We apologize for the mistake.

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 2019-05-21 20:43 UTC, resolved after 0 min, 1 update(s).

Title: Total customer request outage to AWS Frankfurt
Vendor: Elastic Cloud
Date: 2019-05-21 20:43 UTC
URL: https://rewindex.com/company/elastic-cloud/incidents/s7tsq1m53h98

Elastic Cloud profile Recent Elastic Cloud incidents All outages on May 21, 2019 Elastic Cloud in May 2019 Markdown JSON