Elastic Cloud incident

Internal Monitoring Data Delay

Minor Resolved View vendor source →

Elastic Cloud experienced a minor incident on July 1, 2026 affecting Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2 and Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2 and 1 more component, lasting 4h 43m. The incident has been resolved; the full update timeline is below.

Started
Jul 01, 2026, 03:39 PM UTC
Resolved
Jul 01, 2026, 08:23 PM UTC
Duration
4h 43m
Detected by Pingoru
Jul 01, 2026, 03:39 PM UTC

Affected components

Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus

Update timeline

  1. investigating Jul 01, 2026, 03:39 PM UTC

    We're experiencing a monitoring data delay affecting a limited number of Azure regions. Elastic Cloud's internal metrics for these regions are being ingested more slowly than usual. What you may notice: Deployment metrics and instance utilization data may not appear in the Elastic Cloud UI for Hosted Deployments and Serverless Projects in affected regions. What's not affected: Your deployments and projects are running normally. Data ingestion and all functionality remain unimpacted besides lacking some monitoring data on the Elastic Cloud UI. We're actively investigating the root cause and will provide an update within the next 2 hours.

  2. identified Jul 01, 2026, 04:50 PM UTC

    We have identified the issue and implemented a fix. We are seeing signs of system recovery and are continuing to monitor the situation closely.

  3. monitoring Jul 01, 2026, 07:50 PM UTC

    The system has recovered and we are continuing to monitor the situation.

  4. resolved Jul 01, 2026, 08:23 PM UTC

    This issue has been resolved.