Live  /  Elastic Cloud (Public)  /  Incident

Elastic Cloud (Public): Kibana access restored for UI-assigned Organization Owners on Hosted deployments

Elastic Cloud (Public) · elastic.coMajor incidentResolved2026-09-10 09:51 UTC
Public — what happened

Summary

Elastic Cloud reported a major incident in which some Organization Owners on Hosted deployments, specifically those given that role through the user interface, lost access to Kibana, beginning on 2026-09-10 at 01:30 UTC. The company said it rolled out a fix to production and corrected data on the affected accounts, which brought back Kibana access for those users. Elastic Cloud said it was watching the situation to make sure the problem was fully resolved, with the incident marked resolved at 22:36 the same day.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

Independent path health

The status page is the symptom. SquidGrid measures the paths that reach Elastic Cloud (Public) against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.

🔒 Sign in to see
Customers get the live Provider Assessment Report for Elastic Cloud (Public): its full incident track record, what tends to break, and recent public reports of problems.

Included with any paid plan.

Open the Elastic Cloud (Public) report →

More from Elastic Cloud (Public)

Covered in The Squid’s Ink, Week 38, 2026, our weekly internet health report.

The full archive is on the Elastic Cloud (Public) status & history page.

Related: Elastic Cloud (Public) status & history. SquidGrid is not affiliated with Elastic Cloud (Public).