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.
August 2026
Monitoring Visibility Impacted for AWS Lambda Layers on Node.js 22
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
minorSource not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
minorSource not attested
Last archived state: investigating
View archived record details
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
minorSource not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: resolved
View archived record details
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
Source not attested
Last archived state: monitoring
View archived record details
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
minorSource not attested
Last archived state: investigating
View archived record details
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 ...
