Dynatrace Outage History

Started Jul 24, 2026, 07:15 PM UTC· resolved Jul 24, 2026, 07:36 PM UTC

1. identified Jul 24, 2026, 07:15 PM UTC

   We are currently experiencing a technical issue that may delay our ability to view updates submitted through our Customer Support Portal, including support cases, licensing requests, and other inquiries. Our team is actively working to resolve this as quickly as possible. If you have an urgent matter, please reach out to us directly via Dynatrace chat support so we can ensure your request is seen and addressed without delay. We appreciate your patience and will provide an update as soon as normal service is restored.

Read the full incident report →

Started Jul 17, 2026, 07:18 PM UTC· resolved Jul 20, 2026, 03:45 PM UTC

1. identified Jul 17, 2026, 07:18 PM UTC

   We have identified a potential issue affecting OpenShift observability when upgrading to OA 1.341. This may result in reduced or lost visibility into OpenShift environments, which could impact monitoring of production environments. Our team is aware of the issue and is actively working on a fix. We recommend that customers review this potential impact before proceeding with the upgrade and continue monitoring their OpenShift environments closely. If you have already upgraded to OA 1.341, please open up a support case so that our team can assist with reverting you back to the previous version, which is not affected by this issue.

2. identified Jul 18, 2026, 06:01 AM UTC

   Our team continues to actively work on a fix. In the meantime, we have published a community article with downgrade instructions to assist customers who may be affected by the OpenShift monitoring issue after upgrading to OneAgent version 1.341: https://community.dynatrace.com/t5/Troubleshooting/k8s-oc-Downgrading-OneAgent-in-Kubernetes-and-OpenShift-with-the/ta-p/302087 If you require assistance with the downgrade process, please open a support case and our team will assist you accordingly. We apologise for any inconvenience this issue may cause.

3. identified Jul 20, 2026, 09:17 AM UTC

   We have narrowed the scope of the issue and customers using application-only monitoring are not expected to be affected.​‌ While we continue to work on a fix, customers experiencing this issue can use the previously provided downgrade guidance or contact Dynatrace Support for assistance.​‌ We will provide further updates as they become available. We apologize for any inconvenience this issue may cause.

Read the full incident report →

Started Jul 16, 2026, 06:56 AM UTC· resolved Jul 16, 2026, 01:38 PM UTC

1. identified Jul 16, 2026, 06:56 AM UTC

   We have identified an issue in OneAgent .NET version 1.341 affecting IBM MQ tracing. In impacted environments, IBM MQ message processing may be disrupted, which can affect applications consuming IBM MQ messages. Our engineering teams have identified the root cause and are actively working on a fix to resolve this issue. A workaround is available for customers currently experiencing this issue. Customers requiring assistance are encouraged to open a Support case with Dynatrace for guidance. Further updates will be provided as progress is made. We apologize for the inconvenience and appreciate your patience and understanding as we work to resolve this issue

Read the full incident report →

Started Jul 15, 2026, 11:42 AM UTC· resolved Jul 15, 2026, 03:34 PM UTC

1. identified Jul 15, 2026, 11:42 AM UTC

   We have identified an issue affecting connectivity between some Managed deployments in Europe and the Mission Control service. As a result, product update downloads and the synchronization of changes may be delayed or unavailable. Our teams are actively working on mitigation and service restoration. We recommend monitoring the Dynatrace Status page for further updates. We apologize for the inconvenience. The affected managed deployments remain operational, and core observability functionality is not impacted.

2. monitoring Jul 15, 2026, 12:09 PM UTC

   A fix has been implemented and connectivity between Managed deployments and the Mission Control service has been restored. Product update downloads and change synchronization are operating normally. The affected Managed deployments remained operational throughout, and there was no impact on core observability functionality. We are monitoring the service to confirm continued stability. We apologize for the inconvenience.

Read the full incident report →

Started Jul 14, 2026, 11:10 AM UTC· resolved Jul 17, 2026, 10:11 AM UTC

1. identified Jul 14, 2026, 11:10 AM UTC

   We have identified that the Alpine Linux distribution of nginx 1.28.3 on Alpine Linux 3.22 and 3.23 introduces an issue when used together with Dynatrace OneAgent nginx instrumentation. Affected environments may experience HTTP 500 responses or missing monitoring data, including traces and Real User Monitoring. Available mitigations include upgrading to OneAgent version 1.337 or later, upgrading to an unaffected Alpine Linux version, or disabling the OneAgent feature "Nginx modules". For more details on affected configurations and available workarounds, please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Specific-Alpine-Linux-versions-introduce-a-compatibility-issue/ta-p/301869 We are working with the Alpine Linux maintainers to address the underlying issue and will provide updates as more information becomes available. We apologize for the inconvenience.

2. identified Jul 15, 2026, 11:50 AM UTC

   We continue to work on an issue affecting customers using the Alpine Linux distribution of nginx 1.28.3 on Alpine Linux 3.22 and 3.23 together with Dynatrace OneAgent nginx instrumentation. We have identified the root cause and provided a proposed fix to the Alpine Linux project. We are currently working with the maintainers as it progresses through their review process. In parallel, we continue to evaluate additional mitigation options. Available mitigations and affected configurations are described in our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Specific-Alpine-Linux-versions-introduce-a-compatibility-issue/ta-p/301869 We will continue to provide updates on this page as more information becomes available. We apologize for the inconvenience.

Read the full incident report →

Started Jul 08, 2026, 07:44 PM UTC· resolved Jul 10, 2026, 12:29 AM UTC

1. investigating Jul 08, 2026, 07:44 PM UTC

   We are investigating an issue affecting some customers’ ability to access the Classic Host/Service settings page. Our team is working to identify the cause and will provide updates as more information becomes available. We apologize for any inconvenience this may cause.

2. identified Jul 08, 2026, 08:29 PM UTC

   We have identified the root cause of the issue affecting some customers’ ability to access the Classic Host/Service settings page. Our team is actively working on a fix to resolve the issue as quickly as possible. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

3. identified Jul 09, 2026, 12:29 AM UTC

   We have developed a hotfix to resolve this issue which will be progressively rolled out once validated. We are currently validating the hotfix and associated deployment timeframes. A progress update will be provided at 02:30AM UTC 9 July. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

4. identified Jul 09, 2026, 02:30 AM UTC

   We have deployed a hotfix that is progressively rolling out to the affected Classic SaaS Deployments. The hotfix is expected to be applied to all impacted Classic SaaS deployments by approximately 14:00 UTC 9 July. A progress update will be provided at 07:00AM UTC 9 July. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

5. identified Jul 09, 2026, 05:42 AM UTC

   We have successfully deployed the hotfix to 70% of the affected Classic SaaS Deployments. The remaining deployments are expected to be completed by approximately 14:00 UTC 9 July. A progress update will be provided at 08:00AM UTC 9 July. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

6. identified Jul 09, 2026, 07:59 AM UTC

   We have successfully deployed the hotfix to 90% of the affected Classic SaaS deployments. The remaining deployments are currently in progress and are expected to be completed by approximately 14:00 UTC 9 July. We are actively monitoring the rollout and system stability. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

7. monitoring Jul 09, 2026, 04:05 PM UTC

   No new errors have been observed for a while as deployments are finishing. We're actively monitoring to confirm the issue is fully resolved. We apologize for the inconvenience and appreciate your continued patience. If you have any questions, please contact our support team.

Read the full incident report →

Started Jul 02, 2026, 11:58 AM UTC· resolved Jul 08, 2026, 03:19 PM UTC

1. identified Jul 02, 2026, 11:58 AM UTC

   We have identified an issue affecting customers running nginx with Dynatrace OneAgent in specific Red Hat environments, where requests may return HTTP 500 responses. The issue is limited to certain Red Hat nginx package versions and configurations, and may result in failures for all requests handled by impacted nginx instances. Affected nginx versions include 1.20 (latest RHEL 9.8 package), 1.24, and 1.26. Our teams are actively working on mitigation and evaluating available workaround options. For more details on affected configurations and available workarounds, please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Red-Hat-NGINX-package-introduces-a-regression-with-OneAgent/ta-p/301487 We will continue to provide updates on this page as more information becomes available. We apologize for the inconvenience.

2. identified Jul 02, 2026, 07:45 PM UTC

   We are actively working to resolve an issue that may affect customers using nginx with Dynatrace OneAgent in certain Red Hat environments. In some cases, this may result in HTTP 500 responses. Our teams are deploying a fix to address the issue and are continuing work toward full mitigation. Customers who are still experiencing impact can refer to our Community post for additional details about affected configurations and available workarounds: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Red-Hat-NGINX-package-introduces-a-regression-with-OneAgent/ta-p/301487 We apologize for any inconvenience and appreciate your patience as we work to fully resolve this issue.

3. identified Jul 03, 2026, 09:05 AM UTC

   We are actively working to resolve an issue affecting customers using nginx with Dynatrace OneAgent in certain Red Hat environments, which may result in HTTP 500 responses. As a mitigation, customers can upgrade to OneAgent version 1.339.70 or later, which prevents application from returning HTTP 500 responses. However, the lack of tracing still persists on those affected versions. The underlying issue in certain nginx packages provided by Red Hat still exists. We are actively working with Red Hat and continuing efforts toward a permanent resolution. For more details on affected configurations and available workarounds, please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Red-Hat-NGINX-package-introduces-a-regression-with-OneAgent/ta-p/301487 We will continue to provide updates on this page as more information becomes available. We apologize for the inconvenience

4. identified Jul 03, 2026, 02:06 PM UTC

   We have identified an additional workaround that can restore tracing functionality in affected environments. Details, implementation instructions, and validation information have been added to the Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Red-Hat-nginx-package-introduces-a-regression-with-OneAgent/ta-p/301487 We continue to work with Red Hat and will provide further updates as more information becomes available.

Read the full incident report →

Started Jun 22, 2026, 11:17 AM UTC· resolved Jun 22, 2026, 08:21 PM UTC

1. investigating Jun 22, 2026, 11:17 AM UTC

   We are currently investigating an issue affecting data ingestion. This is leading to reduced ingest capacity, delayed data availability, and, in some cases, temporary ingestion interruptions. Our teams are working to restore stable operations and normal ingest performance as quickly as possible. Please continue to monitor Dynatrace status.io for updates. We apologize for the inconvenience.

2. identified Jun 22, 2026, 11:38 AM UTC

   The cause of the data ingestion issue has been identified. Recovery is in progress and the situation is improving. Our teams are working to restore normal performance as quickly as possible. Please continue to monitor Dynatrace status.io for updates. We apologize for the inconvenience.

3. identified Jun 22, 2026, 12:03 PM UTC

   Data ingest continues to recover and the backlog is steadily decreasing. Full recovery is expected within approximately two hours, after which normal data ingestion will resume. We are closely monitoring the situation to ensure full restoration of normal operations. Please continue to monitor Dynatrace status.io for updates. We apologize for the inconvenience.

4. monitoring Jun 22, 2026, 04:30 PM UTC

   We can confirm that log ingestion has been fully restored across the affected deployments. We will monitor the stability 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.

Read the full incident report →

Started May 28, 2026, 10:50 AM UTC· resolved May 29, 2026, 01:03 PM UTC

1. investigating May 28, 2026, 10:50 AM UTC

   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.

2. identified May 28, 2026, 11:40 AM UTC

   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.

3. monitoring May 28, 2026, 12:23 PM UTC

   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.

4. identified May 28, 2026, 02:06 PM UTC

   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.

5. monitoring May 28, 2026, 03:32 PM UTC

   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.

6. monitoring May 28, 2026, 08:41 PM UTC

   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.

Read the full incident report →

Started May 20, 2026, 01:44 PM UTC· resolved May 21, 2026, 06:14 PM UTC

1. identified May 20, 2026, 01:44 PM UTC

   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.

2. identified May 20, 2026, 07:02 PM UTC

   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.

3. monitoring May 20, 2026, 08:58 PM UTC

   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.

Read the full incident report →

Started May 19, 2026, 08:15 AM UTC· resolved May 19, 2026, 01:58 PM UTC

1. investigating May 19, 2026, 08:15 AM UTC

   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.

2. identified May 19, 2026, 08:56 AM UTC

   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.

3. monitoring May 19, 2026, 10:21 AM UTC

   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.

Read the full incident report →

Started May 13, 2026, 12:45 PM UTC· resolved May 13, 2026, 06:01 PM UTC

1. investigating May 13, 2026, 12:45 PM UTC

   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.

2. identified May 13, 2026, 01:41 PM UTC

   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.

3. monitoring May 13, 2026, 03:26 PM UTC

   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.

Read the full incident report →

Started May 13, 2026, 02:27 AM UTC· resolved May 15, 2026, 08:13 AM UTC

1. investigating May 13, 2026, 02:27 AM UTC

   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.

2. identified May 13, 2026, 03:26 AM UTC

   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.

3. monitoring May 13, 2026, 06:50 AM UTC

   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.

4. monitoring May 13, 2026, 09:18 AM UTC

   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.

5. monitoring May 13, 2026, 07:11 PM UTC

   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.

6. monitoring May 14, 2026, 06:08 PM UTC

   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.

Read the full incident report →

Started May 08, 2026, 01:01 AM UTC· resolved May 11, 2026, 09:29 PM UTC

1. identified May 08, 2026, 01:01 AM UTC

   We've identified an issue of degradated data ingestion due to the AWS Amazon Elastic Compute Cloud (N. Virginia) operational issue in a single Availability Zone (use1-az4) in the US-EAST-1 Region. More details can be found: https://health.aws.amazon.com/health/status We are actively monitoring this incident and will update here as the situation changes.

2. identified May 08, 2026, 02:13 AM UTC

   We've observed significant improvements following the mitigation from AWS. We are actively monitoring this incident and will update here as the situation changes.

3. identified May 08, 2026, 09:27 AM UTC

   We are observing broad data ingestion issues that may result in missing or delayed data for customers. Intermittent API ingest requests may also return 500 errors due to elevated memory pressure on ActiveGates. The impact is currently observed in the US‑EAST‑1 region. We are actively working toward full stabilization and continue to closely monitor the situation. We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for further updates.

4. identified May 08, 2026, 11:02 AM UTC

   Recovery actions have been completed and data ingestion is now progressing. The platform is currently catching up on previously delayed ingest, and as a result, real‑time observability may take additional time to fully normalize. Additional capacity adjustments are being applied to accelerate processing and support faster recovery of data visibility. We continue to closely monitor the situation. We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for further updates.

5. identified May 08, 2026, 12:11 PM UTC

   Data ingestion has largely recovered and logs and metrics are ingesting normally. Some customers with high ingest volume may still observe delayed processing for spans, while other customers are seeing normal ingest across all data types. Additional recovery actions have been applied, and the remaining impact is limited to span processing as the system continues to catch up in approximately 2 hours. We are closely monitoring progress. We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for further updates.

6. identified May 08, 2026, 02:35 PM UTC

   We have identified that a limited set of metrics, logs, events, and user sessions are still experiencing ingestion issues, impacting a subset of customers. We are actively working on additional mitigation measures. We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for further updates.

7. monitoring May 08, 2026, 07:05 PM UTC

   Data ingestion has been restored across the affected environments, and systems are operating normally. We will continue to closely monitor the situation as AWS works toward fully resolving their incident. If you continue to experience any issues with data ingestion, please open a Support ticket, and our team will be ready to assist you promptly. Thank you for your patience and understanding while we worked to mitigate this issue.

8. monitoring May 11, 2026, 03:03 AM UTC

   AWS has resolved the operational issue that was delaying data ingestion for some customers in the US‑EAST‑1 region. Normal services have resumed and we are actively monitoring performance to ensure all services are stabilized. If you experience any issues with data ingestion, please open a support ticket, and our team will be ready to assist you promptly. Thank you for your patience and understanding while we work to resolve this issue.

Read the full incident report →

Started May 07, 2026, 03:39 PM UTC· resolved May 07, 2026, 08:55 PM UTC

1. investigating May 07, 2026, 03:39 PM UTC

   We are investigating Synthetic locations running in the Google Cloud locations that are not currently executing tests. We will follow up here with updates as they become available.

2. identified May 07, 2026, 04:35 PM UTC

   We have identified the root cause of this issue and are working toward mitigation which will allow Synthetic test execution to run as expected. We apologize for the inconvenience this has caused.

3. monitoring May 07, 2026, 05:21 PM UTC

   The mitigation has successfully resolved the Synthetic test execution issues, and tests have returned to normal operation. We will continue monitoring closely over the next few hours before formally closing the incident. Thank you for your patience while we worked to resolve this issue.

Read the full incident report →