Dynatrace incident

Multiple Google Synthetic Locations are not executing tests

Minor Resolved View vendor source →

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

Started
May 07, 2026, 03:39 PM UTC
Resolved
May 07, 2026, 08:55 PM UTC
Duration
5h 15m
Detected by Pingoru
May 07, 2026, 03:39 PM UTC

Affected components

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

Update timeline

  1. investigating May 07, 2026, 03:39 PM UTC

    We are investigating Synthetic locations running in the Google Cloud locations that are not currently executing tests. We will follow up here with updates as they become available.

  2. identified May 07, 2026, 04:35 PM UTC

    We have identified the root cause of this issue and are working toward mitigation which will allow Synthetic test execution to run as expected. We apologize for the inconvenience this has caused.

  3. monitoring May 07, 2026, 05:21 PM UTC

    The mitigation has successfully resolved the Synthetic test execution issues, and tests have returned to normal operation. We will continue monitoring closely over the next few hours before formally closing the incident. Thank you for your patience while we worked to resolve this issue.