Looking for an update now? Check the current status, or follow Dynatrace for future changes.
Building verified history20 of 24 verified daily observations collected. A percentage will appear after the minimum coverage threshold is met.
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Recorded Daily Status (Last 54 Days)
Jul 22Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
25 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
July 2026
Potential Observability Impact During OpenShift Upgrade to Version 1.341
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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, ...
IBM MQ message processing issue affecting customer applications
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 guidan...
Mission Control connectivity issues for Managed deployments in Europe
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 functio...
Potential Impact to OneAgent Customers Running nginx on Alpine
minorSource not attested
Last archived state: investigating
View archived record details
investigating
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...
investigating
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".
F...
Inability to access to the Classic/Host Service setting page
Source not attested
Last archived state: resolved
View archived record details
resolved
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.
Potential Impact to OneAgent Customers Running nginx on Red Hat
minorSource not attested
Last archived state: investigating
View archived record details
investigating
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.
investigating
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, 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 ...
investigating
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-...
investigating
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 opt...
June 2026
Data ingest degradation in Azure West US (Arizona)
minorSource not attested
Last archived state: investigating
View archived record details
investigating
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.
monitoring
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.
monitoring
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.
monitoring
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.
May 2026
Instability affecting Dynatrace SaaS deployment Azure West Europe
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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.
investigating
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.
investigating
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.
investigating
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.
OneAgent version 1.337 may impact IBM MQ message processing for .NET applications
minorSource not attested
Last archived state: resolved
View archived record details
resolved
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 yo...
Log ingestion disruption on a subset of deployments
minorSource not attested
Last archived state: investigating
View archived record details
investigating
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.
investigating
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.
investigating
We are investigating an issue where log ingestion is affected on a limited number of deployments. 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.
