Elasticsearch reported this major-impact incident on its official status page on Sep 10, 2026, 01:30 UTC. It was resolved after 21h.
Right now Elasticsearch is operational. Live Elasticsearch status →
This incident has been resolved.
Update: The fix has been deployed to production and we have applied a data correction to affected accounts, restoring Kibana access for impacted users. We are monitoring to confirm full resolution.
Update: This incident is still ongoing and we are continuing to investigate.
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.
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