User Session Export Issue for SaaS Environments

What to do

• Check whether your product depends on Dynatrace. 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-01 08:54 UTC and 2026-10-01 08:54 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 - We have identified the root cause of the issue affecting user session exports.

Updates from Dynatrace 1

1. resolvedOct 1, 2026, 8:54 AM UTC

   September 25, 2026 9:57PM UTC Investigating - We are aware of an issue affecting user session exports. Customers attempting an export may encounter the system notification, “Failed to export data: 500 Errors.” Our teams are actively working to mitigate the issue and restore normal functionality. Data Collection and Storage are not impacted as part of this situation. We continue to work toward a mitigation and full resolution. We apologize for the disruption and appreciate your patience. We will provide our next update within 24 hours or sooner if additional information becomes available. September 26, 2026 2:17PM UTC Identified - We have identified the root cause of the issue affecting user session exports. Customers attempting an export may continue to encounter the system notification, "Failed to export data: 500" errors. We are actively working on a fix to address the issue. Data Collection and Storage remain unaffected. We will provide our next update by 10:00 AM UTC on Monday, or sooner if additional information becomes available. We apologize for the disruption and appreciate your patience. September 28, 2026 10:13AM UTC Identified - We continue working on a fix for the issue affecting User Session Exports. Customers may continue to experience export failures resulting in HTTP 500 errors. Data Collection and Storage remain unaffected. We will provide our next update by 4:00 PM UTC or sooner if additional information becomes available. We apologize for the disruption and appreciate your patience. September 28, 2026 4:09PM UTC Identified - We are deploying the fix to SaaS environments addressing the issue affecting User Session Exports. This process will take time to complete. The fix will restore the ability to generate new exports. Customers may continue to experience export failures resulting in HTTP 500 errors. Data Collection and Storage remain unaffected by this issue. We will provide our next update by 9:00 PM UTC or sooner if additional information becomes available. We apologize for the disruption and appreciate your patience as we work to fully resolve the issue. September 28, 2026 8:22PM UTC Identified - Deployment of the fix to SaaS environments addressing the issue affecting User Session Exports progress is approximately 75% complete. We are monitoring the rollout as it continues across the remaining environments. Until deployment is fully completed, some customers may continue to experience export failures resulting in HTTP 500 errors. The fix will restore the ability to generate new exports once available in each environment. We will provide our next update by 3:00 AM UTC or sooner if additional information becomes available. We apologize for the disruption and appreciate your patience as we work toward full resolution. September 29, 2026 2:51AM UTC Identified - Deployment of the fix to address the issue affecting User Session Exports is approximately 80% complete. This will restore the ability to generate new exports once available in each environment. Our R&D team is actively working to remove a blocker that is preventing deployment of the fix to the remaining environments. Some customers may continue to experience export failures resulting in HTTP 500 errors until the fix is fully deployed. We will provide our next update by 07:00 AM UTC or sooner if additional information becomes available. We apologize for the disruption and appreciate your patience as we work towards full resolution. September 29, 2026 7:13AM UTC Identified - The fix for the issue affecting User Session Exports is now fully deployed across all AWS-hosted SaaS environments. Rollout continues across Azure and GCP. A separate issue affecting the deployment process in a subset of those environments has been resolved, and rollout there is progressing. Environments that have not yet received the update may continue to see export failures returning HTTP 500 errors. Data collection and storage remain unaffected. Our next u

   provider

Corrections

None so far.

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