Dynatrace Outage History

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.

Dynatrace's support ticket system (Zendesk) experienced a major outage lasting 2.7 hours, preventing users from logging in to access support services. The company worked with their provider to restore the system while directing users to call +1-844-900-3962 for immediate support needs. The login functionality was eventually restored after the provider resolved the underlying issue.

Dynatrace experienced elevated load on backend services in AWS London and Azure US East deployments, causing slower UI responsiveness and delays in alert processing. The issue was identified as a backend service overload problem and teams implemented mitigation steps to restore normal service levels. The incident lasted 5.4 hours and affected the SaaS platform's performance across these two specific regional deployments.

Dynatrace experienced a major incident where problem generation was impacted for customer tenants on one Azure SaaS deployment in the US East region. The service disruption lasted 32 minutes while the company investigated the reports. The incident has been resolved, though specific resolution details were not provided in the available updates.

Dynatrace synthetic tests in the AWS Bahrain location were degraded for 147.7 hours due to an ongoing AWS regional availability issue that prevented test execution and resulted in no data being collected. As the infrastructure problems persisted without a clear resolution timeline, Dynatrace disabled the Bahrain location for new synthetic test configurations and planned to disable all existing tests in that location. Users were advised to execute tests from alternate locations as a workaround during the extended outage.

Multiple customers experienced HTTP 500 errors when accessing their Dynatrace Platform Tenant UI in the US-East GCP deployment, with additional impacts to data ingestion and system accessibility. The incident lasted 2.2 hours, during which teams identified the root cause and applied mitigation efforts that restored functionality, though customers experienced intermittent service availability during the resolution process.