Last checked
Elastic Cloud status
Hosted Elasticsearch and search solutions for easy deployment and scaling.
Experiencing an issue?
Elastic Cloud est-il en panne?
Major outage
The official status page for Elastic Cloud reports an outage. An unresolved official incident is listed: “Organisation Owner role access to Elastic Cloud Hosted Kibana”. Components reported as affected: Elastic Cloud Hosted, GCP Mumbai (asia-south1). 0 reports were recorded for Elastic Cloud in the last 24 hours. Last official check: .
Having issues with Elastic Cloud?
Share your experience to help others stay informed.
Elastic Cloud service health graph
Service status and report activity over the last 24 hours, in 15-minute intervals. Early warnings and official incidents are shown separately.
Elastic Cloud activity
Loading reports… · Last 24 hours
Download
- No problems detected
- Possible problems
- Problems detected
- Early warning
- Official incident
Small green bars: normal status (illustrative). Taller bars: report activity. Tap a bar to keep its details open. With the chart focused, use Left and Right to move between intervals, Home or End to jump, and Escape to close. Full data is available in the table below.
| Start | End | Reports | Status |
|---|
Latest activity
Last 24 hoursOfficial status checked
Elastic Cloud is experiencing an outage
Official provider statusOfficial incident active
Organisation Owner role access to Elastic Cloud Hosted Kibana — We have identified and are in the process of fixing+mitigating a bug in our permissions management UI that is prevents users with the Organisation Owner role and Cloud Console, Elasticsearch, and Kibana access from accessing Kibana in Hosted Deployments.
Official provider statusOfficial incident active
Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output — We've identified a bug in Fleet Server 9.5.3 (also present in 9.4.6) that can cause Elastic Agents to crash-loop and go offline when Fleet pushes a configuration update, including enrollment, a policy change, or a routine revision bump. This only affects policies that use Fleet's remote Elasticsearch output feature. Recommendation: If you use Fleet's remote Elasticsearch output, do not upgrade to 9.5.3 or 9.4.6 until a fixed version is available. If you're already on an affected version and experiencing agent check-in failures, contact Support for remediation steps. A fix has been merged and will ship in the next 9.5.x and 9.4.x releases. Known Issue documentation: fleet-server#7791, elastic-agent#16542.
Official provider statusOfficial incident active
Replication bug causing slow recoveries — Elasticsearch 9.5.3 has been released and all customers currently running 9.5.0, 9.5.1 or 9.5.2 are advised to update to this new version as soon as possible. Impacted customers are advised to follow the workaround steps from https://github.com/elastic/elasticsearch/issues/158212 after the upgrade.
Official provider status
