Incident Date | 2021-05-12 |
---|---|
Reference Numbers | CLOUD:81303 |
Incident Start Date (UTC) | 2021-05-12T17:29:26 |
Incident End Date (UTC) | 2021-05-12T20:00:45 |
Incident Duration | 2:31:18 |
Impact Start Date (UTC) | 2021-05-12T16:58:00 |
Impact End Date (UTC) | 2021-05-12T18:13:00 |
Impact Duration | 1 hour 15 minutes |
Loss of access to virtual machines hosting customer deployment instances in Azure Virginia (azure-eastus2) zone 3 due to provider misconfiguration
An incorrect configuration was applied to a storage scale unit by Microsoft resulting in impact on downstream services that relied on the storage resources provided by this scale unit, including several virtual machines we have provisioned to host customer deployments (allocators)
Microsoft rolled back the storage configuration update, restoring access to the affected services, including the virtual machines included in this incident.
UTC Date & Time | Event |
---|---|
2021-05-12T16:58:00 | Provider updates configuration of backend storage scale unit |
2021-05-12T17:09:00 | Elastic Cloud engineers receive first alert of issues with Azure Virginia zone 3 |
2021-05-12T17:29:26 | Incident created for loss of connectivity to virtual machines in Azure Virginia zone 3 |
2021-05-12T17:43:00 | Provider completes rollback of incorrect configuration of backend storage scale unit |
2021-05-12T17:52:00 | Incident posted on Elastic Cloud Status |
2021-05-12T18:00:00 | Received notification from Microsoft of a provider-related issue within this region related to storage scale unit change |
2021-05-12T18:13:00 | Elastic Cloud engineers confirmed access restored to affected virtual machines |
2021-05-12T20:06:00 | Incident marked as resolved on Elastic Cloud Status |