Elasticsearch reported this minor-impact incident on its official status page on Jul 1, 2026, 15:39 UTC. It was resolved after 4h 44m.
Right now Elasticsearch is operational. Live Elasticsearch status →
This issue has been resolved.
The system has recovered and we are continuing to monitor the situation.
We have identified the issue and implemented a fix. We are seeing signs of system recovery and are continuing to monitor the situation closely.
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.
Our 5-minute checks didn't record a change in Elasticsearch's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.
Overlapping incidents aren't necessarily related.
Elasticsearch reported 23 incidents in the last 90 days, 20 of them major or critical. A typical incident lasted 3h 35m. See Elasticsearch's uptime and incident history