Elastic

Monitoring

Website

Resolving…

Description

Elastic is the company behind Elasticsearch, Kibana, and the Elastic Stack. Elastic Observability provides APM, log analytics, metrics, and uptime monitoring with OpenTelemetry support. It helps teams search, analyze, and visualize data in real time across applications and infrastructure.

Status Page

https://status.elastic.co/

Active Incidents

Last refresh: 2026-09-14 17:08 UTC (14m ago)

Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output

Identified

We have patched Fleet Server versions 9.5.3 and 9.4.6 with corrected releases deployed as of September 10, 2026 at 21:20 UTC. - Upgrading to the current 9.4.6 or 9.5.3 releases will not be affected by this bug as the updated release contains the fix. - If you upgraded to 9.4.6 or 9.5.3 before 21:20 UTC on 10 September 2026, perform the following mitigation: 1. Force restart the Integration Serv...

Incident

Location: —

Started: 2026-09-09 20:44 UTC (4d ago)

Updated: 2026-09-11 16:00 UTC (3d ago)

Resolved: N/A

2026-09-09 20:44 UTC (4d ago) : 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 ...

Replication bug causing slow recoveries

Monitoring

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.

Incident

Location: —

Started: 2026-09-01 08:16 UTC (13d ago)

Updated: 2026-09-03 15:47 UTC (11d ago)

Resolved: N/A

2026-09-03 12:13 UTC (11d ago) : 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.

2026-09-01 15:46 UTC (13d ago) : The fix has been identified and backported to the Elasticsearch 9.5 patch branch. The teams are performing the needed validations before scheduling and rolling out the 9.5.3 release.

2026-09-01 11:07 UTC (13d ago) : We have identified the root cause and the team is working on a fix scheduled to be released in Elasticsearch version 9.5.3 What you can do: - If you have not yet upgraded to 9.5.*, you are not affected as upgrades to 9.5 have been disabled until 9.5.3 is released - If you are already running 9.5 and experience the symptoms of this issue, please contact Elastic Support. More information can be f...

Connectivity disruption for AWS Bahrain (me-south-1)

Identified

Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or e...

Incident

Location: Bahrain (BH)

Started: 2026-03-02 06:23 UTC (Mar 02, 2026)

Updated: 2026-08-10 16:46 UTC (Aug 10, 2026)

Resolved: N/A

2026-06-29 17:14 UTC (Jun 29, 2026) : Update — This incident is still ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.el...

2026-06-15 19:27 UTC (Jun 15, 2026) : Update — This incident is still ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.el...