Elasticsearch Outage History

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

The issue has been fully resolved.

The issue has been resolved and a backlog of metrics is being processed which should clear in the next hour.

We are aware of issues impacting the display of deployment metrics in Elastic Cloud Hosted GCP us-central1 region, we are working to resolve this

This incident has been resolved.

We've seen a complete restoration of services. We're continuing to monitor closely and will resolve the incident in one hour if no new impact is detected.

We continue to experience issues with capacity availability impacting deployment creation and scale-out in AWS us-east-1 related to the earlier incident and are continuing to monitor. This may also impact Serverless usage data being available in the console (but no impact to billing itself). We will provide a further update within two hours, or sooner if the situation changes.

We continue to experience issues with capacity availability impacting deployment creation and scale-out in AWS us-east-1 related to the earlier incident and are continuing to monitor. This may also impact Serverless usage data being available in the console (but no impact to billing itself). We will provide a further update within two hours, or sooner if the situation changes.

We are still experiencing issues with capacity availability impacting deployment creation and scale-out in AWS us-east-1 related to the earlier incident and are continuing to monitor. We will provide a further update within an hour.

We are still seeing some issues with capacity availability impacting deployment creation in AWS us-east-1 related to the earlier incident and are continuing to monitor. We will provide a further update within an hour.

We are still seeing some issues with capacity availability impacting deployment creation in AWS us-east-1 related to the earlier incident and are continuing to monitor. We will provide a further update within an hour.

We are still seeing some instability with deployment creation in AWS us-east-1 related to the earlier incident and are continuing to monitor. We will provide a further update within an hour.

All services are operating normally and we are continuing to monitor closely. We will provide a further update within an hour.

Project and Deployment creation on Elastic Cloud Serverless and Elastic Cloud Hosted is back to normal, we are continuing to monitor the situation and will provide a further update within an hour.

We are currently experiencing an issue with Project and Deployment creation on Elastic Cloud Serverless and Elastic Cloud Hosted, we are monitoring the situation and working to resolve it. We'll provide an update within the hour.

We are currently experiencing an issue with Project and Deployment creation on Elastic Cloud Serverless and Elastic Cloud Hosted, we are monitoring the situation and working to resolve it. We'll provide an update within the hour.

A fix for this issue has been deployed and it is again possible to create BYOK (Bring-your-own-KEy) deployments in our GCP regions

We have identified the issue preventing creation of deployments in GCP regions using BYOK (Bring-your-own-Key), and we are currently working on deploying a fix.

BYOK Deployment creation in GCP regions is not currently possible, existing deployments are not impacted. The team is working on a mitigation path.

This incident has been resolved.

The mitigations have been effective in preventing the latency from reocurring. We will continue to monitor closely while a permanent fix is being validated and deployed. We will provide the next status page update in 4 hours or as soon as we have new information.

We continue to monitor the impact of the mitigations. We will provide the next status page update in 4 hours or as soon as we have new information.

We have applied mitigations that should prevent the latency from spiking up again. We are monitoring the impact. We will provide the next status page update in 180 minutes or as soon as we have new information.

We continue to monitor the issue. We will provide another update in about 60 minutes.

The latency is back to pre-incident level. We continue to monitor the issue. We will provide another update in about 60 minutes.

We continue to investigate the increased latency in authentication requests to Elastic Cloud Console. We will provide next update in 60 minutes or as soon as we know more.

We observed increased latency in customer logins to Cloud Console. We are currently investigating.

This incident is now resolved. All functionality has been returned to normal and we have seen no service degradation since mitigating the incident.

This incident is now mitigated. We have found the cause of the disruption and have implemented a solution. All customers should be back to regular operating status. We will continue to monitor the status of customer deployments and resolve this incident shortly.

We have identified an issue regarding the visibility of the status of Hosted deployments. We are continuing our efforts in working this issue to a resolution state. We will post an update in one hour, or sooner if there is a change in status.

We are aware of a potential service impact with the visibility of the status of Hosted Deployments. Our team is currently investigating. Users may see out of date information regarding their Hosted deployments. Our next update will be in one hour, or sooner if there is a change in status.

We have completed our work to restore service to Hosted deployment creation in AWS EU West 1.

The resolution has been deployed, and we are now monitoring deployment creation in AWS EU West 1 for Hosted deployments. We will post an update in one hour, or sooner if the status changes.

We have identified an issue for creating new Hosted deployments in AWS EU West 1. We are continuing our efforts in working this issue to a resolution state. We will post an update in one hour, or sooner if there is a change in status.

We are aware of an issue impacting the creation of Hosted deployments on the AWS EU West 1 region. Our engineering team has been engaged. We will post an additional status update in the next 60 minutes.

This incident has been resolved.

We have identified an issue for creating new Serverless projects and Hosted deployments. Billing information pages are also impacted and do not load. We are continue our efforts in working this issue to a resolution state. We will post an update in one hour, or sooner if there is a change in status.

Our engineering teams are making good progress on the investigation into the issue affecting the creation of Serverless projects, Hosted deployments, and Billing pages. We are still actively working toward a resolution. We will provide our next update in 60 minutes.

We are continuing our efforts to restore full service to the creation of both Serverless projects and Hosted deployments and the Billing information pages. Our teams are working collaboratively in their impact mitigation efforts and we are actively driving to a resolution. We will post an update in one hour, or sooner if there is a change in status.

We are continuing our efforts to restore full service to the creation of both Serverless projects and Hosted deployments. Our teams are working collaboratively in their impact mitigation efforts and we are actively driving to a resolution. We will post an update in one hour, or sooner if there is a change in status.

We are aware of an issue impacting the creation on both Serverless projects and Hosted deployments. Our engineering team is working to remediate this issue. We will post another status update in the next 60 minutes.

We are aware of an issue impacting the creation of new Serverless projects and Hosted deployments to fail. Our engineering team has been engaged. We will post an additional status update in the next 60 minutes.

Our team has implemented a fix and the incident is now resolved.

We have identified an issue affecting provisioning and scaling of projects for Serverless in GCP - Mumbai (asia-south1). Our team is working to resolve the situation and will provide updates as more information becomes available.

We are currently investigating issues affecting provisioning and potential scaling of Serverless projects in the GCP Asia-South1 region. Our team is actively monitoring the situation and will provide updates as more information becomes available.

We have observed service levels have returned to their healthy and expected state.

We have observed an increase in errors for some Serverless observability customers in Azure regions between 13:39 to 14:16 UTC. This is resolved but our teams are continuing to monitor.

We have observed service levels have returned to their healthy and expected state.

We have observed improvements to provisioning new capacity which can affect deployment creation and updates. Some customers may be experiencing a degraded impact. We have identified the cause with our upstream provider and continue to work towards a mitigation. Our next update will be in one hour.

We are experiencing a partial service outage with provisioning new capacity which can affect deployment creation and updates. Our team is currently working to restore the service. All Cloud Hosted users may be affected. Our next update will be in one hour.

The incident affecting adminconsole operations on Elastic Cloud Hosted has been mitigated. We successfully identified and isolated the problematic node, and normal service has been restored. Our team will continue to closely monitor the situation.

We are aware of an issue affecting Elastic Cloud Hosted, where users may be experiencing timeouts when performing adminconsole operations. Our team has identified the underlying issue and is actively working on a solution to mitigate the issue as quickly as possible. We will provide another update as soon as we have more information.

The incident is resolved.

We've validated that any delay in new deployment creation and existing deployment change activity has been resolved. We will continue to monitor.

Some Elastic Cloud Hosted customers may be observing delays with new deployment creation and existing deployment changes in AWS eu-central-1 and ap-southeast-1 regions. We will post another status update within 30 minutes or as new information becomes available.

This incident has been resolved.

A fix has been implemented and we can confirm the Elastic documentation is fully available again. We continue to monitor the situation.

The issue has been identified and a fix is currently being deployed. We will provide an update in the next 30 minutes.

We’re investigating an issue causing elastic.co/docs to be unavailable. Our team is working to restore access as quickly as possible. Other Elastic services are not impacted.

We have released new versions (8.19.1 and 9.1.1) to address the cause. New deployments may use these versions, or existing deployments may upgrade to them. Existing deployments already using these versions can use the mitigation available. For details, please refer to our Knowledge Base article: Mitigation steps (Elastic Cloud account required): https://support.elastic.co/knowledge/40e6b9d4

A fix has been identified and is being validated. Once verified, a new release will be made available. An update will be provided when the release is available.

We have delisted versions 8.19.0 and 9.1.0, preventing new deployments and/or upgrades from using these versions. Existing deployments already using these versions can use the mitigation available. For details, please refer to our Knowledge Base article: Mitigation steps(Elastic Cloud account required): https://support.elastic.co/knowledge/40e6b9d4 Work continues on a broader fix. New updates will be provided as progress is made.

We have identified the root cause of the issue affecting APM availability when creating new deployments in versions 8.19.0 and 9.1.0. APM Server encounters an error during provisioning, which results in the APM endpoint being unavailable. A mitigation is available for users who have already upgraded. For details, please refer to our Knowledge Base article: Mitigation steps(Elastic Cloud account required): https://support.elastic.co/knowledge/40e6b9d4 We are working on a broader fix and will continue to provide updates as progress is made.

We're currently investigating an issue where the APM endpoint is not available (greyed out) when creating deployments on versions 8.19.0 and 9.1.0. Initial findings indicate that APM Server is throwing errors during the provisioning process, which may impact user ability to enable APM in affected versions. Our engineering teams are actively investigating the root cause and implementing mitigation steps. We'll provide an update as soon as more information becomes available.

This incident has been resolved.

The impact of this issue to customers remains mitigated. Changes to safeguard against additional impact have been deployed. We are continuing to monitor the situation and will provide an update if there are any status changes.

The impact of this issue to customers has been mitigated. Our engineering team is actively monitoring the situation and deploying safeguards to ensure there is no additional impact. We will provide an additional update in 60 minutes or as soon as we have an additional development.

We have identified additional impact of this issue impacting Serverless project creation and scaling in additional GCP regions. Our engineering team is currently working to implement and roll out a fix to mitigate the issue. We will provide an additional update in 60 minutes or as soon as we have an additional development.

A fix has been implemented across all affected clusters, and we keep monitoring the situation closely. Initial observations indicate that services related to project creation and scaling are returning to normal operation. We will continue to monitor the situation for stability and provide an update if there are any new developments.

A fix has been implemented across all affected clusters, and we keep monitoring the situation closely. Initial observations indicate that services related to project creation and scaling are returning to normal operation. We will continue to monitor the situation for stability and provide an update if there are any new developments.

A fix has been implemented across all affected clusters, and we keep monitoring the situation closely. Initial observations indicate that services related to project creation and scaling are returning to normal operation. We will continue to monitor the situation for stability and provide an update if there are any new developments.

We have a candidate fix in a testing environment where we have successfully applied it to the first set of affected clusters. We have confirmed that project creation and scaling are now functioning. The rollout of the fix to the remaining impacted environments is ongoing, and we will continue to monitor the situation closely. We will provide our next update within 60 minutes, or as soon as we have a significant development.

We have identified the root cause of the issue affecting deployment creation and scaling on Google Cloud Platform, which is related to a recent automated infrastructure update from our cloud provider. A mitigation plan has been identified, and our teams are coordinating to apply it across the affected clusters. We have also taken steps to prevent further impact. We will provide another update within 60 minutes with more details on the timeline for resolution.

We are currently investigating an issue that is primarily affecting new deployment creations for some customers on Google Cloud Platform. Existing deployments remain operational; however, there is a potential for impact to scaling operations which we are actively investigating. Our engineering teams are working to identify the root cause and restore full functionality. We will provide a further update within 60 minutes, or sooner if we have significant new information.

This incident has been resolved.

The impact to customers is now mitigated. We will continue to monitor closely and post any updates if necessary.

We are currently investigating an issue where clients are receiving HTTP 429 (Too Many Requests) responses from our authentication APIs. This may affect login and token-related operations for some users. Our engineering team is actively working to identify the root cause and implement a fix. We will report back in an hour or sooner if appropriate.

This issue has been resolved.

The impact to customers is now mitigated. We will continue monitoring for further impact and provide an update in one hour, or sooner if there is a change in status.

We are investigating reports of unavailability of our docker registry UI at docker.elastic.co. At this time this is an issue only with the UI. Docker registry functionality continues to work as usual. We will report back in an hour or sooner if appropriate

The billing process for LLM chat inference has been fixed. ECH customers should now see their inference usage reported normally under their organization's billing page.

ECH customers using LLM chat inference through the Elastic Inference Service may be under-billed for their usage. The issue has been identified and a fix is under way.

We have determined that this was actually a mistake with our alerting and there was no customer impact.

We are investigating issues with our Serverless Managed OTLP Endpoint service, where some traffic is being rejected with a 401. We will update again in an hour or earlier.

We have resolved impact to customers and project creation in all regions should be back to normal.

We’re experiencing issues with Serverless projects creation in Azure (azure-eastus region) and our team is actively investigating what the root cause is. Users may experience issues with new Serverless project creations in this region. We will post an update in one hour, or sooner if there is a change in status.

This incident has been resolved successfully.

We have applied a fix to the affected service, and full functionality should be restored. We are monitoring the situation for stability, and will continue to provide any necessary update.

We are experiencing a partial service outage with Serverless and Hosted trials creation. Our team is actively investigating the cause so that they can mitigate and restore the service. We believe all new customers may be affected. We will post an update in one hour, or sooner if there is a change in status.

We have completed our work to restore service to all customers.

We have applied a fix to restore service to all impacted AutoOps customers. We will continue monitoring for further impact and provide an update in one hour, or sooner if there is a change in status.

We are investigating signs of service degradation with the AutoOps service in multiple regions (us-east-1, us-east-2, eu-west-1, eu-west-2, us-west-2, eu-central-1, ap-southeast-1, ap-south-1, ap-northeast-1). Our team is actively investigating the cause so that they can mitigate and restore the service. Other services are not affected. We will post an update in one hour, or sooner if there is a change in status.

We are aware of a potential service impact with AutoOps. Our team is currently investigating. eu-central-1 users may be affected. Our next update will be in one hour, or sooner if there is a change in status.

We have seen no further uptick in response rate latency, therefore we are calling this incident resolved.

The impact to customers is now resolved and we've seen a stabilization in response rates. We will continue to monitor this for a few hours.

We are investigating some response rate slowdowns in our Deployments API. Impact is limited to the AWS us-east-1 region and to managing deployments, not access to existing ES clusters. We will update the status again in 1 hour.

This incident was fully resolved yesterday at 5pm PST but we forgot to update the status page.

We have fixed all affected deployments and believe the impact to customers is resolved. We will continue monitoring for an hour.

We have started active remediation and believe it will take 2 hours to finish all affected deployments. We will update again in 2 hours or earlier.

We have identified an issue where customers may be seeing more frequent logouts or messages about invalid access tokens in Kibana. This is impacting deployments that have multiple Kibanas only. We are working on the remediation and will update again in an hour. If you run into this issue, reloading the page should resolve the issue.

The fix has been rolled out to all regions and customers should now be able to create BYOK deployments again.

We have identified the issue and have a fix in place for the first region. We are working to propagate the fix to the rest of the Azure regions. Once all regions have been addressed we will post a final update.

The Elastic Cloud Hosted service is experiencing issues with the creation of new BYOK (bring-your-own-key) deployments in Azure regions. This only affects users attempting to create a new BYOK deployment in Azure regions. Existing Azure BYOK and non-BYOK deployments are not impacted. The team is working on identifying the root case.