Changes / Elastic Cloud / Issue with Kibana authentication flow
Elastic Cloud: Major incident: Issue with Kibana authentication flow
Summary
A major Kibana authentication outage affected Deployments and Projects: the "Log in with Elastic Cloud" button failed. It started at 2026-06-16 10:57 UTC and was resolved at 2026-06-16 11:36 UTC, lasting 38 min. Customers could use the Kibana link inside the Elastic Cloud console as a workaround; Elastic reported identifying the root cause and mitigating the issue.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Issue with Kibana authentication flow
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-06-16 10:57 UTC
Before: not present
After: 2026-06-16 11:36 UTC
Before: not present
After: Global services - Cloud console
Before: not present
After: We have detected an issue with the Kibana authentication flow for both Deployments and Projects. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure.
A workaround is to access Kibana using the link inside the Elastic Cloud console. We are currently working on a resolution.
Our team is currently identifying the root cause to resolve the issue.
We will share another update in the next hour.
Before: not present
After: We are continuing to investigate this issue.
Before: not present
After: We have identified the root cause and mitigated the issue. Users should now be able to log in to Kibana via the "Log in with Elastic Cloud" button.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Issue with Kibana authentication flow (this change) A major Kibana authentication outage affected Deployments and Projects: the "Log in with Elastic Cloud" button failed. It started at 2026-06-16 10:57 UTC and was resolved at 2026-06-16 11:36 UTC, lasting 38 min. Customers could use the Kibana link inside the Elastic Cloud console as a workaround; Elastic reported identifying the root cause and mitigating the issue. | Major incident |
All Elastic Cloud changes → · Elastic Cloud profile · Markdown · JSON