Is Dynatrace down?

We are currently investigating an issue where a Dynatrace SaaS deployment in Azure West Europe is experiencing instability. This may result in degraded access to the user interface and APIs, as well as delays or interruptions in data ingestion. Our teams are actively working to identify the cause and stabilize the service. We apologize for the inconvenience and recommend monitoring this page for further updates.

We are still working on mitigation efforts to stabilize the Dynatrace SaaS deployment in Azure West Europe. Customers may continue to experience issues with login as well as delays or interruptions in data ingestion. Our teams remain actively engaged in stabilizing the service, and we will provide another update as progress continues. We apologize for the inconvenience and recommend monitoring this page for further updates.

We have applied mitigation steps and are observing recovery of the Dynatrace SaaS deployment in Azure West Europe. Service stability has improved, login functionality and data ingestion are operating at normal levels again. Our teams continue to closely monitor the environment to ensure sustained stability and will provide another update as new information becomes available. We apologize for the inconvenience and recommend monitoring this page for further updates.

We are investigating a recurrence of instability affecting the Dynatrace SaaS deployment in Azure West Europe. Following earlier recovery, service degradation has been observed again and customers may experience issues with login, UI and API access, as well as delays or interruptions in data ingestion. Our teams are actively working to stabilize the deployment and mitigate the renewed impact. We apologize for the inconvenience and recommend monitoring this page for further updates.

We have restabilized the Dynatrace SaaS deployment in Azure West Europe. Service performance has improved, and both login functionality and data ingestion are now operating at normal levels. Our teams continue to closely monitor the environment to ensure sustained stability and will share additional updates as new information becomes available.  We apologize for the disruption and appreciate your patience. Please continue to monitor this page for the latest updates.

We can confirm that the Dynatrace SaaS deployment in Azure West Europe is currently stable and operating normally. Our teams will continue to closely monitor the deployment overnight to ensure ongoing stability. Please return here tomorrow for our next update. We sincerely apologize for the inconvenience and appreciate your patience as we work to ensure full mitigation and sustained service stability.

We are currently investigating an issue related to OneAgent for .NET version 1.337, which is impacting message processing in environments using IBM MQ. As a result, some downstream applications are unable to properly process incoming messages, which may lead to disruptions in normal business operations. Our team is actively working to identify and resolve the problem, and we will provide updates as more information becomes available. At the time we recommend not to update to 1.337 if you have agents in this scenario. Please follow here for updates.

We are actively working on a fix for the issue affecting OneAgent for .NET version 1.337. Mitigation will take some time, and we will continue to provide updates here as progress is made. We do have a manual mitigation for those customers directly impacted. Please open a Support ticket and our team can assist you with this. In the meantime, we recommend that customers using IBM MQ do not upgrade to version 1.337 until mitigation has been completed. We apologize for the inconvenience and appreciate your patience and understanding as we work to resolve this issue.

We have deployed a fix for the issue affecting OneAgent for .NET version 1.337 and are continuing to monitor the situation closely. Customers may proceed with upgrading to version 1.337.51.20260520. If you continue to experience this issue after the upgrade, please open a support ticket for further assistance.

We are investigating an issue where log ingestion is affected on a limited number of clusters. Early indications suggest that some log records are not being ingested as expected. The scope and impact are still being assessed. We apologize for the inconvenience and will provide updates as more information becomes available.

We have identified the issue that is impacting log ingestion on a limited number of deployments. Remediation and impact analysis are currently in progress, we will update as new information becomes available.

We can confirm that log ingestion has been fully restored across the affected deployments. We will monitor the stability over the next couple of hours before resolving this incident. If you notice any issues with log ingestion, please raise a Support ticket and our team will assist you promptly. Thank you for your patience and understanding while we worked to resolve this issue.

We are currently investigating an issue causing a degradation in Anomaly Detection executions. This may result in Anomaly Detectors not running as expected or being temporarily backed off. The behavior is linked to increased response times in a dependent service, and our teams are actively investigating the situation. We apologize for the inconvenience and will provide updates as more information becomes available.

We have identified the root cause of the Anomaly Detection execution degradation. Mitigation work is currently in progress to restore normal execution behavior. We will continue to provide updates as we progress in remediating this issue.

We have deployed a mitigation and are observing improvements across affected environments. Our teams will continue to closely monitor stability over the next several hours. We will provide additional updates if there are any changes. We sincerely apologize for the inconvenience and appreciate your patience.

We are currently investigating an issue causing ingestion delay in spans, logs and user events in AWS US east region. Our teams are actively analyzing the situation and working to restore normal service levels as quickly as possible. We apologize for the inconvenience and recommend monitoring this status page for further updates.

We have identified the root cause of this issue and implemented recovery actions. The platform is currently catching up on previously delayed ingest, and we expect some additional time to fully normalize real‑time observability. We apologize for the inconvenience and appreciate your patience. Please reach out to support team in case you have any further questions.

We continue to see positive progress following recovery actions taken earlier. The platform is actively processing previously delayed ingest, and system buffers are steadily draining. While some customers may still observe delayed real‑time data, overall processing is stabilizing as recovery continues. Our teams are actively monitoring the situation to ensure full normalization. We appreciate your patience and will provide further updates as progress continues.

Recovery actions remain in place and the platform is operating with restored real‑time data processing. New incoming data is being processed normally, while previously queued data continues to catch up. As a result, some data types may still appear with delay until the backlog is fully cleared. The situation is improving and our teams continue to monitor recovery closely. We will revert to normal status once ingest backlog processing has fully completed. Thank you for your patience.

We can confirm that new and ongoing data ingestion has been restored. Our teams will continue to monitor the backlog as data processing catches up. Because this process will take some time to complete, please check back here tomorrow for an update. We apologize for the inconvenience and appreciate your patience as we continue working towards a resolution.

We are seeing positive progress with data ingestion, and many tenants are no longer experiencing impact. However, to ensure full resolution of this issue, our team will continue monitoring the remaining affected tenants as they work through the backlog. We sincerely apologize for the inconvenience and appreciate your continued patience as we complete our remediation efforts. Please check here for updates.