Elastic Cloud Outage History

Started Apr 09, 2026, 08:46 PM UTC· resolved Apr 10, 2026, 07:54 PM UTC

1. identified Apr 09, 2026, 08:46 PM UTC

   A recent change to our Privatelink implementation resulted in the URLs reported by the deployment API being incorrect in some cases, causing connectivity issues for customers who relied on those URLs. We have identified the issue and are working on a fix.

2. identified Apr 09, 2026, 10:44 PM UTC

   We have merged a fix and are working on deploying it to production

3. identified Apr 10, 2026, 12:18 PM UTC

   We are still working on moving the fix to production as we experienced some testing issues.

4. resolved Apr 10, 2026, 07:54 PM UTC

   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.

Read the full incident report →

Started Apr 09, 2026, 03:37 PM UTC· resolved Apr 10, 2026, 11:51 AM UTC

1. investigating Apr 09, 2026, 03:37 PM UTC

   We are aware of an issue when connecting to Kibana through the Elastic Cloud UI via SAML SSO, impacting hosted Cloud deployments. Our team is actively investigating. We will post an update to this status within the next hour.

2. investigating Apr 09, 2026, 04:21 PM UTC

   We have identified that only PrivateLink customers are impacted and no other Hosted Cloud Deployments should see any issues.

3. investigating Apr 09, 2026, 04:41 PM UTC

   We have identified the issue and are working on a fix. We will update again in 3 hours or earlier.

4. investigating Apr 09, 2026, 07:50 PM UTC

   We have rolled out the fix and there should be no more customer impact

5. resolved Apr 10, 2026, 11:51 AM UTC

   We have confirmed no further impact from this incident, and are now marking it as resolved.

Read the full incident report →

Started Apr 06, 2026, 05:58 PM UTC· resolved Apr 06, 2026, 08:43 PM UTC

1. investigating Apr 06, 2026, 05:58 PM UTC

   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.

2. identified Apr 06, 2026, 07:16 PM UTC

   We have identified the problem and are working on a solution. We should have an update within the next 2-3 hours.

3. resolved Apr 06, 2026, 08:43 PM UTC

   Issue has been fixed and there should be no more customer impact

Read the full incident report →

Started Mar 30, 2026, 06:46 PM UTC· resolved Mar 30, 2026, 07:57 PM UTC

1. investigating Mar 30, 2026, 06:46 PM UTC

   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.

2. resolved Mar 30, 2026, 07:57 PM UTC

   Endpoints are operating normally

Read the full incident report →

Started Mar 27, 2026, 04:33 AM UTC· resolved Mar 27, 2026, 07:23 AM UTC

1. investigating Mar 27, 2026, 04:33 AM UTC

   We are currently investigating an outage of AutoOps in AWS us-east-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.

2. monitoring Mar 27, 2026, 05:37 AM UTC

   We have identified the issue and applied mitigations to bring AutoOps in the AWS us-east-1 region back to functionality. Customer deployments may still be marked as inactive, and recent metrics may still not be available. We expect AutoOps to return to full functionality within the next hour. We will provide an update when one is available or within the hour, whichever comes first.

3. monitoring Mar 27, 2026, 07:13 AM UTC

   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.

4. resolved Mar 27, 2026, 07:23 AM UTC

   AutoOps is back to full functionality in the AWS us-east-1 region and the incident has been resolved.

Read the full incident report →

Started Mar 26, 2026, 10:51 AM UTC· resolved Mar 26, 2026, 05:42 PM UTC

1. identified Mar 26, 2026, 10:51 AM UTC

   We are aware of problems creating new Serverless projects in the GCP europe-west3 region. The engineering team has identified the problem and we are working on mitigating it. We will post the next updated in 2 hours.

2. identified Mar 26, 2026, 01:06 PM UTC

   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

3. resolved Mar 26, 2026, 05:42 PM UTC

   This issue is resolved. Customers are now able to create new Serverless projects in the GCP europe-west3 region

Read the full incident report →

Started Mar 09, 2026, 11:32 AM UTC· resolved Mar 09, 2026, 08:29 PM UTC

1. investigating Mar 09, 2026, 11:32 AM UTC

   We have identified an issue impacting the provisioning of kibana resources for new projects. This may delay or fail requests for new projects. We are investigating the root cause, and will post updates shortly.

2. investigating Mar 09, 2026, 11:46 AM UTC

   Further investigations has indentified additional impact across services hosted in the GCP us-central1 region. We are working internally, and with our hosting providers to determine the root cause.

3. identified Mar 09, 2026, 12:05 PM UTC

   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 and scaling tasks.

4. monitoring Mar 09, 2026, 01:16 PM UTC

   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.

5. resolved Mar 09, 2026, 08:29 PM UTC

   This incident has been resolved.

Read the full incident report →

Started Feb 26, 2026, 11:29 AM UTC· resolved Feb 26, 2026, 05:07 PM UTC

1. investigating Feb 26, 2026, 11:29 AM UTC

   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.

2. monitoring Feb 26, 2026, 12:24 PM UTC

   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.

3. resolved Feb 26, 2026, 05:07 PM UTC

   This incident is resolved.

Read the full incident report →

Started Feb 25, 2026, 02:33 PM UTC· resolved Feb 25, 2026, 02:38 PM UTC

1. investigating Feb 25, 2026, 02:33 PM UTC

   We currently investigating an issue causing intermittent 404 errors when visiting the elastic.co webpage. We will provide additional updates as they become available.

2. resolved Feb 25, 2026, 02:38 PM UTC

   404 errors have been resolved on the elastic.co webpage.

Read the full incident report →

Started Feb 18, 2026, 05:56 PM UTC· resolved Feb 18, 2026, 07:12 PM UTC

1. investigating Feb 18, 2026, 05:56 PM UTC

   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.

2. resolved Feb 18, 2026, 07:12 PM UTC

   This issue is now resolved.

Read the full incident report →

Started Feb 12, 2026, 06:21 PM UTC· resolved Feb 13, 2026, 12:46 AM UTC

1. identified Feb 12, 2026, 06:21 PM UTC

   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.

2. resolved Feb 13, 2026, 12:46 AM UTC

   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.

Read the full incident report →

Started Feb 10, 2026, 06:35 PM UTC· resolved Feb 10, 2026, 10:51 PM UTC

1. investigating Feb 10, 2026, 06:35 PM UTC

   We are investigating a degradation in BYOK deployment creation in Azure regions. We will update again in one hour.

2. identified Feb 10, 2026, 07:49 PM UTC

   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.

3. resolved Feb 11, 2026, 01:01 PM UTC

   This issue has been resolved, and BYOK deployment creation has been confirmed as fully functional.

Read the full incident report →

Started Feb 09, 2026, 04:53 PM UTC· resolved Feb 10, 2026, 10:22 AM UTC

1. investigating Feb 09, 2026, 04:53 PM UTC

   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

2. investigating Feb 09, 2026, 07:35 PM UTC

   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.

3. resolved Feb 10, 2026, 10:22 AM UTC

   We have completed our work to restore access to`openai-gpt-oss-120b` model in EIS.

Read the full incident report →

Started Feb 06, 2026, 01:56 AM UTC· resolved Feb 06, 2026, 04:22 AM UTC

1. investigating Feb 06, 2026, 01:56 AM UTC

   We are currently investigating an issue that has resulted in provisioning delays affecting the creation of new Elastic Cloud Serverless projects within the AWS us-east-1 region. While existing projects remain operational and unaffected, customers may encounter errors or extended wait times when attempting to spin up new projects in this specific region. Our engineering team is actively working to identify the root cause and restore full functionality. We apologize for the inconvenience and will provide further updates as more information becomes available.

2. identified Feb 06, 2026, 02:43 AM UTC

   We have successfully identified the root cause of the provisioning delays in the AWS us-east-1 region and are now beginning the remediation phase. A fix has been developed and validated through internal testing, and we are currently rolling out the fix across the affected infrastructure. Customers may still see intermittent failures for a short period as the fix propagates.

3. resolved Feb 06, 2026, 04:22 AM UTC

   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.

Read the full incident report →

Started Feb 02, 2026, 11:01 PM UTC· resolved Feb 03, 2026, 10:42 AM UTC

1. monitoring Feb 02, 2026, 11:01 PM UTC

   We are aware of an active incident involving Microsoft Azure infrastructure that is impacting Elastic Serverless and Elastic Hosted services. Customers may experience failures or significant delays when attempting to provision new Serverless projects, create new Hosted deployments, or perform scaling operations on existing clusters. Our engineering team is closely monitoring the situation. Existing, steady-state deployments in Azure remain operational. There is also no impact to projects or deployments in other cloud providers. We will provide further updates as more information becomes available.

2. monitoring Feb 03, 2026, 12:26 AM UTC

   We are continuing to monitor an open incident on the Microsoft Azure side. At this time, we are not aware of any further active impact to Elastic customers or services; however, we will remain in a monitoring state until Azure provides official confirmation that the incident is fully resolved on their end.

3. monitoring Feb 03, 2026, 03:52 AM UTC

   There is no new information to report at this time. We are still awaiting a final resolution from Microsoft Azure regarding their ongoing incident. As soon as Azure confirms the issue is resolved on their side, we will provide a final update.

4. monitoring Feb 03, 2026, 07:37 AM UTC

   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 very close monitoring status until Azure provides official confirmation that the incident is fully resolved.

5. resolved Feb 03, 2026, 10:42 AM UTC

   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.

Read the full incident report →

Started Jan 23, 2026, 01:10 AM UTC· resolved Jan 23, 2026, 07:31 AM UTC

1. monitoring Jan 23, 2026, 01:10 AM UTC

   Some Elastic Cloud customers may be experiencing issues with receiving emails for account verification and MFA due to an upstream third-party incident. We are actively monitoring this and will post periodic updates or as new information becomes available.

2. monitoring Jan 23, 2026, 03:55 AM UTC

   We are continuing to monitor the status of the upstream provider's incident. We will continue to post periodic updates or as new information becomes available.

3. resolved Jan 23, 2026, 07:31 AM UTC

   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.

Read the full incident report →

Started Jan 23, 2026, 12:37 AM UTC· resolved Jan 23, 2026, 03:51 AM UTC

1. investigating Jan 23, 2026, 12:37 AM UTC

   Customers may observe some data delay in AutoOps functionality for Elastic Cloud Hosted clusters in GCP US Central. We're actively investigating this.

2. monitoring Jan 23, 2026, 12:56 AM UTC

   We've determined that AutoOps functionality has fully recovered for Elastic Cloud Hosted clusters in GCP US Central.

3. resolved Jan 23, 2026, 03:51 AM UTC

   The incident has been resolved.

Read the full incident report →

Started Dec 24, 2025, 08:37 AM UTC· resolved Dec 25, 2025, 03:17 AM UTC

1. investigating Dec 24, 2025, 08:37 AM UTC

   We are currently investigating an outage of AutoOps in GCP us-central-1. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.

2. investigating Dec 24, 2025, 09:37 AM UTC

   We are currently investigating an outage of AutoOps in GCP us-central-1. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.

3. identified Dec 24, 2025, 11:01 AM UTC

   We have implemented mitigations to restore AutoOps functionality in GCP us-central-1. Customer deployments in the region may still be marked as inactive and recent metrics may not be available. We are monitoring its recovery and will provide an update within an hour.

4. identified Dec 24, 2025, 12:05 PM UTC

   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 be marked as inactive, and recent metrics may not be available.

5. identified Dec 24, 2025, 01:03 PM UTC

   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 be marked as inactive, and recent metrics may not be available.

6. identified Dec 24, 2025, 02:06 PM UTC

   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 be marked as inactive, and recent metrics may not be available.

7. identified Dec 24, 2025, 03:16 PM UTC

   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 be marked as inactive, and recent metrics may not be available.

8. monitoring Dec 24, 2025, 04:22 PM UTC

   AutoOps functionality has been restored in the GCP us-central-1 region. We are continuing to monitor the system for signs of service degradation.

9. identified Dec 24, 2025, 05:20 PM UTC

   We are continuing to see intermittent impact in the GCP us-central-1 region, which is causing some customer deployments to be marked as inactive. We are continuing to investigate the issue and will continue to provide updates as they become available.

10. identified Dec 24, 2025, 07:07 PM UTC

    We are continuing to investigate an issue impacting AutoOps deployments in the GCP us-central-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will continue to provide updates as they become available.

11. identified Dec 24, 2025, 09:05 PM UTC

    We are continuing to investigate an issue impacting AutoOps deployments in the GCP us-central-1 region. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will continue to provide updates as they become available.

12. identified Dec 24, 2025, 10:27 PM UTC

    We are continuing to see intermittent impact in the GCP us-central-1 region, which is causing some customer deployments to be marked as inactive. We are continuing to investigate the issue and will continue to provide updates as they become available.

13. identified Dec 24, 2025, 11:26 PM UTC

    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 be marked as inactive, and recent metrics may not be available until it is fully recovered.

14. identified Dec 25, 2025, 12:35 AM UTC

    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 be marked as inactive, and recent metrics may not be available until it is fully recovered.

15. monitoring Dec 25, 2025, 02:19 AM UTC

    AutoOps functionality has been restored in the GCP us-central-1 region. We are continuing to monitor the system for signs of service degradation.

16. resolved Dec 25, 2025, 03:17 AM UTC

    The system is operational.

Read the full incident report →

Started Dec 23, 2025, 03:29 AM UTC· resolved Dec 23, 2025, 05:29 AM UTC

1. investigating Dec 23, 2025, 03:29 AM UTC

   We are currently investigating a partial outage of AutoOps in GCP us-central-1. Customer deployments in the region may be marked as inactive and recent metrics may not be available. We will provide an update when one is available or within the hour, whichever comes first.

2. identified Dec 23, 2025, 04:24 AM UTC

   We have identified the underlying cause of the issue and are applying a fix. We will post another update as it becomes available or within an hour, whichever is first.

3. monitoring Dec 23, 2025, 04:47 AM UTC

   We are seeing recovery in the system with the deployed fix, and are continuing to monitor the health of the system.

4. resolved Dec 23, 2025, 05:29 AM UTC

   The system is operational.

Read the full incident report →

Started Dec 17, 2025, 12:10 PM UTC· resolved Dec 17, 2025, 12:49 PM UTC

1. identified Dec 17, 2025, 12:10 PM UTC

   We're aware of delays affecting emails being sent for customers, such as password reset requests, receiving billing invoices and adding users to organisations. Our team is investigating the issue and we will provide updates on our progress.

2. resolved Dec 17, 2025, 12:49 PM UTC

   Our teams have resolved an issue with the mail system, which caused delays for emails being sent for customers such as password reset requests, receiving billing invoices and adding users to organisations.

Read the full incident report →

Started Dec 11, 2025, 04:50 PM UTC· resolved Dec 11, 2025, 08:23 PM UTC

1. identified Dec 11, 2025, 04:50 PM UTC

   We are aware of an issue impacting deployments created after December 3rd that causes the AutoOps button to appear greyed out. Affected AWS regions are af-south-1, ap-east-1, ap-northeast-2, aws-ap-southeast-2, ca-central-1, me-south-1, sa-east-1, eu-north-1, eu-south-1, eu-west-3, us-west-1, eu-central-2. The us-central-1 GCP region is also affected. Our engineers have been engaged and are currently working on a resolution. We will provide an update within 1 hour, or sooner if appropriate

2. identified Dec 11, 2025, 05:58 PM UTC

   Our engineers have deployed a change and new deployments will be able to use AutoOps. We are still working on fixing the affected deployments between December 3 and today. We will provide an update within 1 hour, or sooner if appropriate.

3. monitoring Dec 11, 2025, 06:56 PM UTC

   We have completed the roll out of the fix and are monitoring to confirm resolution. We will post an update in an hour or sooner.

4. resolved Dec 11, 2025, 08:23 PM UTC

   The fix is working as expected. This issue is resolved

Read the full incident report →

Started Dec 04, 2025, 08:29 PM UTC· resolved Dec 04, 2025, 10:31 PM UTC

1. identified Dec 04, 2025, 08:29 PM UTC

   We are aware of issues where system emails are not being delivered. We are investigating and will provide an update in two hours or earlier on our investigation.

2. monitoring Dec 04, 2025, 08:59 PM UTC

   We've identified the issue and have started processing the backlog of emails. We will continue to monitor the situation until the backlog is cleared.

3. resolved Dec 04, 2025, 10:31 PM UTC

   This incident is now resolved as the backlog of emails has been cleared.

Read the full incident report →

Started Nov 28, 2025, 10:42 PM UTC· resolved Nov 29, 2025, 11:25 AM UTC

1. investigating Nov 28, 2025, 10:42 PM UTC

   We are currently investigating an increase in HTTP 502 errors affecting Serverless projects running in Azure regions.

2. investigating Nov 29, 2025, 12:02 AM UTC

   We are continuing our investigation into the intermittent 5xx errors in Azure Serverless projects. We will update again in an hour.

3. identified Nov 29, 2025, 01:24 AM UTC

   We have identified a potential fix that we are in the process of rolling out. We anticipate this to be complete in approximately 3-4 hours. We will update when this process is complete.

4. identified Nov 29, 2025, 05:20 AM UTC

   We are continuing the rollout of the potential fix. We will update again in an hour

5. identified Nov 29, 2025, 06:50 AM UTC

   We are continuing the rollout of the potential fix. We will update again in an hour

6. identified Nov 29, 2025, 07:50 AM UTC

   We are continuing the rollout of the potential fix. We will update again in an hour

7. monitoring Nov 29, 2025, 10:08 AM UTC

   We have completed the roll out of the fix and are monitoring to confirm resolution. We will post an update in an hour or sooner.

8. resolved Nov 29, 2025, 11:25 AM UTC

   The fix is working as expected. This issue is resolved

Read the full incident report →

Started Nov 21, 2025, 04:52 AM UTC· resolved Nov 21, 2025, 06:09 AM UTC

1. investigating Nov 21, 2025, 04:52 AM UTC

   We are aware of ingestion problems in Managed OTLP Endpoint & Managed Intake Service for GCP us-central1 region since 0338 UTC. Other regions remain unaffected. We are currently investigating the problem. We will publish more information as it becomes available. Next update in 1 hr

2. investigating Nov 21, 2025, 05:11 AM UTC

   We are continuing to investigate this issue.

3. monitoring Nov 21, 2025, 05:48 AM UTC

   Ingestion rates are back to normal, we're currently monitoring the situation.

4. resolved Nov 21, 2025, 06:09 AM UTC

   Ingestion rates are normal, the incident is resolved

Read the full incident report →

Started Nov 18, 2025, 01:46 PM UTC· resolved Nov 18, 2025, 06:35 PM UTC

1. monitoring Nov 18, 2025, 01:46 PM UTC

   We are seeing intermittent 404s/500s on elastic.co. This is due to an outage with one of our providers. Our team is monitoring and will update as we know more.

2. monitoring Nov 18, 2025, 03:28 PM UTC

   The underlying outage with our provider is reported as resolved. We will continue monitoring to ensure our service is fully operational.

3. resolved Nov 18, 2025, 06:35 PM UTC

   The situation has been resolved.

Read the full incident report →