Skip to main content
Dynatrace

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

Partial outage Lasted 0m · started · Dynatrace's page

Level
confirmed
Worst impact
Partial outage
Regions
us, us-east-1
Down Index
26of 100

What to do

  • Check whether you use Dynatrace in us, us-east-1. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

    Anything that failed between 2026-10-12 14:26 UTC and 2026-10-12 14:26 UTC may need a replay.
  • Subscribe to Dynatrace's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=dynatrace works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Dynatrace 1

  1. resolved

    October 9, 2026 5:42PM UTC Investigating - 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. October 9, 2026 6:49PM UTC Investigating - 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. October 9, 2026 7:53PM UTC Investigating - 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. October 9, 2026 8:57PM UTC Investigating - 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. October 9, 2026 9:42PM UTC Monitoring - 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. October 10, 2026 7:15AM UTC Monitoring - 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. October 12, 2026 2:26PM UTC Resolved - The issue affecting Gen3 apps and queries for our customers on US-East-1 has been resolved, and all services are operating normally. Thank you for your patience while we worked to resolve this issue.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-2b508eb520

Is Dynatrace still down?

No, this incident was resolved 2026-10-12 14:26 UTC. For Dynatrace's live state, see https://down.guide/dynatrace.

How long did it last?

0m, from 2026-10-12 14:26 UTC to 2026-10-12 14:26 UTC, by the times Dynatrace posted.

What was affected?

Dynatrace named in us, us-east-1.

What caused it?

Dynatrace hasn't published a root cause. If it does, it shows here.

Where does this come from?

Dynatrace's official status page, https://dynatrace.status.io, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.