Companies / Elastic Cloud / incidents

Elastic Cloud: Internal Monitoring Data Delay

Affected components: Azure Virginia (azure-eastus2) - Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2Azure Washington (azure-westus2) - Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2Azure Virginia (azure-eastus) - Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastusDeployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus

Timeline of updates

1. investigating2026-07-01 15:39 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. identified2026-07-01 16:50 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. monitoring2026-07-01 19:50 UTC

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

4. resolved2026-07-01 20:23 UTC

   This issue has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Elastic Cloud profile · Recent Elastic Cloud incidents · Markdown · JSON