Skip to main content
Elastic Cloud

Internal Monitoring Data Delay

Degraded Lasted 4h 44m · started · Elastic Cloud's page

Level
confirmed
Worst impact
Degraded
Components
Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus
Down Index
21of 100

What to do

  • Check whether you use Elastic Cloud Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 4h 44m it lasted.

    Anything that failed between 2026-07-01 15:39 UTC and 2026-07-01 20:23 UTC may need a replay.
  • Subscribe to Elastic Cloud's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=elastic-cloud works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Elastic Cloud 4

  1. investigating

    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.

    provider

  2. identified

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

    provider

  3. monitoring

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

    provider

  4. resolved

    This issue has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-24af77caa7

Is Elastic Cloud still down?

No, this incident was resolved 2026-07-01 20:23 UTC. For Elastic Cloud's live state, see https://down.guide/elastic-cloud.

How long did it last?

4h 44m, from 2026-07-01 15:39 UTC to 2026-07-01 20:23 UTC, by the times Elastic Cloud posted.

What was affected?

Elastic Cloud named Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus2, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-westus2, Deployment orchestration (Create/Edit/Restart/Delete): Azure azure-eastus.

What caused it?

Elastic Cloud hasn't published a root cause. If it does, it shows here.

Where does this come from?

Elastic Cloud's official status page, https://status.elastic.co, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.