Company Logo

Is there an ESS (Public) outage?

ESS (Public) status: Systems Active

Last checked: 12 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 6 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: Nov. 20, 2024, 3:24 p.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Nov. 20, 2024, 12:13 p.m.
    Status: Monitoring
    Update: A fix has been implemented by AWS and we're monitoring the situation to confirm that scaling High Storage deployments is working as expected.
  • Time: Nov. 20, 2024, 8:53 a.m.
    Status: Investigating
    Update: We are investigating an issue with creating or scaling up High Storage deployments across us-west-1 AWS region. We're following up with AWS on the details. Next update will be in one hour, or sooner if appropriate.

Updates:

  • Time: Nov. 13, 2024, 6:56 a.m.
    Status: Resolved
    Update: This incident has been resolved.
  • Time: Nov. 13, 2024, 6:51 a.m.
    Status: Monitoring
    Update: The 8.16.0 packages are now available in https://artifacts.elastic.co/packages/8.x
  • Time: Nov. 12, 2024, 10:25 p.m.
    Status: Identified
    Update: 8.16.0 is still unavailable in https://artifacts.elastic.co/packages/8.x. As a workaround, it can be downloaded from https://www.elastic.co/downloads/. We will provide an update once it is available on https://artifacts.elastic.co/packages/8.x
  • Time: Nov. 12, 2024, 9:36 p.m.
    Status: Identified
    Update: We've fixed a corrupted manifest. Elastic Cloud is no longer impacted and fully functional. Adding https://artifacts.elastic.co/packages/8.x and pulling 8.15.4 packages is also working. Pulling 8.16.0 packages are still impacted and being worked on. An update will be provided in 1 hour, or less if the situation changes.
  • Time: Nov. 12, 2024, 8:11 p.m.
    Status: Investigating
    Update: We've identified that 8.15.4 packages are also impacted. If you have already added https://artifacts.elastic.co/packages/8.x/apt you can still pull packages other than 8.16.0 or 8.15.4, however attempts to add this as a new repository will fail. We're continuing to work on a resolution. An update will be provided in 1 hour, or less if the situation changes.
  • Time: Nov. 12, 2024, 7:23 p.m.
    Status: Investigating
    Update: We are investigating errors when pulling 8.16.0 apt packages from artifacts.elastic.co. This also impacts Elastic Cloud customers.

Updates:

  • Time: Nov. 15, 2024, 4:51 a.m.
    Status: Resolved
    Update: All related capacity issues were resolved earlier today and monitoring found no new issues.
  • Time: Nov. 13, 2024, 12:59 p.m.
    Status: Identified
    Update: We are still working with AWS to resolve capacity constraints in a handful of regions. Next update in 4 hours, or sooner if appropriate
  • Time: Nov. 12, 2024, 7:26 p.m.
    Status: Identified
    Update: We are continuing to work with AWS to mitigate the provisioning failures across all impacted regions. Next update will be in one hour, or sooner if appropriate
  • Time: Nov. 12, 2024, 5:38 p.m.
    Status: Identified
    Update: We are continuing to work with AWS to mitigate the provisioning failures. Next update will be in one hour, or sooner if appropriate
  • Time: Nov. 12, 2024, 3:59 p.m.
    Status: Identified
    Update: We have identified the root cause for the failed scale up and creation deployment operations that we were seeing and we are working with AWS to mitigate this. Next update will be in one hour, or sooner if appropriate
  • Time: Nov. 12, 2024, 12:09 p.m.
    Status: Investigating
    Update: We are still investigating issues with creating or scaling up High Storage deployments or those with Warm or Cold data tier across multiple AWS regions. We're following up with AWS on the details. Next update will be in one hour, or sooner if appropriate
  • Time: Nov. 12, 2024, 11:04 a.m.
    Status: Investigating
    Update: We are investigating an issue with creating or scaling up High Storage deployments across multiple AWS regions. We're following up with AWS on the details. Next update will be in one hour, or sooner if appropriate

Updates:

  • Time: Oct. 31, 2024, 11:46 p.m.
    Status: Resolved
    Update: We have implemented restrictions in Elastic Cloud blocking the problematic upgrade paths. The small number of impacted customers have been notified via an email containing information on the mitigation steps to follow. These steps are also documented in: https://www.elastic.co/guide/en/observability/8.15/apm-known-issues.html#_upgrading_to_v8_15_x_may_cause_ingestion_to_fail https://www.elastic.co/guide/en/observability/8.15/apm-known-issues.html#_upgrading_to_v8_15_0_may_cause_apm_indices_to_lose_their_lifecycle_policy
  • Time: Oct. 31, 2024, 3:32 p.m.
    Status: Identified
    Update: There is a known issue where upgrading to v8.15.0 may cause APM indices to lose their lifecycle policy. It is suggested to upgrade to at least v8.15.1. Please see this article for more detail and support on how to navigate your upgrades: https://www.elastic.co/guide/en/observability/8.15/apm-known-issues.html#_upgrading_to_v8_15_0_may_cause_apm_indices_to_lose_their_lifecycle_policy There is a known issue where upgrading from v8.12.2 or below directly to any 8.15 version causes APM data ingestion to be rejected. It is suggested to first upgrade to v8.14.3 and from there upgrade to version 8.15.1 or higher. Please see this article for more detail and support on how to navigate your upgrades: https://www.elastic.co/guide/en/observability/8.15/apm-known-issues.html#_upgrading_to_v8_15_x_may_cause_ingestion_to_fail
  • Time: Oct. 31, 2024, 2:04 p.m.
    Status: Identified
    Update: There is a known issue where upgrading to v8.15.0 may cause APM indices to lose their lifecycle policy. It is suggested to upgrade to at least v8.15.1. Please see this article for more detail and support on how to navigate your upgrades: https://www.elastic.co/guide/en/observability/8.15/apm-known-issues.html#_upgrading_to_v8_15_0_may_cause_apm_indices_to_lose_their_lifecycle_policy There is a known issue where upgrading from v8.12.2 or below directly to any 8.15 version causes APM data ingestion to be rejected. It is suggested to first upgrade to v8.14.3 and from there upgrade to version 8.15.1 or higher.

Updates:

  • Time: Oct. 29, 2024, 6:39 p.m.
    Status: Resolved
    Update: This incident has been resolved. All impacted repositories have been made public, and their forks have been restored.
  • Time: Oct. 29, 2024, 5:59 p.m.
    Status: Identified
    Update: As previously communicated, all repositories except for Kibana have been changed back to public, and their forks have been restored. We are awaiting further input from GitHub Support for the Kibana repository but expect it may take several hours (or more) to be changed back to public. We will post updates here as we have them.
  • Time: Oct. 29, 2024, 5:07 p.m.
    Status: Identified
    Update: All repositories except for Kibana have been changed back to public and their forks have been restored. We are awaiting further input from GitHub Support for the Kibana repository.
  • Time: Oct. 29, 2024, 4:06 p.m.
    Status: Identified
    Update: All repositories except for Kibana have been changed back to public. GitHub is in the process of restoring forks for those repositories. We are awaiting further input from GitHub Support for the Kibana repository.
  • Time: Oct. 29, 2024, 3:09 p.m.
    Status: Identified
    Update: Our teams are executing on the restoration path for returning our impacted git repositories to a public state and are moving closer to remediation. This was caused as part of an internal change task where some of our public git repositories hosted under Elastic's GitHub organisation were marked as private. As a result, when attempting to access these repositories an error may be seen.
  • Time: Oct. 29, 2024, 1:52 p.m.
    Status: Identified
    Update: As part of an internal change task, some of our public git repositories hosted under Elastic's GitHub organisation were marked as private. As a result, when attempting to access these repositories an error may be seen. Our teams are working on the restoration path for returning our impacted git repositories to a public state.
  • Time: Oct. 29, 2024, 12:51 p.m.
    Status: Identified
    Update: As part of an internal change task, some of our public git repositories hosted under Elastic's GitHub organisation were marked as private. As a result, when attempting to access these repositories an error may be seen. Our teams are working to restore these with urgency.
  • Time: Oct. 29, 2024, 12:28 p.m.
    Status: Identified
    Update: We are aware that some of our public repositories are temporarily unavailable and are working towards resolving this.

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

Systems Active

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