Dynatrace incident

IBM MQ message processing issue affecting customer applications

Dynatrace experienced a minor incident on July 16, 2026 affecting Dynatrace Product and Dynatrace Product (Process-AWS-americas) and 1 more component, lasting 6h 42m. The incident has been resolved; the full update timeline is below.

Started: Jul 16, 2026, 06:56 AM UTC
Resolved: Jul 16, 2026, 01:38 PM UTC
Duration: 6h 42m
Detected by Pingoru: Jul 16, 2026, 06:56 AM UTC

Affected components

Dynatrace ProductDynatrace Product (Process-AWS-americas)Dynatrace Product (Process-AWS-emea)Dynatrace Product (Process-Azure-emea)Dynatrace Product (Process-GCP-emea)Dynatrace Product (Process-AWS-asia-pacific)Dynatrace Product (Process-Azure-americas)Dynatrace Product (Process-Azure-asia-pacific)Dynatrace Product (Process-GCP-americas)Dynatrace Product (Process-GCP-asia-pacific)

Update timeline

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