Dynatrace Outage History

Dynatrace experienced instability in their SaaS deployment in Azure West Europe for 1.6 hours, causing degraded access to the user interface and APIs along with delays and interruptions in data ingestion. Customers also experienced login issues during the incident. The service teams worked on mitigation efforts to stabilize the deployment and resolve the connectivity problems.

OneAgent for .NET version 1.337 caused message processing failures in IBM MQ environments, preventing downstream applications from properly processing incoming messages and disrupting business operations. The incident lasted 7.3 hours with Dynatrace recommending customers avoid upgrading to version 1.337 until a fix was implemented. A manual mitigation was made available through support tickets while the team worked on a permanent resolution.

Dynatrace experienced a log ingestion disruption affecting a limited number of deployments, where some log records were not being ingested as expected. The issue lasted 5.6 hours before log ingestion was fully restored across all affected deployments. The service was monitored for stability following the resolution to ensure complete recovery.

Dynatrace experienced degraded anomaly detection executions for 2.7 hours due to increased response times in a dependent service. The issue caused anomaly detectors to not run as expected or be temporarily backed off. The root cause was identified and mitigation work was implemented to restore normal execution behavior.

Dynatrace experienced a 39.7-hour incident causing ingestion delays for spans, logs, and user events in the AWS US East region. The service identified and addressed the root cause, implementing recovery actions that restored real-time data processing for new incoming data while the platform worked through the backlog of previously delayed data. The incident was resolved with normal ingestion restored, though some residual delays persisted as the system fully processed the accumulated backlog.

An AWS operational issue in the US-EAST-1 region caused degraded data ingestion for Dynatrace US deployments, resulting in missing or delayed data, intermittent API errors, and processing delays across metrics, logs, events, and user sessions. The incident lasted 18 hours with recovery actions progressively restoring data ingestion, though some high-volume customers continued experiencing delayed span processing and a limited subset still faced ingestion issues for certain data types. Full resolution was achieved through capacity adjustments and system recovery measures that allowed the platform to catch up on previously delayed data.

Dynatrace experienced an outage where multiple Google Cloud synthetic monitoring locations stopped executing tests for 1.7 hours. The service identified the root cause and worked on mitigation to restore normal synthetic test execution. The incident was classified as minor severity.

Dynatrace experienced an issue with Real User Monitoring sessions processing through OpenPipeline, where data ingestion continued normally but post-processing was impacted. The incident affected user session data analysis and monitoring capabilities for 1.3 hours. The root cause was identified and mitigation steps were implemented to resolve the processing issue.

Dynatrace experienced SSO authentication issues that prevented users from logging into the platform, though existing active sessions remained functional for up to one hour and the core product continued operating normally. The incident lasted 1.6 hours before a mitigation was applied and access was restored. Teams confirmed recovery through customer feedback and continued monitoring while working toward a complete resolution.

Dynatrace experienced increased load on the data processing pipeline in their Azure Europe (Switzerland) deployment, causing delays in log ingestion for some customers. The incident was classified as minor and lasted 33 minutes. Teams actively analyzed the situation and took steps to stabilize the deployment, resolving the ingestion delays.