Elasticsearch Outage History

This issue has been resolved.

We have identified and deployed a fix for this issue and are continuing to closely monitor the situation.

We are currently investigating an issue when creating/updating Deployments in several regions. We've identified the issue and working on applying a fix. We will provide an update when one is available or within the hour, whichever comes first.

This issue is resolved.

This incident is ongoing. The upstream providers are aware and working to resolve the issue. We will provide an update when the status changes or within an hour, whichever comes first.

We are currently experiencing an issue impacting the ability to ingest data into mOTLP and .amp endpoints in the Azure Australia East region.  The upstream providers are aware and working to resolve the issue.  We will provide an update when the status changes or within an hour, whichever comes first.

We have identified the root cause and mitigated the issue. Users should now be able to log in to Kibana via the "Log in with Elastic Cloud" button.

We are continuing to investigate this issue.

We have detected an issue with the Kibana authentication flow for both Deployments and Projects. Authenticating to Kibana using the "Log in with Elastic Cloud" button results in an authentication failure. A workaround is to access Kibana using the link inside the Elastic Cloud console. We are currently working on a resolution. Our team is currently identifying the root cause to resolve the issue. We will share another update in the next hour.

This issue has been resolved.

This issue has been mitigated, and we are continuing to monitor the situation.

We are currently investigating an intermittent issue which may cause unavailability of Elastic Cloud Serverless projects or the inability to create new Serverless projects in AWS us-east-1.  We will continue to update status as we learn more.

This incident has been resolved.

Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are seeing increased recovery across as we monitor the situation. Services are being restored. Monitoring is continuing, and we will provide further updates as we progress.

Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. Recovery has started and we will provide further updates as we progress.

Customers may see delays with creating Azure serverless projects and existing Azure projects may be temporarily unavailable. We are currently investigating the issue.

This incident has been resolved.

We continue to monitor the situation which has mostly recovered. A small number of deployments are still not healthy. Our support team is working on resolving these on a case-by-case basis.

Remediation is underway and systems are recovering. We  continue to monitor the situation and will post an update in the next 2 hours or earlier.

We continue to remediate the impact of an upstream Azure outage in Azure West US 2 (azure-westus2), limited to availability zone westus2-2. Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors, degraded performance, or delays when performing deployment operations. Deployments configured for high availability across multiple availability zones are not expected to be affected. Our teams remain actively engaged with Microsoft Azure and are working to restore affected infrastructure. We will provide further updates as recovery progresses

We continue to respond to an upstream Microsoft Azure outage in Azure West US 2 (azure-westus2), caused by a datacenter power event reported by Azure. Elastic impact remains limited to availability zone westus2-2. Customers with deployments not configured for high availability in this region may continue to experience intermittent connectivity errors, degraded performance, or delays when performing deployment operations (including create, edit, restart, and delete). Deployments configured for high availability across multiple availability zones are not expected to be affected. Our teams are actively remediating affected infrastructure in the impacted zone. Recovery progress is currently constrained by degraded Azure platform APIs and capacity availability in the region.

We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region. We have confirmed that impact to our service is limited to a single availability zone (westus2-2). Customers whose deployments are not configured for high availability may experience intermittent errors, delays, or inability to access certain features. Deployments configured for high availability across multiple zones are not expected to be affected. Our team is working to mitigate the situation and the impact on our environment. We will provide further updates as more information becomes available.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are continuing to investigate the impact of an upstream Azure WestUS2 outage which is impacting Elastic services and deployment healthiness, including Elastic Serverless projects hosted in this region. We have confirmed that impact to our service is limited to a single availability zone (westus2-2). Customers whose deployments are not configured for high availability may experience intermittent errors, delays, or inability to access certain features. Deployments configured for high availability across multiple zones are not expected to be affected. Our team is working to mitigate the situation and the impact on our environment. We will provide further updates as more information becomes available.

This issue has been resolved.

We're aware of an issue with creating Serverless projects in the AWS ap-southeast-2 region. The engineering team is investigating the problem. We will post the next update in 2 hours.

Some users experienced missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure Southeast Asia region. We have already stabilized the situation.

The system has recovered and functionality has returned to normal.

The problem has been identified and is being stabilized, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.

Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the Azure North Europe region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 1 hour.

Synthetics browser monitors running in Europe-Germany region (GCP europe-west3) for some of the users were experiencing delayed executions results and some of them being stopped. The issue affected both Elastic Cloud Hosted and Elastic Cloud Serverless in that region and other regions were not impacted.

We have confirmed no further impact from this incident, and are now considering this issue resolved. Thank you for your patience.

We are aware of issues resulting in temporary unavailability across multiple Serverless projects. From 08:00 UTC to 09:40 UTC on May 11, Search, Ingest and EIS functionality may have been unavailable. The root cause of this issue has been identified and resolved - we are currently monitoring, and expect no further impact.

This issue is now resolved. Email delivery has been successful with no monitored issues.

A solution has been implemented, and email delivery has resumed. We are continuing to track the situation closely and will provide another update once considered resolved.

We are currently investigating reports that some customers may be facing issues with email alerts.

This issue has now been resolved.

This issue has now been resolved and we are continuing to monitor the system.

We have identified and are working to mitigate an issue which is causing delayed AutoOps metrics for customers in AWS us-east-1.

The system has recovered and functionality has returned to normal.

We are continuing to see signs of stabilization and monitoring as the system recovers, but metrics visualizations in the Cloud console remains impacted until recovery is complete. We will provide a further update in 1 hour, or when there is a change in status.

Our investigation is ongoing.  We continue to see early signs of stabilization, but metrics visualizations in the Cloud console remain impacted.  We will provide a further update in 1 hour, or when there is a change in status.

Our investigation is ongoing. Some early signs of stabilisation have been observed, but metrics visualizations in the Cloud console remain impacted. We will provide a further update within 30 minutes.

Some users are seeing missing metrics visualizations in the Cloud console due to a disruption in metric data ingestion affecting deployments in the us-east-1 (US East) region. Some recent metric data may not appear in charts or monitoring views. We are actively investigating and will provide another update within 30 minutes.

The connectivity issues affecting a subset of customers in our AWS EU West (Paris) region have been resolved. Failed probes recovered at 11:36 UTC following remediation of an issue with our underlying cloud infrastructure provider. We are no longer observing any elevated error rates or latency in the region. We apologise for any inconvenience caused and will conduct a post-incident review.

Our monitoring system reports that AWS EU West 3 (Paris) region ingress layer traffic has recovered to normal levels as of 11:36 UTC and our SLO alerts have resolved. We are continuing to monitor and will update once we are confident the issue is fully resolved.

We are continuing to work on a fix for this issue.

We are currently investigating connectivity issues affecting a subset of customers in our AWS EU West 3 (Paris) region. Some requests may be experiencing elevated latency or failures. Our team is actively investigating, and we are working with our cloud infrastructure provider on the underlying issue. Other regions are not affected at this time. We will provide updates as the situation develops.

An incident with an upstream service provider has been resolved, and access to the model is now restored.

Errors are coming from the provider API (Google). The incident has been escalated to them, and we are still waiting for a response.

We're seeing elevated 5xx error rates for the Gemini Embedding v1 model in EIS. The following default inference endpoint is affected: - .google-gemini-embedding-001 We're investigating and will update again in 2 hours or if there's a change in status.

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.

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

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

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.

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

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

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

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

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.

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

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

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.

Endpoints are operating normally

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.

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

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.

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.

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.

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

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

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.

Update — This incident is still ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email mailto:support@elastic.co.

Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email support@elastic.co.

Update — Incident ongoing. AWS Bahrain (me-south-1) has been removed from new deployment selection on cloud.elastic.co. Existing deployments remain inaccessible due to the AWS infrastructure disruption, with no recovery timeline provided by AWS. Assume the region is unavailable for the foreseeable future. For assistance, please open a case in our Support portal (https://support.elastic.co) or email support@elastic.co.

Update — This incident remains ongoing. AWS Bahrain (me-south-1) has been removed from the available region selection on cloud.elastic.co and is unavailable for new deployments. Existing deployments in me-south-1 remain inaccessible due to the ongoing AWS infrastructure disruption. AWS has not provided a recovery timeline for the region. Customers should continue to assume the region is unavailable for the foreseeable future. We continue to support impacted customers individually through our support channels. If you have not yet done so, please open a case so we can assist with your recovery options. For assistance, please open a case in our Support portal (https://support.elastic.co) or email mailto:support@elastic.co. Apr 20, 2026 — 00:00 UTC

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 our Support portal (https://support.elastic.co) or email support@elastic.co.

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 support@elastic.co.

We have identified a further potential disruption to our services hosted in the AWS Bahrain (me-south-1) region. We are working to determine the scope of this impact, and have engaged with AWS as the providers in this investigation. Further updates will be posted within the hour, or when we have further information.

There are no new updates. 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 support@elastic.co.

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 support@elastic.co.

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 support@elastic.co.

We are aware of connectivity and power issues affecting AWS Bahrain (me-south-1) due to localized power issues. We are awaiting further updates from AWS and will update here once we have more information.

This incident is resolved.

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.

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.

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

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

This issue is now resolved.

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.

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.

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.

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

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.

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

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

The incident has been resolved.

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

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

The system is operational.

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

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.

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.

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.

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.

The system is operational.

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

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.

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.

The fix is working as expected. This issue is resolved

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.

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.

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

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

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.

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.

The fix is working as expected. This issue is resolved

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.

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

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

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

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.

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

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

Ingestion rates are normal, the incident is resolved

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

We are continuing to investigate this issue.

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

The situation has been resolved.

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

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.

The issue has been successfully mitigated and full service has been restored to the AWS region; the root cause involved an internal provisioning system temporarily preventing the application of new hosted plans, which has now been corrected. We will continue to monitor the system closely.

We are actively investigating the root cause of the incident and are working towards a full resolution. The next update will be provided as soon as significant progress is made or a preliminary resolution timeframe is established.

We are currently investigating an issue with Elastic Cloud Hosted in the eu-west-1 region of AWS. Customers may be experiencing issues with upgrades, new deployments, and vacates in that region.

The issue affecting the creation of new Serverless projects has been fully resolved. The service is functioning normally, and no further impact is expected.

We have deployed a fix for the issue affecting the creation of new Serverless projects. The service is operating as expected, and we are monitoring the system to ensure stability. We will provide a final update once the incident is fully resolved.

We have identified the root cause of the issue affecting the creation of new Serverless projects. Our team is currently preparing a patch to restore full functionality. We will provide another update once the fix is deployed.

We are currently investigating an issue that prevents creating new Serverless projects. Our team is working to find the cause, and we will provide a status update as soon as more information becomes available.

This issue has been resolved, and system operations returned to normal.

We have identified the cause of this issue and are currently applying a fix. We are seeing recovery in the system and will continue to monitor.

We are continuing to investigate this issue. We will share an update when one is available or one hour from now, whichever comes first.

We are aware of an issue impacting all serverless regions interacting with the Synthetics service. We will provide an update when more information is available or in one hour, whichever is sooner.

We are currently investigating an issue with Azure impacting some of our services, specifically Managed OTLP and MIS.

We are currently investigating an issue with Azure impacting some of our services, specifically Managed OTLP and MIS.

This issue has been resolved.

This issue has been mitigated and new Deployments are coming up as expected. We are continuing to monitor.

We are experiencing an issue with new Deployments taking longer than expected to create in AWS us-east-1. We'll post an update on this within the hour