Dynatrace Outage History
Daily status observations, past incidents, and reported issue history for Dynatrace.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 43.5% | 23 | 13 |
| July 2026 | 35.5% | 31 | 20 |
| June 2026 | 96.7% | 30 | 1 |
| May 2026 | 57.1% | 7 | 3 |
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Daily Status (Last 91 Days)
May 25
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Monitoring Visibility Impacted for AWS Lambda Layers on Node.js 22
Started:
Process-AWS-americas
Process-AWS-emea
Process-AWS-asia-pacific
Dynatrace Product
resolved
We are aware of an issue resulting in a loss of monitoring visibility for Lambda functions on Node.js version 22. Our team is actively investigating this issue and are working towards mitigation.
We understand the importance of reliable monitoring and will provide the next update within the next four hours, or sooner if additional information becomes available.
Thank you for your patience and understanding.
Access to Dynatrace services is currently impacted in AWS US East
Started:
resolved
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.
Latency and Slower Response in East US Deployment
Started:
monitoring
We have implemented changes to address the increased latency and slower response times within the user interface that some customers in the East US deployment experienced.
We are currently observing normal performance and will continue monitoring the situation prior to resolving this incident.
If you experience further issues, please raise a support case.
monitoring
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.
monitoring
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.
monitoring
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.
monitoring
We are investigating an issue that may cause some customers located in East US Deployment to experience increased latency and slower response times within the user interface. Our teams are actively engaged and working toward a resolution.
We will provide an update within two hours or before if progress has been made.
We apologize for the inconvenience and thank you for your patience.
Event Triggers for Workflows are Impacted
Started:
resolved
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.
Cloud integration data ingestion issue
Started:
resolved
We are investigating an issue affecting metric ingestion from a subset of AWS and Azure integrations. As a result, some customers may observe incomplete metric data and gaps in monitoring results. In addition, certain topology-related data may be delayed.
Our teams are actively working to identify the cause and restore normal service.
We will provide further updates as they become available. We apologize for any inconvenience this issue may cause.
Potential delay in logs and metrics ingestion in AWS US east
Started:
investigating
We have mitigated an issue affecting the Dynatrace Platform production environment (AWS-US East). During this time, customers may have experienced processing delays mainly with logs.
Our teams are actively working to stabilize the environment, restore normal processing, and validate the scope of customer impact. We are closely monitoring service health and will provide additional updates as meaningful progress is made.
If you are experiencing any issue please open a support case.
AWS Lambda layer instrumentation on Node.js impacted on version 1.341
Started:
resolved
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.
July 2026
Access to Business Event Settings is Impacted
Started:
resolved
We are investigating an issue affecting access to the Platform BizEvents (Business Events) settings page in customer environments. As a result, some customers may be unable to create, modify, or disable BizEvents through the affected settings page: /ui/apps/dynatrace.settings/settings/bizevents. BizEvent processing is uninterrupted at this time.
Our teams are actively working to restore access and minimize customer impact. We apologize for the disruption and will provide additional upda...
Dynatrace Operator 1.10.x: Deployment Issue
Started:
monitoring
We have identified an issue that may prevent some customers from deploying Operator 1.10.1 on fresh deployments or upgrades where operator components have been deleted. In some cases, this may delay planned changes in production environments
While we work toward a resolution, we have published a Community post with workaround guidance for impacted customers. Please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Unable-to-deploy-Operator-1-10-1-on-fr...
Salesforce Support Case Technical Issues
Started:
investigating
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 ...
Potential Observability Impact During OpenShift Upgrade to Version 1.341
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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)
Started:
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
Started:
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
Started:
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
Started:
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.
Anomaly detection executions are degraded due to increased response times
Started:
investigating
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.
monitoring
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
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.
Potential delay in spans, logs and user events ingestion in AWS US east region
Started:
investigating
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.
monitoring
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
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
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
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
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.
AWS operational issue may impact some US deployments
Started:
investigating
AWS has resolved the operational issue that was delaying data ingestion for some customers in the US‑EAST‑1 region. Normal services have resumed and we are actively monitoring performance to ensure all services are stabilized.
If you experience any issues with data ingestion, please open a support ticket, and our team will be ready to assist you promptly.
Thank you for your patience and understanding while we work to resolve this issue.
investigating
Data ingestion has been restored across the affected environments, and systems are operating normally. We will continue to closely monitor the situation as AWS works toward fully resolving their incident.
If you continue to experience any issues with data ingestion, please open a Support ticket, and our team will be ready to assist you promptly.
Thank you for your patience and understanding while we worked to mitigate this issue.
monitoring
We have identified that a limited set of metrics, logs, events, and user sessions are still experiencing ingestion issues, impacting a subset of customers. We are actively working on additional mitigation measures.
We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for further updates.
monitoring
Data ingestion has largely recovered and logs and metrics are ingesting normally. Some customers with high ingest volume may still observe delayed processing for spans, while other customers are seeing normal ingest across all data types.
Additional recovery actions have been applied, and the remaining impact is limited to span processing as the system continues to catch up in approximately 2 hours. We are closely monitoring progress.
We apologize for the inconvenience and recommend mon...
monitoring
Recovery actions have been completed and data ingestion is now progressing. The platform is currently catching up on previously delayed ingest, and as a result, real‑time observability may take additional time to fully normalize.
Additional capacity adjustments are being applied to accelerate processing and support faster recovery of data visibility. We continue to closely monitor the situation.
We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for ...
monitoring
We are observing broad data ingestion issues that may result in missing or delayed data for customers. Intermittent API ingest requests may also return 500 errors due to elevated memory pressure on ActiveGates.
The impact is currently observed in the US‑EAST‑1 region. We are actively working toward full stabilization and continue to closely monitor the situation.
We apologize for the inconvenience and recommend monitoring the Dynatrace Status page for further updates.
monitoring
We've observed significant improvements following the mitigation from AWS.
We are actively monitoring this incident and will update here as the situation changes.
monitoring
We've identified an issue of degradated data ingestion due to the AWS Amazon Elastic Compute Cloud (N. Virginia) operational issue in a single Availability Zone (use1-az4) in the US-EAST-1 Region.
More details can be found: https://health.aws.amazon.com/health/status
We are actively monitoring this incident and will update here as the situation changes.
Multiple Google Synthetic Locations are not executing tests
Started:
resolved
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.
April 2026
Real User Monitoring on Grail sessions processing in OpenPipeline are impacted
Started:
resolved
We are investigating an issue with User Sessions processing through OpenPipeline. The data is being ingested, but post processing is affected. We will update with more information here.