Is Dynatrace Down?

We are aware of an issue affecting a limited number of customers using Gen3 apps. Impacted customers may experience errors, failures, or delays when running DQL queries or using Gen3 apps that rely on these queries. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may cause. We will provide another update within the next hour, or sooner if additional information becomes available. --- [2026-10-09T18:49:35.414Z] (300) We are continuing to investigate an issue affecting a limited number of customers using Gen3 apps. Impacted customers may experience errors, failures, or delays when running DQL queries or using Gen3 apps that rely on these queries. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may cause. We will provide another update within the next hour, or sooner if additional information becomes available. --- [2026-10-09T19:53:27.732Z] (300) We are continuing to investigate an issue affecting a limited number of customers using Gen3 apps. Impacted customers may experience errors, failures, or delays when running DQL queries or using Gen3 apps that rely on these queries. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may cause. We will provide another update within the next hour, or sooner if additional information becomes available. --- [2026-10-09T20:57:18.662Z] (300) We are continuing to test out mitigation strategies. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may have caused. We will provide further updates as more information becomes available. --- [2026-10-09T21:42:29.545Z] (300) We have applied mitigation and we are seeing improvements. We will continue to monitor the situation closely over the weekend and provide a further update once more information is available. We appreciate your patience as we work to fully resolve this issue. --- [2026-10-10T07:15:08.208Z] (100) Mitigation measures have produced the expected results, and all services are operating normally. We will continue to monitor closely over the weekend and share a further update if necessary. We apologize for the inconvenience and appreciate your patience.

We are aware of an issue affecting customers who have upgraded to OneAgent version 1.347. The issue is due to an emergent incompatibility with Oracle, customers may experience issues running the Orabase command-line interface (CLI) tool. Out of an abundance of caution, we recommend that customers running Orbase CLI tool do not upgrade to OneAgent 1.347 until the incompatibility has been resolved. If you have already upgraded and are experiencing impact, we recommend downgrading to a OneAgent version earlier than 1.347 until resolved. We understand the potential disruption this may cause and appreciate your patience as we work to resolve this issue. We will provide another update within the next four hours, or sooner if additional information becomes available. --- [2026-10-07T20:00:58.851Z] (400) We are actively addressing an issue affecting customers who upgraded to OneAgent version 1.347. The issue stems from an emergent incompatibility with Oracle and may impact customers using the Orabase command-line interface (CLI) tool. As a precaution, we continue to recommend that customers using the Orabase CLI tool do not upgrade to OneAgent 1.347 until the incompatibility is resolved. Customers already experiencing impact should downgrade to a OneAgent version earlier than 1.347. A mitigating OneAgent version is currently being rolled out. We will provide the next update within two hours, or sooner if new information becomes available. --- [2026-10-07T22:13:21.303Z] (400) We identified an issue affecting some customers who upgraded to OneAgent version 1.347. Our investigation determined that the issue is related to an incompatibility with Oracle and may impact customers using the Orabase command-line interface (CLI) tool. To address this, a new version of OneAgent has been rolled out and is expected to mitigate the issue for affected customers. We encourage any customer who believes they may be impacted to update to the latest version of OneAgent. Since this version has been released, our teams will continue monitoring the fix to confirm it is working as expected. If the issue persists, please contact your support team. Our support teams are available to assist and will work with you to resolve any remaining impact. We will provide the next update within four hours, or sooner if new information becomes available. --- [2026-10-08T02:03:29.407Z] (400) We are currently rolling out a new version of OneAgent to address an incompatibility with Oracle that may impact customers using the Orabase command-line interface (CLI) tool. The new version has been successfully deployed to all AWS environments, and we are working to complete the roll out for a small number of Azure and GCP environments. Once available, we encourage any customer who believes they may be impacted to update to the latest version of OneAgent. We will provide the next update at 05:00 AM UTC, or sooner if new information becomes available. --- [2026-10-08T05:19:22.490Z] (400) We are continuing to work on completing the roll out of the new OneAgent version for the remaining Azure and GCP environments. The new version is available on all AWS environments. We will provide the next update by 09:00 AM UTC, or sooner if new information becomes available. --- [2026-10-08T09:10:36.755Z] (400) We have completed the rollout of the updated OneAgent version to all AWS environments. We expect the updated version for the remaining Azure and GCP environments to become available early next week. Customers on Azure and GCP environments who are using the Orabase command-line interface (CLI) tool should pause upgrading to OneAgent version 1.347 until the updated version becomes available. Customers already experiencing impact may use a OneAgent version earlier than 1.347 as a workaround. As the rollout timeline for the remaining Azure and GCP environments is longer than initially anticipated, we will provide the next update by Monday, 8:00 AM UTC, or sooner if new information becomes available.

We are investigating an issue affecting environments on GCP in the US-East region. Customers may experience delays in data ingestion or issues with data processing. We are working to restore normal processing as quickly as possible. We will provide another update by 3:30 PM UTC, or sooner if further information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue. --- [2026-10-01T14:09:04.249Z] (400) We are investigating an issue affecting services in the GCP US-East region. Customers may currently experience delayed telemetry data ingestion. As a result, some telemetry may not be fully reflected in Dynatrace services, which may lead to gaps in dashboards, delayed problem detection, or event-based workflows not executing as expected. We are working to restore normal processing as quickly as possible and will provide another update by 4:00 PM UTC, or sooner if further information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue. --- [2026-10-01T15:07:32.818Z] (100) The issue affecting services in the GCP US-East region has been mitigated. The root cause points to a service disruption on our cloud provider’s side, which has since subsided. Telemetry ingestion has recovered, and delayed log data is now being processed. Customers should begin to see recovery across related Dynatrace services as processing continues to stabilize. Our teams are monitoring for continued stability and will provide another update by 6:00 PM UTC, or sooner if further information becomes available. We apologize for the disruption and appreciate your continued patience as recovery progresses. --- [2026-10-01T18:03:21.194Z] (100) We continue to see positive progress following the mitigation of the service disruption affecting the GCP US-East region.  Telemetry ingestion has recovered, and delayed log data is processing as expected, with related Dynatrace services continuing to stabilize. Our teams will remain actively engaged and continue monitoring to confirm sustained stability. We will provide another update by 9:00PM UTC, or sooner if there are any material changes.  We appreciate your continued patience and partnership as recovery progresses.