Dynatrace Outage History
8 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Dynatrace Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Aug 29, 2026 | Planned Maintenance affecting Authentication and Identity Management ServicesScheduled Maintenance | 1h 0m | Scheduled |
| Aug 20, 2026 | Monitoring Visibility Impacted for AWS Lambda Layers on Node.js 22We 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… | 84h 45m | Resolved |
| Aug 13, 2026 | Access to Dynatrace services is currently impacted in AWS US EastWe 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… | 1h 51m | Resolved |
| Aug 12, 2026 | Latency and Slower Response in East US DeploymentWe 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… | 17h 4m | Resolved |
| Aug 12, 2026 | Event Triggers for Workflows are ImpactedWe 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… | 1h 54m | Resolved |
| Aug 11, 2026 | Cloud integration data ingestion issueWe 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… | 4h 38m | Resolved |
| Aug 10, 2026 | Dynatrace Synthetic | Database maintenanceScheduled Maintenance | 4h 0m | Scheduled |
| Aug 7, 2026 | Potential delay in logs and metrics ingestion in AWS US eastWe 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… | 61h 33m | Resolved |
How to Read This Dynatrace Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Dynatrace acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Dynatrace outage in this window ran 3d 12h, against a mean recovery of 22h 6m. If you depend on Dynatrace in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.