Elastic

Mar 9, 20:29 UTC
Resolved - This incident has been resolved.

Mar 9, 13:16 UTC
Monitoring - We have seen an improvement regarding this service disruption. The docker registry is available, and project orchestration has been restored. We will continue to monitor the situation, and ensure a full service recovery.

Mar 9, 12:05 UTC
Identified - The issue has been identified, and we are working with our hosting providers to reach a solution.

Users may see an impact with the availability of the elastic docker registry (browsing, and pulling images)
Users may see an impact with the orchestration of their hosted Serverless projects, leading to slower provisioning …

Mar 9, 16:50 UTC
Completed - The scheduled maintenance has been completed.

Mar 9, 16:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.

Mar 6, 20:22 UTC
Scheduled - We will be performing maintenance on the production database for the docker registry web interface during this window. We expect this procedure to take approximately 30 minutes.

During the maintenance window, users who visit the docker registry web interface (https://www.docker.elastic.co) in a browser will see a redirect to the status page for this maintenance. Actual docker operations, such as `docker pull`, will continue to work without interruption.

Mar 9, 15:01 UTC
Update - 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].

Mar 2, 06:23 UTC
Identified - We are aware of connectivity and power issues affecting AWS …

Feb 26, 17:07 UTC
Resolved - This incident is resolved.

Feb 26, 12:24 UTC
Monitoring - We have identified the root cause of those sporadic errors observed and have successfully mitigated the issue. We continue to observe the situation and provide an update within the next 2 hours.

Feb 26, 11:29 UTC
Investigating - We're seeing some errors from fleet-server in Elastic Cloud that are affecting new incoming connections for some projects. We will provide an update within the next 2 hours.

Feb 25, 14:38 UTC
Resolved - 404 errors have been resolved on the elastic.co webpage.

Feb 25, 14:33 UTC
Investigating - We currently investigating an issue causing intermittent 404 errors when visiting the elastic.co webpage. We will provide additional updates as they become available.

Feb 18, 19:12 UTC
Resolved - This issue is now resolved.

Feb 18, 17:56 UTC
Investigating - We are currently aware of and investigating an issue causing failure to provision new capacity in Elastic Cloud Hosted Azure regions. We will provide additional updates as they become available.

Feb 13, 00:46 UTC
Resolved - We have identified and fixed an issue on the billing usage pages that resulted in the pages showing incorrect billing totals. There should be no more customer impact.

Feb 12, 18:21 UTC
Identified - We've identified an issue on the billing usage pages where some hosted deployments might be showing incorrect usage. We're working on a fix and will update again in 6 hours.

Feb 10, 22:51 UTC
Resolved - This issue has been resolved, and BYOK deployment creation has been confirmed as fully functional.

Feb 10, 19:49 UTC
Identified - We have identified a misconfiguration in our Azure set up and working on pushing out the fix. Will update soon once it has been released.

Feb 10, 18:35 UTC
Investigating - We are investigating a degradation in BYOK deployment creation in Azure regions. We will update again in one hour.

Feb 10, 10:22 UTC
Resolved - We have completed our work to restore access to`openai-gpt-oss-120b` model in EIS.

Feb 9, 19:35 UTC
Update - We've identified the issue and have merged a fix. We are in the process of rolling this out but are blocked by a GitHub degradation. Will update as soon as we have some progress on the deploy.

Feb 9, 16:53 UTC
Investigating - We've noticed a degradation in the `openai-gpt-oss-120b` model in EIS, we're investigating the root cause and we'll update again in 2 hours