Elastic Cloud Incident Report: February 4, 2019 | Elastic Blog