Dynatrace incident

Dynatrace Operator 1.10.x: Deployment Issue

Minor Resolved View vendor source →

Dynatrace experienced a minor incident on July 24, 2026 affecting Dynatrace Product and Dynatrace Product (Process-AWS-americas) and 1 more component, lasting 2d 14h. The incident has been resolved; the full update timeline is below.

Started
Jul 24, 2026, 09:08 PM UTC
Resolved
Jul 27, 2026, 11:44 AM UTC
Duration
2d 14h
Detected by Pingoru
Jul 24, 2026, 09:08 PM UTC

Affected components

Dynatrace ProductDynatrace Product (Process-AWS-americas)Dynatrace Product (Process-AWS-emea)Dynatrace Product (Process-Azure-emea)Dynatrace Product (Process-GCP-emea)Dynatrace Product (Process-AWS-asia-pacific)Dynatrace Product (Process-Azure-americas)Dynatrace Product (Process-Azure-asia-pacific)Dynatrace Product (Process-GCP-americas)Dynatrace Product (Process-GCP-asia-pacific)

Update timeline

  1. investigating Jul 24, 2026, 09:08 PM UTC

    We have identified an issue that may prevent some customers from deploying Operator 1.10.1 on fresh deployments or upgrades where operator components have been deleted. In some cases, this may delay planned changes in production environments While we work toward a resolution, we have published a Community post with workaround guidance for impacted customers. Please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Unable-to-deploy-Operator-1-10-1-on-fresh-clusters-or-upgrades/ta-p/302391 We apologize for the inconvenience and appreciate your patience as we work to restore normal deployment functionality.