Dynatrace incident

Gen3 apps and queries impacted for environments in US-East-1

Minor Resolved View vendor source →

Dynatrace experienced a minor incident on October 9, 2026 affecting Dynatrace Product and Dynatrace Product (Analyze-AWS-americas), lasting 2d 20h. The incident has been resolved; the full update timeline is below.

Started
Oct 09, 2026, 05:42 PM UTC
Resolved
Oct 12, 2026, 02:36 PM UTC
Duration
2d 20h
Detected by Pingoru
Oct 09, 2026, 05:42 PM UTC

Affected components

Dynatrace ProductDynatrace Product (Analyze-AWS-americas)

Update timeline

  1. investigating Oct 09, 2026, 05:42 PM UTC

    We are aware of an issue affecting a limited number of customers using Gen3 apps. Impacted customers may experience errors, failures, or delays when running DQL queries or using Gen3 apps that rely on these queries. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may cause. We will provide another update within the next hour, or sooner if additional information becomes available.

  2. investigating Oct 09, 2026, 06:49 PM UTC

    We are continuing to investigate an issue affecting a limited number of customers using Gen3 apps. Impacted customers may experience errors, failures, or delays when running DQL queries or using Gen3 apps that rely on these queries. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may cause. We will provide another update within the next hour, or sooner if additional information becomes available.

  3. investigating Oct 09, 2026, 07:53 PM UTC

    We are continuing to investigate an issue affecting a limited number of customers using Gen3 apps. Impacted customers may experience errors, failures, or delays when running DQL queries or using Gen3 apps that rely on these queries. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may cause. We will provide another update within the next hour, or sooner if additional information becomes available.

  4. investigating Oct 09, 2026, 08:57 PM UTC

    We are continuing to test out mitigation strategies. Our teams are actively investigating the issue and working to restore normal service as quickly as possible. We apologize for any disruption this may have caused. We will provide further updates as more information becomes available.

  5. monitoring Oct 09, 2026, 09:42 PM UTC

    We have applied mitigation and we are seeing improvements. We will continue to monitor the situation closely over the weekend and provide a further update once more information is available. We appreciate your patience as we work to fully resolve this issue.

  6. monitoring Oct 10, 2026, 07:15 AM UTC

    Mitigation measures have produced the expected results, and all services are operating normally. We will continue to monitor closely over the weekend and share a further update if necessary. We apologize for the inconvenience and appreciate your patience.