Skip to main content
Dynatrace

Data Processing Issue Affecting Metrics and Events for US East

Degraded Lasted 0m · started · Dynatrace's page

Level
confirmed
Worst impact
Degraded
Regions
us

What to do

  • Check whether you use Dynatrace in us. 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-16 22:35 UTC and 2026-10-16 22:35 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 14, 2026 5:38PM UTC Investigating - We are aware of an issue affecting the pipeline responsible for processing extracted metrics from logs, span metrics, entities, and anomaly detection. Some customers may experience data drops for these affected data types. Our teams are actively working to mitigate the issue and reduce customer impact. We will provide the next update within the next hour, or sooner if new information becomes available. We apologize for the inconvenience and thank you for your patience. October 14, 2026 6:46PM UTC Monitoring - We have applied mitigation efforts for the issue affecting the pipeline responsible for processing extracted metrics from logs, span metrics, entities, and anomaly detection. We are now seeing data flow as expected for the affected data types. Our teams will continue to monitor the service closely to confirm ongoing stability and ensure customer impact remains mitigated. We will provide an update in the next two hours or sooner. October 14, 2026 9:28PM UTC Monitoring - We continue to see stability following the mitigation efforts applied for the issue affecting the pipeline responsible for processing extracted metrics from logs, span metrics, entities, and anomaly detection. Data continues to flow as expected for the affected data types. Our teams will continue to monitor the service closely for a period to confirm ongoing stability and ensure customer impact remains mitigated. We will provide the next update within the next 24 hours, or sooner if new information becomes available. October 15, 2026 8:18PM UTC Monitoring - Service remains stable following implementation of the fix, with data processing operating as expected across the affected services. We will continue to monitor closely to verify sustained stability and provide our next update within 24 hours, or sooner if there are material developments. If you are experiencing any remaining issues, please contact your support team for assistance. October 16, 2026 10:35PM UTC Resolved - The issue has been resolved. Service remains stable, and data processing is operating as expected across the affected services. We apologize for the inconvenience and thank you for your patience while we resolved 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-da3486b533

Is Dynatrace still down?

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

How long did it last?

0m, from 2026-10-16 22:35 UTC to 2026-10-16 22:35 UTC, by the times Dynatrace posted.

What was affected?

Dynatrace named in us.

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.