Dynatrace SaaS environments experienced a 131-hour outage affecting user session exports, where customers received "Failed to export data: 500 Errors" when attempting exports. The root cause was identified and a fix was progressively rolled out across AWS, Azure, and GCP environments, with a deployment blocker on a subset of environments causing additional delays. The fix was fully deployed to all impacted environments by October 1, 2026, with data collection and storage unaffected throughout the incident.
Trusted by 1,000+ teams
Stop finding out about outages from your users. Monitor 6,320+ cloud services and get alerted the second something breaks.
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.
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.
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.
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.
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.
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.
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 update will be provided by 1:00 PM UTC, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience as we work toward full resolution.
The fix for the issue affecting User Session Exports is fully deployed across all AWS-hosted SaaS environments. Rollout continues across Azure and GCP. We are making good progress, and deployment across the remaining environments is nearing completion.
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 update will be provided by 4:00 PM UTC, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience as we work toward full resolution.
The fix for the issue affecting User Session Exports is fully deployed across all AWS-hosted SaaS environments. Rollout across Azure and GCP environments is continuing steadily, with good progress being made. We remain focused on completing deployment to the remaining environments as quickly as possible.
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 update will be provided by 8:00 PM UTC, or sooner if there is significant progress. We apologize for the disruption and appreciate your patience as we work toward full resolution.
The fix for the issue affecting User Session Exports has now been deployed to 99% of impacted environments. We anticipate completing the remaining rollout and resolving the issue soon.
If you believe your environment is still affected, please contact your support team for assistance. Data collection and storage remain unaffected.
We continue to closely monitor the rollout and will provide another update 11pm UTC, or sooner if additional information becomes available. We apologize for the disruption and appreciate your continued patience.
The fix for the issue affecting User Session Exports has been deployed to 99% of impacted environments.
If you believe your environment is still affected, please contact your support team for assistance. Data collection and storage remain unaffected.
We are actively monitoring the remaining rollout and will provide another update 03:00 am UTC, or sooner if additional information becomes available. We apologize for the disruption and appreciate your continued patience.
The fix for the issue affecting User Session Exports has been deployed to 99% of impacted environments.
If you believe your environment is still affected, please contact your support team for assistance. Data collection and storage remain unaffected.
We are actively monitoring the remaining rollout and will provide another update at 07:00 am UTC, or sooner if additional information becomes available. We apologize for the disruption and appreciate your continued patience.
The fix for the issue affecting User Session Exports has been deployed to 99% of impacted environments.
If you believe your environment is still affected, please contact your support team for assistance. Data collection and storage remain unaffected.
We are monitoring the remaining rollout and will provide another update at 11:00 AM UTC, or sooner if additional information becomes available. We apologize for the disruption and appreciate your continued patience.
The fix for the issue affecting User Session Exports has been deployed to 99% of impacted environments.
If you believe your environment is still affected, please contact your support team for assistance. Data collection and storage remain unaffected.
With deployment completed in the vast majority of environments and remaining progress expected to occur gradually, we will transition to an eight-hour update cadence. Our next update will be provided by 07:00 PM UTC, or sooner if significant new information becomes available.
We apologize for the disruption and appreciate your continued patience.
The fix for the issue affecting User Session Exports has now been deployed to 99% of impacted environments. As a result, the majority of customers should no longer be experiencing impact from this issue.
Customers who believe their environment remains affected are encouraged to contact their Support team for further assistance. Data collection and storage remain unaffected.
Given the broad completion of deployment and the expectation that remaining progress will continue gradually, we will move to an eight-hour update cadence. Our next update will be provided by 3:00 AM UTC, or sooner if significant new information becomes available. We apologize for the disruption and appreciate your continued patience.
The fix for the issue affecting User Session Exports has now been deployed to all impacted environments.
If you experience further issues or need assistance recovering user session exports for the impacted period, please raise a support case.
We are now in a state of monitoring and will provide our next update by 13:00PM UTC, or sooner if further information becomes available.
We apologize for the disruption this may have caused while we addressed this issue.
With IsDown, you can monitor all your critical services' official status pages from one centralized dashboard and receive instant alerts the moment an outage is detected. Say goodbye to constantly checking multiple sites for updates and stay ahead of outages with IsDown.
Start free trialNo credit card required · Cancel anytime · 6320 services available
Integrations with