Service
Apr 10, 19:54 UTC Resolved - We have successfully deployed a fix for the PrivateLink hostname issue to the User Console. Customers who experienced incorrect PrivateLink URLs or connectivity issues with their deployments should now see correct hostnames. We apologize for the inconvenience. Apr 10, 12:18 UTC Update - We are still working on moving the fix to production as we experienced some testing issues. Apr 9, 22:44 UTC Update - We have merged a fix and are working on deploying it to product...
Apr 10, 11:51 UTC Resolved - We have confirmed no further impact from this incident, and are now marking it as resolved. Apr 9, 19:50 UTC Update - We have rolled out the fix and there should be no more customer impact Apr 9, 16:41 UTC Update - We have identified the issue and are working on a fix. We will update again in 3 hours or earlier. Apr 9, 16:21 UTC Update - We have identified that only PrivateLink customers are impacted and no other Hosted Cloud Deployments should see any issues. Apr...
Apr 6, 20:43 UTC Resolved - Issue has been fixed and there should be no more customer impact Apr 6, 19:16 UTC Identified - We have identified the problem and are working on a solution. We should have an update within the next 2-3 hours. Apr 6, 17:58 UTC Investigating - We are investigating an issue in our Synthetics service on us-east-4. Some customer monitor jobs may not run on their expected schedule. We will provide an update in an hour or earlier.
Mar 30, 19:57 UTC Resolved - Endpoints are operating normally Mar 30, 18:46 UTC Investigating - We're seeing elevated 5xx error rates for the Claude Sonnet 4.5 model in EIS. The following default inference endpoints are affected: - .anthropic-claude-4.5-sonnet-chat_completion - .anthropic-claude-4.5-sonnet-completion - .gp-llm-v2-chat_completion - .gp-llm-v2-completion We're investigating and will update again in 2 hours or if there's a change in status.
Mar 27, 07:23 UTC Resolved - AutoOps is back to full functionality in the AWS us-east-1 region and the incident has been resolved. Mar 27, 07:13 UTC Update - We have mitigated the issue, and AutoOps is back to full functionality in the AWS us-east-1 region. We will continue monitoring the signals from the region to ensure AutoOps remains fully functional, and will share another update once the issue is fully resolved. Mar 27, 05:37 UTC Monitoring - We have identified the issue and applied mitiga...
Mar 26, 17:42 UTC Resolved - This issue is resolved. Customers are now able to create new Serverless projects in the GCP europe-west3 region Mar 26, 13:06 UTC Update - The engineering team is validating the fix to restore project creation in the GCP europe-west3 region. We will post another update in 2 hours or sooner if needed Mar 26, 10:51 UTC Identified - We are aware of problems creating new Serverless projects in the GCP europe-west3 region. The engineering team has identified the problem a...
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 elas...
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.dock...
Apr 2, 00:00 UTC Update - 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 ou...
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 ...
Feb 6, 04:22 UTC Resolved - The issues affecting Elastic Cloud Serverless project creation in the AWS us-east-1 region have been resolved. Our engineering team identified a DNS configuration error as the root cause; once the records were corrected and propagated, service functionality returned to normal. All systems are now operating as expected, and customers should no longer experience delays or errors when creating new projects. We appreciate your patience while we worked to clear this up. F...
Feb 3, 10:42 UTC Resolved - The incidents affecting us have been resolved on Azure's side. All Elastic services are fully operational and no further impact was observed during the past 4 hours. Hence, we mark this incident as resolved. Feb 3, 07:37 UTC Update - We are closely monitoring the situation as we await Microsoft Azure's final resolution regarding their ongoing incidents. Currently, we are not aware of any additional impact on Elastic customers or services. However, we will maintain a...
Jan 23, 07:31 UTC Resolved - We have completed our work to restore service to Elastic Cloud email and MFA services. The upstream third-party incident that was affecting account verification and MFA emails has been resolved, and all systems are now operating normally. We have confirmed that email delivery has returned to expected levels. Jan 23, 03:55 UTC Update - We are continuing to monitor the status of the upstream provider's incident. We will continue to post periodic updates or as new infor...
Jan 23, 03:51 UTC Resolved - The incident has been resolved. Jan 23, 00:56 UTC Monitoring - We've determined that AutoOps functionality has fully recovered for Elastic Cloud Hosted clusters in GCP US Central. Jan 23, 00:37 UTC Investigating - Customers may observe some data delay in AutoOps functionality for Elastic Cloud Hosted clusters in GCP US Central. We're actively investigating this.
Dec 25, 03:17 UTC Resolved - The system is operational. Dec 25, 02:19 UTC Monitoring - AutoOps functionality has been restored in the GCP us-central-1 region. We are continuing to monitor the system for signs of service degradation. Dec 25, 00:35 UTC Update - AutoOps functionality is gradually being restored in the GCP us-central-1 region. We expect the full recovery to resume within a few hours and will keep updating until full recovery is achieved. Customer deployments in the region may still ...