Dynatrace incident

Inability to access to the Classic/Host Service setting page

Minor Resolved View vendor source →

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

Started
Jul 08, 2026, 07:44 PM UTC
Resolved
Jul 10, 2026, 12:29 AM UTC
Duration
1d 4h
Detected by Pingoru
Jul 08, 2026, 07:44 PM UTC

Affected components

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

Update timeline

  1. investigating Jul 08, 2026, 07:44 PM UTC

    We are investigating an issue affecting some customers’ ability to access the Classic Host/Service settings page. Our team is working to identify the cause and will provide updates as more information becomes available. We apologize for any inconvenience this may cause.

  2. identified Jul 08, 2026, 08:29 PM UTC

    We have identified the root cause of the issue affecting some customers’ ability to access the Classic Host/Service settings page. Our team is actively working on a fix to resolve the issue as quickly as possible. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

  3. identified Jul 09, 2026, 12:29 AM UTC

    We have developed a hotfix to resolve this issue which will be progressively rolled out once validated. We are currently validating the hotfix and associated deployment timeframes. A progress update will be provided at 02:30AM UTC 9 July. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

  4. identified Jul 09, 2026, 02:30 AM UTC

    We have deployed a hotfix that is progressively rolling out to the affected Classic SaaS Deployments. The hotfix is expected to be applied to all impacted Classic SaaS deployments by approximately 14:00 UTC 9 July. A progress update will be provided at 07:00AM UTC 9 July. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

  5. identified Jul 09, 2026, 05:42 AM UTC

    We have successfully deployed the hotfix to 70% of the affected Classic SaaS Deployments. The remaining deployments are expected to be completed by approximately 14:00 UTC 9 July. A progress update will be provided at 08:00AM UTC 9 July. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

  6. identified Jul 09, 2026, 07:59 AM UTC

    We have successfully deployed the hotfix to 90% of the affected Classic SaaS deployments. The remaining deployments are currently in progress and are expected to be completed by approximately 14:00 UTC 9 July. We are actively monitoring the rollout and system stability. We apologize for the inconvenience and appreciate your patience. If you have any questions, please contact our support team.

  7. monitoring Jul 09, 2026, 04:05 PM UTC

    No new errors have been observed for a while as deployments are finishing. We're actively monitoring to confirm the issue is fully resolved. We apologize for the inconvenience and appreciate your continued patience. If you have any questions, please contact our support team.