Elastic.io incident

Issues with creating/updating Deployments in several regions

Major Resolved View vendor source →

Elastic.io experienced a major incident on June 17, 2026 affecting Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2 and Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west4 and 1 more component, lasting 1h 42m. The incident has been resolved; the full update timeline is below.

Started
Jun 17, 2026, 03:52 PM UTC
Resolved
Jun 17, 2026, 05:35 PM UTC
Duration
1h 42m
Detected by Pingoru
Jun 17, 2026, 03:52 PM UTC

Affected components

Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Deployment orchestration (Create/Edit/Restart/Delete): GCP europe-west4Deployment orchestration (Create/Edit/Restart/Delete): AWS us-east-2Deployment orchestration (Create/Edit/Restart/Delete): AWS us-west-1Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-west-2Deployment orchestration (Create/Edit/Restart/Delete): AWS eu-central-1Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-southafricanorth

Update timeline

  1. identified Jun 17, 2026, 03:52 PM UTC

    We are currently investigating an issue when creating/updating Deployments in several regions. We've identified the issue and working on applying a fix. We will provide an update when one is available or within the hour, whichever comes first.

  2. monitoring Jun 17, 2026, 04:53 PM UTC

    We have identified and deployed a fix for this issue and are continuing to closely monitor the situation.

  3. resolved Jun 17, 2026, 05:35 PM UTC

    This issue has been resolved.