- Level
- confirmed
- Worst impact
- Partial outage
- 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-31 08:20 UTC and 2026-10-31 08:20 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.
Root cause
Identified - Data gaps may possibly be observed in Azure EAST US (Virginia) due to delays in log and metrics ingestions.Read the postmortem
Updates from Dynatrace 1
- resolved
October 31, 2026 5:26AM UTC Identified - Data gaps may possibly be observed in Azure EAST US (Virginia) due to delays in log and metrics ingestions. No data loss at this stage. 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 31, 2026 6:07AM UTC Monitoring - We have applied mitigation efforts for the issue affecting the pipeline responsible for processing extracted metrics from logs, span metrics, and entities. 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 31, 2026 6:34AM UTC Monitoring - We have applied mitigation efforts for the issue affecting the pipeline responsible for processing extracted metrics from logs, span metrics, and entities. We are now seeing data flow as expected for the affected data types. There was no data lost stemming from this incident. 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 31, 2026 8:20AM UTC Resolved - The issue affecting the pipeline responsible for processing extracted metrics from logs, span metrics, and entities in Azure East US (Virginia) has been resolved. Data processing has returned to normal and our monitoring confirms that the service remains stable. We apologise for the disruption and any inconvenience this may have caused.
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-d58ba9d70a
Is Dynatrace still down?
No, this incident was resolved 2026-10-31 08:20 UTC. For Dynatrace's live state, see https://down.guide/dynatrace.
How long did it last?
0m, from 2026-10-31 08:20 UTC to 2026-10-31 08:20 UTC, by the times Dynatrace posted.
What was affected?
Dynatrace named in us.
What caused it?
Dynatrace wrote: "Identified - Data gaps may possibly be observed in Azure EAST US (Virginia) due to delays in log and metrics ingestions." The postmortem: https://status.io/pages/incident/546d8cb6af8407b6730000cb/6ae57c1c3dbbeb05d7621853
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.