Company Logo

Is there an ESS (Public) outage?

ESS (Public) status: Systems Active

Last checked: 7 minutes ago

Get notified about any outages, downtime or incidents for ESS (Public) and 1800+ other cloud vendors. Monitor 10 companies, for free.

Subscribe for updates

ESS (Public) outages and incidents

Outage and incident data over the last 30 days for ESS (Public).

There have been 7 outages or incidents for ESS (Public) in the last 30 days.

Severity Breakdown:

Tired of searching for status updates?

Join OutLogger to be notified when any of your vendors or the components you use experience an outage. It's completely free and takes less than 2 minutes!

Sign Up Now

Components and Services Monitored for ESS (Public)

Outlogger tracks the status of these components for Xero:

Component Status

Latest ESS (Public) outages and incidents.

View the latest incidents for ESS (Public) and check for official updates:

Updates:

  • Time: March 29, 2024, 3:40 p.m.
    Status: Resolved
    Update: A fix for this issue has been committed and will be included in the upcoming Elasticsearch 8.13.1 release. The Elasticsearch 8.13.1 release is planned to be available mid next week. At that time, we will make Elasticsearch 8.13 available again for Elastic Cloud customers. We are resolving this incident at this time as we have confirmed no Elastic Cloud customers are affected by the Elasticsearch 8.13.0 issue. If you believe you are affected or have any questions related to this incident, please open a support case at https://support.elastic.co.
  • Time: March 29, 2024, 12:32 p.m.
    Status: Monitoring
    Update: A fix for this issue has been implemented and is scheduled to be released with Elasticsearch 8.13.1. The exact release timeline of 8.13.1 is currently being defined. On Elastic Cloud, version 8.13.0 will remain unavailable. As soon as version 8.13.1 is released, this version will become available to all Elastic Cloud customers, offering them a safe upgrade path to Elasticsearch 8.13. We continue to monitor the situation and will provide an update until today 17:30 UTC, or sooner if there is a change in status.
  • Time: March 29, 2024, 5:15 a.m.
    Status: Identified
    Update: The issue has been identified and our teams are working on a fix for Elasticsearch. No Elastic Cloud deployment was affected by this bug and upgrades to version 8.13.0 are prevented. Our next update will be at 17:30 UTC, or sooner if there is a change in status.
  • Time: March 28, 2024, 5:30 p.m.
    Status: Investigating
    Update: We have identified a critical bug in Elasticsearch 8.13.0. The bug causes all clusters running 8.10+ which are using downsampling or have used downsampling since upgrading to 8.10 or later to fail to upgrade to 8.13.0. The nodes on version 8.13.0 will be unable to join the cluster. As an immediate mitigation action we are preventing upgrades on Elastic Cloud to version 8.13.0. Our next update will be in one hour, or sooner if there is a change in status.

Updates:

  • Time: March 26, 2024, 9:47 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 26, 2024, 9:03 p.m.
    Status: Monitoring
    Update: A fix has been implemented and we are monitoring the results.
  • Time: March 26, 2024, 9:03 p.m.
    Status: Identified
    Update: We have deployed a fix for this issue and customers are once again able to sign up / activate subscriptions via the AWS Marketplace.
  • Time: March 26, 2024, 7:59 p.m.
    Status: Identified
    Update: Our team has identified the issue and are currently working on a fix. Our next update will be in 1 hour, or sooner if there is a change in status.
  • Time: March 26, 2024, 6:49 p.m.
    Status: Investigating
    Update: Our team is continuing to investigate this issue. Our next update will be within 1 hour or sooner if the status changes.
  • Time: March 26, 2024, 5:48 p.m.
    Status: Investigating
    Update: We are currently investigating an issue with users being unable to sign up and/or activate subscriptions via the AWS Marketplace. We apologize for the inconvenience and will have another update within the next 60 minutes.

Updates:

  • Time: March 27, 2024, 9:17 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: March 27, 2024, 7:09 a.m.
    Status: Monitoring
    Update: We have deployed a fix for this issue. Creating, viewing, modifying and deleting deployment traffic filters in the Cloud Console (cloud.elastic.co) is working fine again. We continue to monitor the situation.
  • Time: March 27, 2024, 5:29 a.m.
    Status: Identified
    Update: The team has completed verification in our pre-production environments and the fix is being deployed to our production environment. Our next update will be in three hours, or sooner if there is a change in status.
  • Time: March 27, 2024, 2:16 a.m.
    Status: Identified
    Update: Our team is continuing to test their fix in our pre-production environments. Our next update will be in three hours, or sooner if there is a change in status.
  • Time: March 26, 2024, 11:04 p.m.
    Status: Identified
    Update: Verification of the fix continues in our pre-production environments. Our next update will be in three hours, or sooner if there is a change in status.
  • Time: March 26, 2024, 8:57 p.m.
    Status: Identified
    Update: We are continuing to test our fix in our pre-production environments. Our next update will be in two hours, or sooner if there is a change in status.
  • Time: March 26, 2024, 7:54 p.m.
    Status: Identified
    Update: Our team has developed a fix for the issue and we are currently testing in our pre-production environments. Our next update will be in one hour or sooner if there is a change in status.
  • Time: March 26, 2024, 6:30 p.m.
    Status: Identified
    Update: We are continuing to work on a fix for this issue. Our next update will be in one hour or sooner if there is a change in status.
  • Time: March 26, 2024, 5:26 p.m.
    Status: Identified
    Update: Our team has identified the issue and are currently working on a fix. Our next update will be at 18:00 UTC, or sooner if there is a change in status.
  • Time: March 26, 2024, 5 p.m.
    Status: Investigating
    Update: We are aware of an issue with viewing or modifying deployment traffic filters in the Cloud Console, cloud.elastic.co. Our team has confirmed traffic filters are still in place and working for deployments that had these configured. Our team is currently investigating the issue with displaying and modifying these filters in the Cloud Console. Our next update will be in one hour, or sooner if there is a change in status.

Updates:

  • Time: March 19, 2024, 1:17 p.m.
    Status: Resolved
    Update: Azure confirmed on their side that they are no longer experiencing issues. Elastic Cloud Azure Southeast Asia is operating normally. This is incident is resolved.
  • Time: March 19, 2024, 1:07 p.m.
    Status: Monitoring
    Update: All workload has been moved away from the impacted compute. We're not observing any other impact to running deployments, currently. Due to the underlying issues with Azure, we are not able to scale out a subset of our compute types in Zone 1 in the Azure Southeast Asia region. Customers might face issues executing some deployment topology or configuration changes in that availability zone. We are monitoring the situation. Next update within 4 hours.
  • Time: March 19, 2024, 11:56 a.m.
    Status: Identified
    Update: Starting at 09:51 UTC on 19 Mar 2024, a number of virtual machines in Azure Southeast Asia region have been experiencing connection failures and unexpected restarts. Furthermore, starting at 10:48 UTC on 19 Mar 2024 we're unable to scale out virtual machine scale sets in Availability Zone 1 of Azure Southeast Asia. Azure has identified both issues on their end are actively investigating it. We're migrating affected workload to other availability zones in the region or other available compute in the same zone. Next update will be provided in one hour, or as events warrant.
  • Time: March 19, 2024, 11:02 a.m.
    Status: Identified
    Update: Starting at 09:51 UTC on 19 Mar 2024, a number of virtual machines in Azure Southeast Asia region have been experiencing connection failures and unexpected restarts. Azure has identified the issue on their end are actively investigating it. We are assessing impact and attempting to mitigate it. Next update will be provided in one hour, or as events warrant.

Updates:

  • Time: March 16, 2024, 1:08 a.m.
    Status: Resolved
    Update: Azure has confirmed that the connectivity issues in the South Africa North region have been mitigated. They are continuing to add capacity on their end to prevent a recurrence of the issue and will monitor closely over the weekend and into next week to ensure continued stability as that capacity is added. We have not seen any impact on our connectivity for over 18 hours. We are updating this incident status to Resolved but will continue to closely monitor this region.
  • Time: March 15, 2024, 6:17 p.m.
    Status: Monitoring
    Update: We continue to monitor for any remaining connectivity issues in Azure South Africa North. Currently, we are not observing anything abnormal. However, we are waiting for Azure to formally mark the incident as mitigated or resolved on their end before marking it as resolved for our users. At that point, we'll perform a last round of verification checks and resolve the incident.
  • Time: March 15, 2024, 2:28 p.m.
    Status: Monitoring
    Update: We continue to monitor for any remaining connectivity issues in Azure South Africa North. Currently, we are not observing anything abnormal. However, Azure is facing technical difficulties with their capacity activation and need to resolve those before they can safely introduce it into their network. Updated ETA for completion of mitigation is 18:00 UTC on 15 Mar 2024. At that point, we'll perform a last round of verification checks and we will resolve the incident.
  • Time: March 15, 2024, 12:47 p.m.
    Status: Monitoring
    Update: We continue to monitor for any remaining connectivity issues in Azure South Africa North. Azure has determined that multiple fiber cables on the West Coast of Africa — WACS, MainOne, SAT3, ACE — have been impacted which reduced their total capacity supporting Regions in South Africa. In addition to these cable impacts, the on-going cable cuts in the Red Sea — EIG, Seacom, AAE-1 — are also impacting overall capacity on the East Coast of Africa. These incidents together reduced Azure's the total network capacity for most of Africa's regions. Azure teams have taken steps to increase capacity in the region, and are currently redirecting traffic flows to alternative paths. Signs of recovery are reported, with many of Azure Services that were affected by this issue earlier have now returned to normal functionality. Azure's ETA for completion of mitigation is 14:00 UTC on 15 Mar 2024. At that point, we'll perform a last round of verification checks and we will resolve the incident.
  • Time: March 15, 2024, 5:04 a.m.
    Status: Monitoring
    Update: We continue to monitor connectivity issues towards the Azure South Africa North which could also affect deployment changes. Azure is still in the process of remediating the problem. We will post an update as new details emerge from the provider.
  • Time: March 14, 2024, 7 p.m.
    Status: Monitoring
    Update: We continue to monitor connectivity issues towards the Azure South Africa North which could also affect deployment changes. We are in contact with Azure to assess the actual impact. We will post an update as new details emerge from the provider.
  • Time: March 14, 2024, 2:55 p.m.
    Status: Monitoring
    Update: Azure is working on potential mitigations to resolve the connectivity issues. We will keep monitoring the situation and we will post an update within the next 4 hours or sooner if there is an update from Azure
  • Time: March 14, 2024, 11:53 a.m.
    Status: Monitoring
    Update: Azure has confirmed the connectivity impact on South Africa North region. We will be monitoring the situation and we will post an update within the next 2 hours
  • Time: March 14, 2024, 11:33 a.m.
    Status: Investigating
    Update: Our team is investigating a degraded connectivity issue towards the Azure South Africa North which could also affect deployment changes. We are in contact with Azure to assess the actual impact. We will post an update within the next hour

Check the status of similar companies and alternatives to ESS (Public)

Smartsheet
Smartsheet

Systems Active

ESS (Public)
ESS (Public)

Systems Active

Cloudera
Cloudera

Systems Active

New Relic
New Relic

Systems Active

Boomi
Boomi

Systems Active

AppsFlyer
AppsFlyer

Systems Active

Imperva
Imperva

Systems Active

Bazaarvoice
Bazaarvoice

Issues Detected

Optimizely
Optimizely

Systems Active

Electric
Electric

Systems Active

ABBYY
ABBYY

Issues Detected

Housecall Pro
Housecall Pro

Systems Active

Frequently Asked Questions - ESS (Public)

Is there a ESS (Public) outage?
The current status of ESS (Public) is: Systems Active
Where can I find the official status page of ESS (Public)?
The official status page for ESS (Public) is here
How can I get notified if ESS (Public) is down or experiencing an outage?
To get notified of any status changes to ESS (Public), simply sign up to OutLogger's free monitoring service. OutLogger checks the official status of ESS (Public) every few minutes and will notify you of any changes. You can veiw the status of all your cloud vendors in one dashboard. Sign up here
What does ESS (Public) do?
Elasticsearch Platform and AI provide enterprise solutions to help you build, observe, and protect your data. Try it for free to gain powerful insights and outcomes.

Start monitoring now!

Join OutLogger to be notified when any of your vendors or the components you use experience an outage or down time. Join for free - no credit card required.

Get Started for Free