Instability affecting Dynatrace SaaS deployment Azure West Europe
Affected: Dynatrace ProductDynatrace Product (Process-Azure-emea)Dynatrace Product (Analyze-Azure-emea)Dynatrace Product (Automate-Azure-emea)
Dynatrace Outage History
Dynatrace is up right nowDynatrace had 7 outages in the last 2 years totaling 217h 12m of downtime — averaging 0.3 incidents per month.
There were 7 Dynatrace outages since May 7, 2026 totaling 217h 12m of downtime. Each is summarised below — incident details, duration, and resolution information.
OneAgent version 1.337 may impact IBM MQ message processing for .NET applications
Affected: 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)
Timeline · 3 updates
- 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.
- 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.
- 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.
Log ingestion disruption on a subset of deployments
Affected: Dynatrace ProductDynatrace Product (Process-AWS-americas)Dynatrace Product (Process-AWS-emea)Dynatrace Product (Process-AWS-asia-pacific)
Timeline · 3 updates
- 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.
- 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.
- 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.
Anomaly detection executions are degraded due to increased response times
Affected: Dynatrace ProductDynatrace Product (Analyze-AWS-americas)Dynatrace Product (Analyze-AWS-emea)Dynatrace Product (Analyze-Azure-americas)
Timeline · 3 updates
- 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.
- 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.
- 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.
Potential delay in spans, logs and user events ingestion in AWS US east region
Affected: Dynatrace ProductDynatrace Product (Process-AWS-americas)
Timeline · 6 updates
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
AWS operational issue may impact some US deployments
Affected: Dynatrace ProductDynatrace Product (Process-AWS-americas)Dynatrace Product (Analyze-AWS-americas)Dynatrace Product (Automate-AWS-americas)
Timeline · 8 updates
Multiple Google Synthetic Locations are not executing tests
Affected: Dynatrace ProductDynatrace Product (Automate-AWS-americas)Dynatrace Product (Automate-AWS-emea)Dynatrace Product (Automate-AWS-asia-pacific)Dynatrace Product (Automate-Azure-americas)Dynatrace Product (Automate-Azure-emea)Dynatrace Product (Automate-Azure-asia-pacific)Dynatrace Product (Automate-GCP-americas)Dynatrace Product (Automate-GCP-emea)Dynatrace Product (Automate-GCP-asia-pacific)
Timeline · 3 updates
- 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.
- 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.
- 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.