Is Elastic Cloud down?

Last checked 1m ago
Current status
Elastic Cloud is down

2 active incidents: Replication bug causing slow recoveries, Connectivity disruption for AWS Bahrain (me-south-1)

Get alerts when Elastic Cloud breaks → View Elastic Cloud outage history →

Free · no credit card

Official status page: https://status.elastic.co · Polled every 5 minutes · 542 components tracked

Elastic Cloud is reporting a major outage right now (last checked 1m ago). 2 active incidents on the official status page.

Real-time Elastic Cloud status, recent outages, and incident history — pulled directly from Elastic Cloud's official status page at https://status.elastic.co every 5 minutes. Pingoru tracks 542 Elastic Cloud services and has captured 29 incidents in the last 90 days (99.85% uptime). Get email, Slack, Discord, or webhook alerts the moment Elastic Cloud reports a new incident — free for 5 monitors, no credit card.

Users who monitor Elastic Cloud also follow these Analytics services: New Relic Grafana Fivetran Segment Amplitude Mixpanel Hudl Qualtrics Hotjar Branch View all 6,000+ providers
Elastic Cloud uptime 99.85% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Active incidents 2

  1. Replication bug causing slow recoveries
    Ongoing ● 16d 13h
    Started Sep 01, 2026, 08:16 AM UTC
    Elastic Cloud Hosted
    Timeline · 5 updates
    • investigating · Sep 01, 2026, 08:16 AM UTC

      We are aware of a bug affecting customers on Elasticsearch versions 9.5.0, 9.5.1 and 9.5.2 where bulk index operations processed on the primary shard can result in divergence on the replicas resulting in high disk usage and long-running recoveries. The team is working on a fix. More information can be found on https://www.elastic.co/docs/release-notes/elasticsearch/known-issues#elasticsearch-9.5.2-known-issues The next update will be in the next 2 hours or sooner if needed.

    • identified · Sep 01, 2026, 11:07 AM UTC

      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 found on https://www.elastic.co/docs/release-notes/elasticsearch/known-issues#elasticsearch-9.5.2-known-issues

    • identified · Sep 01, 2026, 03:46 PM UTC

      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.

    • monitoring · Sep 03, 2026, 12:13 PM UTC

      Elasticsearch 9.5.3 has been released and all Elastic Cloud and On-Premises 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.

    • monitoring · Sep 03, 2026, 03:47 PM UTC

      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.

    Latest: 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 ar…

  2. Connectivity disruption for AWS Bahrain (me-south-1)
    Ongoing ● 199d 14h
    Started Mar 02, 2026, 06:23 AM UTC
    AWS EC2 Health: me-south-1Snapshot Storage Infrastructure (S3): me-south-1Deployment orchestration (Create/Edit/Restart/Delete): AWS me-south-1APM connectivity: AWS me-south-1AWS Infrastructure health: me-south-1Elasticsearch connectivity: AWS me-south-1Kibana connectivity: AWS me-south-1
    Timeline · 14 updates
    • identified · Mar 02, 2026, 06:23 AM UTC

      We are aware of connectivity and power issues affecting AWS Bahrain (me-south-1) due to localized power issues. We are awaiting further updates from AWS and will update here once we have more information.

    • identified · Mar 09, 2026, 03:01 PM UTC

      This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].

    • identified · Mar 16, 2026, 07:46 PM UTC

      This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].

    • identified · Mar 23, 2026, 04:20 PM UTC

      There are no new updates. This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].

    • identified · Mar 24, 2026, 09:29 AM UTC

      We have identified a further potential disruption to our services hosted in the AWS Bahrain (me-south-1) region. We are working to determine the scope of this impact, and have engaged with AWS as the providers in this investigation. Further updates will be posted within the hour, or when we have further information.

    • identified · Mar 24, 2026, 11:09 AM UTC

      This incident remains ongoing. We continue to monitor the situation in AWS Bahrain (me-south-1) and are actively supporting all impacted customers through our support channels. As this incident has no ETA for mitigation, our status updates for this incident will be on a weekly basis, or sooner if there is a significant change in status. For any further assistance, please feel free to reach out to Elastic support by either opening a case in our Support portal (https://support.elastic.co) or by emailing [email protected].

    • identified · Apr 02, 2026, 12:00 AM UTC

      As this incident remains ongoing with no recovery timeline provided by AWS, we have removed AWS Bahrain (me-south-1) from the available region selection on cloud.elastic.co. The region is currently unavailable for the creation of new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS connectivity disruption. Customers in this region should continue to work through Elastic support channels. For assistance, please open a case in our Support portal (https://support.elastic.co) or email [email protected].

    • identified · Apr 20, 2026, 05:46 PM UTC

      Update — This incident remains ongoing. AWS Bahrain (me-south-1) has been removed from the available region selection on cloud.elastic.co and is unavailable for new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS infrastructure disruption. AWS has not provided a recovery timeline for the region. Customers should continue to assume the region is unavailable for the foreseeable future. We continue to support impacted customers individually through our support channels. If you have not yet done so, please open a case so we can assist with your recovery options. For assistance, please open a case in our Support portal (https://support.elastic.co) or email mailto:[email protected]. Apr 20, 2026 — 00:00 UTC

    • identified · May 18, 2026, 04:33 PM UTC

      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 email [email protected].

    • identified · Jun 01, 2026, 05:13 PM UTC

      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 email [email protected].

    • identified · Jun 15, 2026, 07:27 PM UTC

      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.elastic.co) or email mailto:[email protected].

    • identified · Jun 29, 2026, 05:14 PM UTC

      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.elastic.co) or email mailto:mailto:[email protected].

    • identified · Jul 13, 2026, 04:42 PM UTC

      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 email [email protected].

    • identified · Aug 10, 2026, 04:46 PM UTC

      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 email [email protected].

    Latest: 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 infr…

Recent outages & incidents

Past 90 days
  1. AutoOps node metrics temporarily unavailable in some regions
    Resolved 41m
    Started Sep 17, 2026, 03:50 PM UTC · Resolved Sep 17, 2026, 04:31 PM UTC
    Timeline · 3 updates
    • investigating · Sep 17, 2026, 03:50 PM UTC

      We are investigating reports of missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions. This may appear as a "No data" message on the Nodes view. Cluster health, shard, and deployment data are unaffected, and no data loss has occurred. We will provide an update within the next 2 hours or earlier.

    • identified · Sep 17, 2026, 04:13 PM UTC

      We've identified the cause of the missing node-level metrics (CPU, memory, disk, thread pools) in affected regions. Cluster health, shard, and deployment data were never affected, and no data loss has occurred. A fix has been validated in one region and is now being rolled out to the remaining affected regions. We'll provide a further update once the rollout is complete.

    • resolved · Sep 17, 2026, 04:31 PM UTC

      The issue causing missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions has been fully resolved. Cluster health, shard, and deployment data were unaffected throughout, and no data was lost.

    Latest: The issue causing missing node-level metrics (CPU, memory, disk, thread pools) for recent time ranges in a subset of AutoOps regions has been fully resolved. Cluster health, shard,…

  2. Elastic Support Portal unavailable
    Resolved 2h 21m
    Started Sep 16, 2026, 01:17 PM UTC · Resolved Sep 16, 2026, 03:38 PM UTC
    Timeline · 3 updates
    • investigating · Sep 16, 2026, 01:17 PM UTC

      We are currently aware that some customers may be unable to access the Elastic Support Portal at this time. We are working with our provider to investigate. If you need to contact support in the meantime, please contact [email protected].

    • monitoring · Sep 16, 2026, 02:49 PM UTC

      We are seeing signs of recovery on the Elastic Support Portal, and customers should now be able to access as normal. We will continue monitoring for 30 minutes before marking this incident as resolved.

    • resolved · Sep 16, 2026, 03:38 PM UTC

      The Elastic Support Portal remains available and steady - at this time, we are considering this incident resolved.

    Latest: The Elastic Support Portal remains available and steady - at this time, we are considering this incident resolved.

  3. Delayed Metrics in Cloud Console - GCP us-east4
    Resolved 8h 24m
    Started Sep 12, 2026, 11:21 PM UTC · Resolved Sep 13, 2026, 07:45 AM UTC
    Timeline · 4 updates
    • investigating · Sep 12, 2026, 11:21 PM UTC

      We are investigating metrics delays in the console.

    • identified · Sep 13, 2026, 12:18 AM UTC

      We've identified and fixed the cause of the metrics delay. The queue is being processed and delayed metrics will be viewable when complete.

    • monitoring · Sep 13, 2026, 02:55 AM UTC

      Metrics queues are being processed and delayed data is starting to show again. We'll monitor to be sure everything catches up as expected.

    • resolved · Sep 13, 2026, 07:45 AM UTC

      The metrics ingestion delay in GCP us-east4 has been fully resolved. All queued data has been processed and metrics are now showing in the console in real time.

    Latest: The metrics ingestion delay in GCP us-east4 has been fully resolved. All queued data has been processed and metrics are now showing in the console in real time.

  4. Kibana access restored for UI-assigned Organization Owners on Hosted deployments
    Resolved 21h
    Started Sep 10, 2026, 01:30 AM UTC · Resolved Sep 10, 2026, 10:31 PM UTC
    Timeline · 4 updates
    • identified · Sep 10, 2026, 01:30 AM UTC

      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.

    • identified · Sep 10, 2026, 06:03 AM UTC

      Update: This incident is still ongoing and we are continuing to investigate.

    • monitoring · Sep 10, 2026, 09:51 AM UTC

      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.

    • resolved · Sep 10, 2026, 10:31 PM UTC

      This incident has been resolved.

    Latest: This incident has been resolved.

  5. Elastic Agent enrollment/check-in failures on 9.5.3 (and 9.4.6) with Fleet remote Elasticsearch output
    Resolved 7d 13h
    Started Sep 09, 2026, 08:44 PM UTC · Resolved Sep 17, 2026, 10:30 AM UTC
    Timeline · 4 updates
    • identified · Sep 09, 2026, 08:44 PM UTC

      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.

    • identified · Sep 11, 2026, 02:25 PM UTC

      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 Server component of you affected deployment 2. Run cleanup procedures on affected Elastic Agents (see https://support.elastic.co/knowledge/bee1c75c) — required if agents failed to check in or remained offline after the Integration Server restart

    • identified · Sep 11, 2026, 04:00 PM UTC

      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 Server component of you affected deployment 2. Run cleanup procedures on affected Elastic Agents (see https://support.elastic.co/knowledge/bee1c75c) — required if agents failed to check in or remained offline after the Integration Server restart IMPORTANT: The patched Fleet Server is not available outside Elastic Cloud Enterprise (ECE) Stack Packs and Elastic Cloud Hosted (ECH).

    • resolved · Sep 17, 2026, 10:30 AM UTC

      We have confirmed that Elastic Agents are no longer experiencing enrollment failures related to this issue. Corrected Fleet Server releases (9.5.4 / 9.4.6) have been available on Elastic Cloud Hosted and Elastic Cloud Enterprise stack packs since September 10, 2026, and all known affected deployments have confirmed recovery. If you upgraded to an affected release before that time and have not yet applied the mitigation, guidance is available here: https://support.elastic.co/knowledge/bee1c75c.

    Latest: We have confirmed that Elastic Agents are no longer experiencing enrollment failures related to this issue. Corrected Fleet Server releases (9.5.4 / 9.4.6) have been available on E…

See the full Elastic Cloud outage history

22 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Elastic Cloud outage history →

Or sign up free to get alerts when Elastic Cloud breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 26 incidents View full outage history →