Dynatrace incident

Anomaly detection executions are degraded due to increased response times

Minor Resolved View vendor source →

Dynatrace experienced a minor incident on May 13, 2026 affecting Dynatrace Product and Dynatrace Product (Analyze-AWS-americas) and 1 more component, lasting 5h 15m. The incident has been resolved; the full update timeline is below.

Started
May 13, 2026, 12:45 PM UTC
Resolved
May 13, 2026, 06:01 PM UTC
Duration
5h 15m
Detected by Pingoru
May 13, 2026, 12:45 PM UTC

Affected components

Dynatrace ProductDynatrace Product (Analyze-AWS-americas)Dynatrace Product (Analyze-AWS-emea)Dynatrace Product (Analyze-Azure-americas)

Update timeline

  1. investigating May 13, 2026, 12:45 PM UTC

    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.

  2. identified May 13, 2026, 01:41 PM UTC

    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.

  3. monitoring May 13, 2026, 03:26 PM UTC

    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.