Dynatrace Outage History

We are aware of an issue impacting service access across multiple regions within the last hour. Some customers may experience intermittent errors when logging in or accessing services in the affected regions. Based on current information, data ingestion is not impacted. Mitigation steps have been implemented, including rerouting traffic away from the infrastructure experiencing issues, and we are observing positive indicators of recovery. Our teams are continuing to monitor service health closely to validate sustained improvement and overall stability. We will provide another update within the next 30 minutes, or sooner if there is a material change. We apologize for the disruption and appreciate your patience as we continue working to confirm full recovery.

We have identified an issue affecting Dynatrace services hosted in AWS US East. Users may experience errors in the Dynatrace UI, slower-than-normal performance, and missing or delayed alerts. We are working to mitigate the impact and restore normal service. Please continue to monitor Dynatrace Status for updates. We apologize for the inconvenience and will provide an update within the next two hours or sooner if we have more information to share.

We have identified the issue causing increased latency and slower response times within the user interface for some customers in the East US deployment. Our team is working to restore expected performance. We will provide the next update within four hours, or sooner if additional progress is available. We apologize for the disruption and appreciate your continued patience as we work to resolve this matter.

We have identified the issue causing increased latency and slower response times within the user interface for some customers in the East US deployment. We are currently implementing changes to restore expected performance. We will provide the next update at 01:30am UTC, or sooner if additional progress is available. We apologize for the disruption and appreciate your continued patience as we work to resolve this matter.

We have identified the issue causing increased latency and slower response times within the user interface for some customers in the East US deployment. We are continuing to implement changes to restore expected performance. We will provide the next update at 05:30am UTC, or sooner if additional progress is available. We apologize for the disruption and appreciate your continued patience as we work to resolve this matter.

We have identified an issue affecting Workflows functionality impacting event triggers for some customers. Our teams are actively investigating and working toward a fix. We will provide an update within the next two hours, or sooner when more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

We have identified an issue impacting the AWS Lambda layer on Node.js for version 1.341 which is missing a runtime configuration for the SQS/SNS instrumentation, We are currently working on a fix to publish to all environments. There will be a progress update here within the next 4 hours. We apologize for the inconvenience this has caused.

Our teams continue to work on finalizing the build and deploying it across all customer environments. We will share our next update within 4 hours, including the latest progress on the rollout. We appreciate your patience as we work to complete this effort.

We have commenced deploying a fix for the issue impacting the AWS Lambda layer on Node.js for version 1.341 which is missing a runtime configuration for the SQS/SNS instrumentation. A progress update will be provided at 04:00am UTC 5 August.

A fix has been deployed for the issue impacting the AWS Lambda layer on Node.js for version 1.341 which was missing a runtime configuration for the SQS/SNS instrumentation. The fix is nearing full deployment, and a status update will be provided once it is completed.

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.

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.

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.

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.

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

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.