Dynatrace Outage History

Started Oct 16, 2026, 04:01 PM UTC· resolved Oct 21, 2026, 08:22 PM UTC

1. investigating Oct 16, 2026, 04:01 PM UTC

   We are aware and actively working to mitigate an issue affecting access to our support portal. Some customers may be unable to sign in or may encounter error messages during login. For immediate assistance with a critical issue, please call our support hotline at 1-844-900-3962 if you are unable to access the portal. We will provide an update within the next hour, or sooner if more information becomes available. We apologize for the disruption and appreciate your patience as we work to restore access.

2. investigating Oct 16, 2026, 04:59 PM UTC

   We continue to investigate login issues affecting some customers accessing our support portal. Affected customers may be unable to sign in or may encounter error messages during login. For any critical issues, please call our support hotline at 1-844-900-3962 for immediate assistance rather than relying on portal access while the investigation continues. We will provide an update within the next two hours, or sooner if more information becomes available.

3. investigating Oct 16, 2026, 06:51 PM UTC

   Our investigation into the support portal access issues remains ongoing. Some customers may experience sign-in failures or receive error messages when attempting to log in. Our teams are actively working on a fix. If you need assistance with a critical issue, please contact our support hotline directly at 1-844-900-3962 for immediate support while portal login issues persist. Our next update will be shared within three hours, or earlier if additional information becomes available.

4. monitoring Oct 16, 2026, 10:24 PM UTC

   We have implemented a fix for the support portal login issues, and customers should now be able to sign in successfully. If you continue to have trouble accessing the portal and need assistance with a critical issue, please call our support hotline at 1-844-900-3962 for immediate support. Our teams will continue monitoring for stability throughout the weekend, and we will provide an update on Monday. Thank you for your patience while we worked to restore access.

5. monitoring Oct 19, 2026, 09:30 PM UTC

   While we have applied a fix to address the support portal login issues, our investigation identified additional issues affecting some customers’ ability to log in. Our teams are actively working to resolve these issues. If you continue to have trouble accessing the portal and need assistance with a critical issue, please call our support hotline at 1-844-900-3962 for immediate support. We will provide our next update on Wednesday. We apologize for the continued inconvenience and appreciate your patience as we work to restore reliable access.

Read the full incident report →

Started Oct 14, 2026, 05:38 PM UTC· resolved Oct 16, 2026, 10:39 PM UTC

1. investigating Oct 14, 2026, 05:38 PM UTC

   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.

2. monitoring Oct 14, 2026, 06:46 PM UTC

   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.

3. monitoring Oct 14, 2026, 09:28 PM UTC

   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.

4. monitoring Oct 15, 2026, 08:18 PM UTC

   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.

Read the full incident report →

Started Oct 09, 2026, 05:42 PM UTC· resolved Oct 12, 2026, 02:36 PM UTC

1. investigating Oct 09, 2026, 05:42 PM UTC

   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.

2. investigating Oct 09, 2026, 06:49 PM UTC

   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.

3. investigating Oct 09, 2026, 07:53 PM UTC

   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.

4. investigating Oct 09, 2026, 08:57 PM UTC

   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.

5. monitoring Oct 09, 2026, 09:42 PM UTC

   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.

6. monitoring Oct 10, 2026, 07:15 AM UTC

   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.

Read the full incident report →

Started Oct 07, 2026, 02:54 PM UTC· resolved Oct 09, 2026, 07:20 AM UTC

1. identified Oct 07, 2026, 02:54 PM UTC

   We are aware of an issue affecting customers who have upgraded to OneAgent version 1.347. The issue is due to an emergent incompatibility with Oracle, customers may experience issues running the Orabase command-line interface (CLI) tool. Out of an abundance of caution, we recommend that customers running Orbase CLI tool do not upgrade to OneAgent 1.347 until the incompatibility has been resolved. If you have already upgraded and are experiencing impact, we recommend downgrading to a OneAgent version earlier than 1.347 until resolved. We understand the potential disruption this may cause and appreciate your patience as we work to resolve this issue. We will provide another update within the next four hours, or sooner if additional information becomes available.

2. identified Oct 07, 2026, 08:00 PM UTC

   We are actively addressing an issue affecting customers who upgraded to OneAgent version 1.347. The issue stems from an emergent incompatibility with Oracle and may impact customers using the Orabase command-line interface (CLI) tool. As a precaution, we continue to recommend that customers using the Orabase CLI tool do not upgrade to OneAgent 1.347 until the incompatibility is resolved. Customers already experiencing impact should downgrade to a OneAgent version earlier than 1.347. A mitigating OneAgent version is currently being rolled out. We will provide the next update within two hours, or sooner if new information becomes available.

3. monitoring Oct 07, 2026, 10:13 PM UTC

   We identified an issue affecting some customers who upgraded to OneAgent version 1.347. Our investigation determined that the issue is related to an incompatibility with Oracle and may impact customers using the Orabase command-line interface (CLI) tool. To address this, a new version of OneAgent has been rolled out and is expected to mitigate the issue for affected customers. We encourage any customer who believes they may be impacted to update to the latest version of OneAgent. Since this version has been released, our teams will continue monitoring the fix to confirm it is working as expected. If the issue persists, please contact your support team. Our support teams are available to assist and will work with you to resolve any remaining impact. We will provide the next update within four hours, or sooner if new information becomes available.

4. identified Oct 08, 2026, 02:03 AM UTC

   We are currently rolling out a new version of OneAgent to address an incompatibility with Oracle that may impact customers using the Orabase command-line interface (CLI) tool. The new version has been successfully deployed to all AWS environments, and we are working to complete the roll out for a small number of Azure and GCP environments. Once available, we encourage any customer who believes they may be impacted to update to the latest version of OneAgent. We will provide the next update at 05:00 AM UTC, or sooner if new information becomes available.

5. identified Oct 08, 2026, 05:19 AM UTC

   We are continuing to work on completing the roll out of the new OneAgent version for the remaining Azure and GCP environments. The new version is available on all AWS environments. We will provide the next update by 09:00 AM UTC, or sooner if new information becomes available.

6. identified Oct 08, 2026, 09:10 AM UTC

   We have completed the rollout of the updated OneAgent version to all AWS environments. We expect the updated version for the remaining Azure and GCP environments to become available early next week. Customers on Azure and GCP environments who are using the Orabase command-line interface (CLI) tool should pause upgrading to OneAgent version 1.347 until the updated version becomes available. Customers already experiencing impact may use a OneAgent version earlier than 1.347 as a workaround. As the rollout timeline for the remaining Azure and GCP environments is longer than initially anticipated, we will provide the next update by Monday, 8:00 AM UTC, or sooner if new information becomes available.

Read the full incident report →

Started Oct 01, 2026, 01:35 PM UTC· resolved Oct 01, 2026, 09:06 PM UTC

1. investigating Oct 01, 2026, 01:35 PM UTC

   We are investigating an issue affecting environments on GCP in the US-East region. Customers may experience delays in data ingestion or issues with data processing. We are working to restore normal processing as quickly as possible. We will provide another update by 3:30 PM UTC, or sooner if further information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

2. investigating Oct 01, 2026, 02:09 PM UTC

   We are investigating an issue affecting services in the GCP US-East region. Customers may currently experience delayed telemetry data ingestion. As a result, some telemetry may not be fully reflected in Dynatrace services, which may lead to gaps in dashboards, delayed problem detection, or event-based workflows not executing as expected. We are working to restore normal processing as quickly as possible and will provide another update by 4:00 PM UTC, or sooner if further information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

3. monitoring Oct 01, 2026, 03:07 PM UTC

   The issue affecting services in the GCP US-East region has been mitigated. The root cause points to a service disruption on our cloud provider’s side, which has since subsided. Telemetry ingestion has recovered, and delayed log data is now being processed. Customers should begin to see recovery across related Dynatrace services as processing continues to stabilize. Our teams are monitoring for continued stability and will provide another update by 6:00 PM UTC, or sooner if further information becomes available. We apologize for the disruption and appreciate your continued patience as recovery progresses.

4. monitoring Oct 01, 2026, 06:03 PM UTC

   We continue to see positive progress following the mitigation of the service disruption affecting the GCP US-East region. Telemetry ingestion has recovered, and delayed log data is processing as expected, with related Dynatrace services continuing to stabilize. Our teams will remain actively engaged and continue monitoring to confirm sustained stability. We will provide another update by 9:00PM UTC, or sooner if there are any material changes. We appreciate your continued patience and partnership as recovery progresses.

Read the full incident report →

Started Sep 30, 2026, 05:11 PM UTC· resolved Oct 02, 2026, 07:11 AM UTC

1. investigating Sep 30, 2026, 05:11 PM UTC

   We are aware of an issue affecting EdgeConnect service availability in a limited number of customer environments. During this period, workflows that rely on EdgeConnect to deliver problem notifications may be impacted. A temporary workaround is available; please contact support team for guidance on applying it. Our teams are actively investigating the root cause and working with urgency to restore a permanent fix. We will provide another update within the next hour, or sooner if further information becomes available. We recognize the importance of timely notifications to your operations and are treating this as a priority. Thank you for your patience.

2. investigating Sep 30, 2026, 06:02 PM UTC

   We are continuing to investigate an issue affecting EdgeConnect service availability in a limited number of customer environments. During this period, workflows that rely on EdgeConnect to deliver problem notifications may be impacted. A temporary workaround remains available; please contact support teams for guidance on applying it. Our teams remain focused on identifying the root cause and advancing mitigation efforts toward a full resolution. We will provide another update by 8pm UTC, or sooner if further information becomes available. We recognize the importance of timely notifications to your operations and are treating this as a priority. Thank you for your patience.

3. investigating Sep 30, 2026, 08:09 PM UTC

   We are continuing to investigate an issue affecting EdgeConnect service availability in a limited number of customer environments. During this period, workflows that rely on EdgeConnect to deliver problem notifications may be impacted. While a temporary workaround is available, our teams remain actively engaged in developing and validating a permanent fix. If your environment is affected, please contact Support for guidance on applying the workaround. Our teams are prioritizing resolution efforts and will continue to provide updates as progress is made. We will provide another update by tomorrow 8AM UTC, or sooner if further information becomes available. We recognize the importance of timely notifications to your operations and are treating this matter with urgency. Thank you for your continued patience as we work toward full resolution.

4. investigating Sep 30, 2026, 09:35 PM UTC

   We have stabilized the environment affected by the EdgeConnect service availability issue. As a result, customers should now be able to access EdgeConnect without performing the previously communicated workaround. Our teams remain actively engaged in the work needed to reach full resolution. We will continue to monitor service behavior closely and provide updates as progress is made. We will provide another update by tomorrow 8AM UTC, or sooner if further information becomes available. We are sorry for the inconvenience and thank you for your continued patience as we work toward full resolution.

5. investigating Oct 01, 2026, 07:51 AM UTC

   We have stabilized the environment affected by the EdgeConnect service availability issue. As a result, customers should now be able to access EdgeConnect without performing the previously communicated workaround. Our teams remain actively engaged in the work needed to reach full resolution. We will continue to monitor service behavior closely and provide updates as progress is made. We will provide another update by tomorrow 8:00 PM UTC, or sooner if further information becomes available. We are sorry for the inconvenience and thank you for your continued patience as we work toward full resolution.

Read the full incident report →

Started Sep 30, 2026, 11:33 AM UTC· resolved Sep 30, 2026, 02:35 PM UTC

1. investigating Sep 30, 2026, 11:33 AM UTC

   We are currently investigating an issue affecting telemetry data processing in the AWS South America region. As a result, customers may experience delays in the ingestion and processing of logs, metrics, and events. Traces and spans are not affected. Our teams are actively investigating the issue and working to restore normal service. Our next update will be provided by 13:30 PM UTC, or sooner if significant new information becomes available. We apologize for the inconvenience.

2. monitoring Sep 30, 2026, 12:43 PM UTC

   We have applied mitigation measures and are seeing recovery across the affected services. Processing of logs, metrics, and events has fully recovered, all backlog has been cleared, and ingestion is operating normally. During the impact, customers may have experienced delays in the ingestion and processing of logs, metrics, and events. Traces and spans were not affected. We will continue to monitor the service and apologize for the inconvenience. Our next update will be provided by 2:45 PM UTC, or sooner if significant new information becomes available.

Read the full incident report →

Started Sep 25, 2026, 09:57 PM UTC· resolved Oct 01, 2026, 08:58 AM UTC

1. investigating Sep 25, 2026, 09:57 PM UTC

   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.

2. identified Sep 26, 2026, 02:17 PM UTC

   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.

3. identified Sep 28, 2026, 10:13 AM UTC

   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.

4. identified Sep 28, 2026, 04:09 PM UTC

   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.

5. identified Sep 28, 2026, 08:22 PM UTC

   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.

6. identified Sep 29, 2026, 02:51 AM UTC

   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.

7. identified Sep 29, 2026, 07:13 AM UTC

   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.

8. identified Sep 29, 2026, 12:55 PM UTC

   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.

9. identified Sep 29, 2026, 03:45 PM UTC

   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.

10. identified Sep 29, 2026, 08:03 PM UTC

    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.

11. identified Sep 29, 2026, 10:59 PM UTC

    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.

12. identified Sep 30, 2026, 03:03 AM UTC

    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.

13. identified Sep 30, 2026, 06:53 AM UTC

    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.

14. identified Sep 30, 2026, 10:57 AM UTC

    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.

15. identified Sep 30, 2026, 06:40 PM UTC

    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.

16. monitoring Oct 01, 2026, 02:50 AM UTC

    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.

Read the full incident report →

Started Sep 23, 2026, 02:16 PM UTC· resolved Sep 23, 2026, 04:01 PM UTC

1. investigating Sep 23, 2026, 02:16 PM UTC

   We are aware of an issue impacting access in multiple regions within the last hour. Customers may experience intermittent errors impacting login and potential access to services in these regions, ingestion of data isn't affected. Our teams are actively working toward mitigation, and we will provide additional updates as more information becomes available. We will provide an update in the next 30 mins or sooner if available. We apologize for any disruption and appreciate your patience while we work to resolve this issue.

2. identified Sep 23, 2026, 02:34 PM UTC

   We are aware of an issue impacting service access across multiple regions within the last hour. Some customers may experience intermittent errors when logging in or accessing services in the affected regions. Based on current information, data ingestion is not impacted. Mitigation steps have been implemented, including rerouting traffic away from the infrastructure experiencing issues, and we are observing positive indicators of recovery. Our teams are continuing to monitor service health closely to validate sustained improvement and overall stability. We will provide another update within the next 30 minutes, or sooner if there is a material change. We apologize for the disruption and appreciate your patience as we continue working to confirm full recovery.

3. monitoring Sep 23, 2026, 02:59 PM UTC

   We are addressing an issue affecting service access across multiple regions. Some customers may have experienced intermittent errors when logging in or accessing services in the affected regions. Based on current information, data ingestion remains unaffected. Mitigation actions have been implemented, including rerouting traffic away from the affected infrastructure, and we continue to see positive improvements from these efforts. Our teams will continue to monitor the issue closely until full recovery has been confirmed. We will provide another update within the next hour, or sooner if there is a material change. We apologize for the disruption and appreciate your continued patience as we work to confirm sustained service stability.

Read the full incident report →

Started Sep 16, 2026, 03:16 PM UTC· resolved Sep 16, 2026, 09:16 PM UTC

1. investigating Sep 16, 2026, 03:16 PM UTC

   We are aware of an issue affecting DTP-Prod16 (IL - Central-1). Currently, alerting and querying are unavailable, and data ingestion is currently lagged. Our teams are actively investigating and working to remediate the issue as quickly as possible. We apologize for the disruption and will provide another update within the next hour, or sooner as more information becomes available.

2. identified Sep 16, 2026, 03:56 PM UTC

   We have identified the issue affecting IL - Central-1 as related to AWS service disruption in the IL - Central-1 region. Currently, alerting querying and data ingestion remain affected for impacted customers. Data ingest is currently lagging, with the full impact to be determined by support teams after restoration. Our teams are actively engaged with AWS and are prioritizing service restoration while continuing to assess customer impact. We apologize for the disruption and will provide another update within the next hour, or sooner as more information becomes available.

3. identified Sep 16, 2026, 05:12 PM UTC

   AWS has confirmed performance issues with the Amazon Aurora PostgreSQL Multi-AZ clusters in the IL-CENTRAL-1 Region. AWS is working to identify the underlying root cause and, in parallel, to mitigate the issue. This AWS service disruption continues to affect Dynatrace services in the IL-CENTRAL-1 region for impacted customers, including alerting query functionality and data ingestion. Data ingestion is currently delayed, and our support teams will continue assessing the full customer impact as restoration progresses. Our teams remain actively engaged with AWS and are focused on supporting service restoration, monitoring customer-facing services closely, and validating impact as AWS mitigation efforts continue. We apologize for the disruption and will provide another update within the next two hours, or sooner as more information becomes available.

4. monitoring Sep 16, 2026, 07:40 PM UTC

   AWS has administered a fix for the issue affecting services in the IL-CENTRAL-1 Region. We are seeing improvement across impacted services and will continue to validate recovery. This AWS-related disruption affected Dynatrace services in the IL-CENTRAL-1 region for impacted customers, including alerting, query functionality, and data ingestion. While conditions are improving, our teams are continuing to monitor customer-facing services closely for any remaining issues. Our teams remain actively engaged and are focused on confirming sustained service stability while monitoring for any continued impact to customers. We apologize for the disruption and appreciate your patience as we continue to monitor the environment. We will provide another update within the next two hours, or sooner if there are material changes.

Read the full incident report →

Started Sep 16, 2026, 09:05 AM UTC· resolved Sep 16, 2026, 05:30 PM UTC

1. identified Sep 16, 2026, 09:05 AM UTC

   We have identified an issue affecting access to the Customer Support Portal. Users may be unable to access or use portal functionality as expected due to a third-party service disruption impacting Salesforce. The issue is external to our services. We are actively monitoring the situation and working with the service provider while awaiting resolution. We apologize for the inconvenience and will provide the next update within one hour or sooner if significant new information becomes available.

2. identified Sep 16, 2026, 09:17 AM UTC

   We have identified an issue affecting access to the Customer Support Portal. Users may be unable to access or use portal functionality as expected due to a third-party service disruption impacting Salesforce. For critical issues requiring immediate assistance, please contact our support hotline at +1-844-900-3962. We apologize for the inconvenience and will provide the next update within one hour or sooner if significant new information becomes available.

3. identified Sep 16, 2026, 09:26 AM UTC

   We have identified an issue affecting access to the Customer Support Portal. Users may be unable to access or use portal functionality as expected due to a third-party service disruption impacting Salesforce. For critical issues requiring immediate assistance, please send an email to [email protected] or contact our support hotline at +1-844-900-3962. We apologize for the inconvenience and will provide the next update within one hour or sooner if significant new information becomes available.

4. identified Sep 16, 2026, 09:41 AM UTC

   We have identified an issue affecting access to the Customer Support Portal. Users may be unable to access or use portal functionality as expected due to a third-party service disruption impacting Salesforce. For critical issues requiring immediate assistance, please follow the instructions in our community article: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Service-disruption-Support-ticket-access-SalesForce/ta-p/304422 We apologize for the inconvenience and will provide the next update within one hour, or sooner if significant new information becomes available.

5. identified Sep 16, 2026, 10:45 AM UTC

   The third-party service disruption impacting access to the Customer Support Portal is ongoing, and functionality may remain unavailable or degraded. For critical issues requiring immediate assistance, please follow the instructions provided in our community article: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Service-disruption-Support-ticket-access-SalesForce/ta-p/304422 We apologize for the inconvenience. As there are currently no indications of remediation by the third-party service provider, we will provide the next update within two hours, or sooner if significant new information becomes available.

6. identified Sep 16, 2026, 12:43 PM UTC

   Salesforce has initiated remediation activities for the service disruption affecting access to the Customer Support Portal. We are observing improvements in portal availability and functionality; however, intermittent issues may still occur. For critical issues requiring immediate assistance, please follow the instructions provided in our community article: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Service-disruption-Support-ticket-access-SalesForce/ta-p/304422 We apologize for the inconvenience and will provide the next update within two hours, or sooner if significant new information becomes available.

7. monitoring Sep 16, 2026, 02:37 PM UTC

   We continue to see improvement in access to the Customer Support Portal following Salesforce’s remediation activities. Some customers may need to clear cached data or restart their session for full recovery. However, we have not yet received final confirmation of full resolution from Salesforce, and intermittent issues may still occur while remediation work continues. We will continue to monitor the situation closely for any further issues. Customers who are still experiencing issues and require assistance with critical matters should follow the instructions provided in our community article: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Service-disruption-Support-ticket-access-SalesForce/ta-p/304422 We apologize for the inconvenience and will provide the next update within two hours, or sooner if significant new information becomes available.

8. monitoring Sep 16, 2026, 04:31 PM UTC

   We are seeing continued improvement in access to the Customer Support Portal following Salesforce’s remediation efforts. Some customers may need to clear cached data or restart their session for full recovery. At this time, we have not yet received final confirmation of full resolution from Salesforce. We will continue to monitor the situation closely until that confirmation has been provided and will share any significant updates as they become available. Customers who are still experiencing issues and require assistance with critical matters should follow the instructions provided in our community article: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Service-disruption-Support-ticket-access-SalesForce/ta-p/304422 We apologize for the inconvenience and will provide the next update within four hours, or sooner if significant new information becomes available

Read the full incident report →

Started Sep 14, 2026, 01:35 PM UTC· resolved Sep 14, 2026, 04:42 PM UTC

1. investigating Sep 14, 2026, 01:35 PM UTC

   We are investigating a performance issue affecting Azure environments in the East US region. Increased latency is impacting metric processing and may also result in slower-than-normal user interface responsiveness. Customers may experience reduced alert generation, including metric events and anomaly detection. We are currently evaluating mitigation measures to restore normal service performance and will provide further updates as more information becomes available. We apologize for the inconvenience.

2. monitoring Sep 14, 2026, 01:54 PM UTC

   We have identified the cause of a performance issue affecting Azure environments in the East US region. Mitigation measures have been applied, and service levels are returning to normal. We are continuing to monitor the environment closely to ensure ongoing stability and will provide the next update within one hour or sooner if significant new information becomes available. We apologize for the inconvenience.

3. monitoring Sep 14, 2026, 02:54 PM UTC

   We continue to observe stable performance across Azure environments in the East US region following the mitigation measures previously implemented. Service levels remain within expected thresholds, and no new issues have been identified. Given the positive recovery trend, our next update will be provided within two hours, or sooner if any significant new information becomes available. We apologize for the inconvenience and appreciate your patience while we continue to monitor the environment closely.

Read the full incident report →

Started Sep 10, 2026, 10:56 AM UTC· resolved Sep 10, 2026, 02:31 PM UTC

1. investigating Sep 10, 2026, 10:56 AM UTC

   We are investigating an issue affecting a subset of Dynatrace environments on AWS US East. Some customers may experience failures of DQL queries, when loading dashboards and applications, and delays or failures in alert processing, or missing alerts. We apologize for the inconvenience and will provide the next update within one hour or sooner if significant new information becomes available.

2. monitoring Sep 10, 2026, 11:53 AM UTC

   A mitigation has been implemented for the issue affecting a subset of Dynatrace environments on AWS US East. Service availability has improved, and we are actively monitoring the platform to ensure stability. We apologize for the inconvenience and will provide the next update within one hour or sooner if significant new information becomes available.

3. monitoring Sep 10, 2026, 12:52 PM UTC

   Service availability remains stable following the mitigation implemented for the issue affecting a subset of Dynatrace environments on AWS US East. We continue to actively monitor the platform to ensure stability. We apologize for the inconvenience and will provide the next update within one hour or sooner if significant new information becomes available.

4. monitoring Sep 10, 2026, 01:51 PM UTC

   Service availability remains stable in AWS US East. We continue to actively monitor the platform and have not observed a recurrence of the issue. We apologize for the inconvenience and will provide the next update within one hour or sooner if significant new information becomes available.

Read the full incident report →

Started Sep 01, 2026, 11:54 AM UTC· resolved Sep 03, 2026, 02:19 PM UTC

1. investigating Sep 01, 2026, 11:54 AM UTC

   We are investigating an issue affecting authentication services. As a result, data processing and extraction services may experience errors or delayed results. Data ingestion continues to operate, but processing of ingested data may be impacted. Our teams are actively investigating the issue and working to restore normal service. Please monitor Dynatrace Status for further updates. We apologize for the inconvenience.

2. investigating Sep 01, 2026, 12:13 PM UTC

   We are continuing to investigate the issue affecting authentication services. Customers may experience problems accessing Dynatrace services. We are actively working to mitigate the issue and restore normal service. We will provide our next update within 30 minutes or sooner if significant new information becomes available. We apologize for the inconvenience.

3. identified Sep 01, 2026, 12:41 PM UTC

   We have identified the issue affecting authentication services and are actively implementing mitigation measures. Customers may experience problems accessing Dynatrace services while mitigation activities are in progress. We are working to restore normal service as quickly as possible and will provide our next update within 30 minutes or sooner if significant new information becomes available. We apologize for the inconvenience.

4. identified Sep 01, 2026, 01:10 PM UTC

   We continue to work on mitigation measures for the issue affecting authentication services. Customers may experience problems accessing Dynatrace services. We will provide our next update within 30 minutes or sooner if significant new information becomes available. We apologize for the inconvenience.

5. identified Sep 01, 2026, 01:41 PM UTC

   We continue to work on mitigation measures for the issue affecting authentication services and are observing slight improvements. We will provide our next update within 30 minutes or sooner if significant new information becomes available. We apologize for the inconvenience.

6. identified Sep 01, 2026, 02:11 PM UTC

   We continue to work on mitigation measures for the issue affecting authentication services. We are observing continued improvements. Access to the Dynatrace platform is improving. We have implemented additional mitigation measures to reduce the impact, while work continues to restore all affected services. We will provide our next update within 30 minutes or sooner if significant new information becomes available.

7. identified Sep 01, 2026, 02:45 PM UTC

   We continue to make progress in mitigating the issue affecting authentication services. Additional mitigation measures have been implemented to reduce customer impact while our teams continue working toward full service restoration. We will provide the next update within 30 minutes, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience as we continue working toward full mitigation.

8. identified Sep 01, 2026, 03:14 PM UTC

   We continue to make progress in mitigating the issue affecting authentication services. Additional mitigation measures have been implemented to reduce customer impact while our teams continue working toward full-service restoration. We will provide the next update within 30 minutes, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience as we continue working toward full mitigation.

9. identified Sep 01, 2026, 03:47 PM UTC

   We continue to make progress in mitigating the issue affecting authentication services. We have identified that the token service supporting several Dynatrace capabilities remains impacted and are actively implementing additional mitigation measures while work continues toward full service restoration. The following services may experience degraded functionality or interruptions while mitigation activities are in progress: - Authentication Services - Anomaly Detectors - BizEvents - Extracted Metrics - Problem Manager - Real User Monitoring - Smartscape - Synthetics - Workflows In addition, customers may begin to experience issues accessing the Dynatrace Classic UI. If you are unable to access your environment, this is related to this ongoing incident. We will share progress and resolution updates on this Status Page as they become available. To reduce duplicate effort and keep our teams focused on remediation, please follow this incident here rather than opening a Support case for the impacted behavior. Our teams remain actively engaged and are working to restore all affected services as quickly as possible. We will provide the next update within 30 minutes, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience as we continue working toward full mitigation.

10. identified Sep 01, 2026, 04:19 PM UTC

    We continue to make progress in mitigating the issue affecting authentication services. We have identified that the token service supporting several Dynatrace capabilities remains impacted and are actively implementing additional mitigation measures while work continues toward full service restoration. The following services may experience degraded functionality or interruptions while mitigation activities are in progress: - Authentication Services - Anomaly Detectors (Alerting) - BizEvents - Extracted Metrics - Problem Manager - Real User Monitoring - Smartscape - Synthetics - Workflows In addition, customers may begin to experience issues accessing the Dynatrace Classic UI. If you are unable to access your environment, this is related to this ongoing incident. We will share progress and resolution updates on this Status Page as they become available. To reduce duplicate effort and keep our teams focused on remediation, please follow this incident here rather than opening a Support case for the impacted behavior. Our teams remain actively engaged and are working to restore all affected services as quickly as possible. We will provide the next update within 30 minutes, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience as we continue working toward full mitigation.

11. identified Sep 01, 2026, 04:53 PM UTC

    We continue to make progress mitigating the issue affecting the Dynatrace Platform. The token service supporting several Dynatrace capabilities remains impacted, and we are implementing additional mitigation measures to further reduce customer impact while work continues toward full-service restoration. The following services may experience degraded functionality or interruptions while mitigation activities are in progress: - Authentication Services - Anomaly Detectors (Alerting) - BizEvents - Extracted Metrics - Problem Manager - Real User Monitoring - Smartscape - Synthetics - Workflows In addition, customers may begin to experience issues accessing the Dynatrace Classic UI. If you are unable to access your environment, this is related to this ongoing incident. We will share progress and resolution updates on this Status Page as they become available. To reduce duplicate effort and keep our teams focused on remediation, please follow this incident here rather than opening a Support case for the impacted behavior. Our teams remain actively engaged and are working to restore all affected services as quickly as possible. We will provide the next update within 30 minutes, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience as we continue working toward full mitigation.

12. identified Sep 01, 2026, 05:35 PM UTC

    We are continuing to implement mitigation measures and are seeing gradual progress. Our investigation has helped narrow the issue to increase of requests affecting our authentication services coming from internal resources. The team is actively working to restore service behaviour to normal operating levels. However, we are still processing the accumulated backlog, and customers may continue to experience degraded functionality until recovery is fully completed. We will provide the next update within 30 minutes, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience as we continue working toward full mitigation.

13. identified Sep 01, 2026, 06:10 PM UTC

    We continue to implement mitigation measures, and early results are showing promising signs of improvement. Our investigation has narrowed the issue to elevated internal request volume impacting authentication services. Teams remain focused on restoring normal service behavior as quickly and safely as possible. Recovery is still progressing as we work through the accumulated backlog, and some customers may continue to experience degraded functionality until mitigation is fully complete. We will provide the next update within 30 minutes, or sooner if significant new information becomes available. We apologize for the disruption and appreciate your continued patience as we work toward full mitigation.

14. identified Sep 01, 2026, 06:42 PM UTC

    We continue to implement mitigation measures, and some customers should begin seeing improvements in their environments. Our investigation has narrowed the issue to elevated internal request volume impacting authentication services. Teams remain fully engaged and are making steady progress toward restoring normal service behavior as quickly as possible. Until full mitigation is reached, some customers may continue to experience degraded functionality and data ingestion lags, while recovery work continues. We will provide the next update within 30 minutes, or sooner if significant new information becomes available. We apologize for the disruption and appreciate your continued patience as we work toward full mitigation.

15. identified Sep 01, 2026, 07:24 PM UTC

    We continue to see steady improvement as mitigation efforts progress, and many customers should already be experiencing better platform performance. While we are making significant progress toward full service restoration, some customers may still encounter degraded functionality and delays in data ingestion as recovery activities continue. We understand the impact this may have on your operations and remain fully focused on restoring all services as quickly as possible. Full recovery may take several more hours. We will provide the next update within 60 minutes, or sooner if there are any significant developments. We sincerely apologize for the disruption and greatly appreciate your patience and understanding as we work toward full restoration.

16. identified Sep 01, 2026, 08:31 PM UTC

    Mitigation efforts continue to show steady improvement, and many customers are already seeing better platform performance. While recovery work continues, some customers may still experience degraded functionality or data ingestion delays. We are closely monitoring backlog processing and overall system health to help ensure customer environments return to a healthy state following this incident. We understand the importance of restoring normal service as quickly as possible and remain fully engaged until recovery is complete. Based on current progress, full recovery may still require several more hours, and we will continue working to minimize any remaining customer impact. The latest mitigation efforts require propagation. Full recovery may take several more hours. We will share the next update within 30 minutes, or sooner if there is a material change. We sincerely apologize for the disruption and appreciate your continued patience and trust as we complete recovery efforts.

17. identified Sep 01, 2026, 09:03 PM UTC

    Mitigation efforts continue to show progress, with GCP and Azure environments showing significant improvement. Some customers may still experience degraded functionality or data ingestion delays while recovery work continues. Full recovery may take several more hours as mitigation propagates. Teams remain fully engaged and are monitoring system health and backlog processing. We will provide the next update within 30 minutes, or sooner if there are any significant developments. We apologize for the disruption and appreciate your continued patience.

18. identified Sep 01, 2026, 09:34 PM UTC

    Mitigation efforts continue to progress, with GCP and Azure environments demonstrating significant improvement. While recovery activities remain ongoing, our teams are focused on the restoration of AWS environments to a healthy operational state. Some customers may continue to experience degraded functionality or data ingestion delays during this period. Full recovery may require several additional hours as mitigation measures to propagate across affected environments. Our teams remain fully engaged, with continued monitoring of system health and backlog processing. We will provide the next update within 30 minutes, or sooner if there are any significant developments.

19. identified Sep 01, 2026, 10:20 PM UTC

    Mitigation continues to progress, with GCP and Azure showing significant improvement and we are also seeing a large number of AWS deployments are now in a healthy state. Some customers may still experience degraded functionality or data ingestion delays while recovery completes. Full recovery may take several more hours. Our teams remain fully engaged and are monitoring system health and backlog processing. We will provide the next update within 30 minutes, or sooner if there are significant developments.

20. identified Sep 01, 2026, 11:07 PM UTC

    Recovery efforts continue to progress across all cloud providers. Approximately 85% of AWS deployments have now returned to a healthy state, and we continue to see stability across GCP and Azure environments. While service stability has improved for the majority of affected customers, recovery may take several hours, and some customers may still experience degraded functionality or delays in data processing and ingestion as recovery activities continue and remaining backlogs are cleared. Our teams remain fully engaged and are closely monitoring system health and recovery progress. We will provide the next update within 30 minutes, or sooner if there are significant developments.

21. identified Sep 01, 2026, 11:47 PM UTC

    Mitigations have now been implemented across all cloud providers with only a small number of remaining AWS deployments to be restored. Customers may experience degraded functionality or delays in data processing and ingestion, which may take several hours to resolve, as recovery activities continue and remaining backlogs are cleared. Some customers may experience a significant increase in alerts as services restore. Our teams remain fully engaged and are closely monitoring system health and recovery progress. We will provide the next update within 30 minutes, or sooner if there are significant developments.

22. monitoring Sep 02, 2026, 12:27 AM UTC

    Mitigations have now been implemented across all cloud providers and all deployments are fully recovered. We are continuing to actively monitor the health of the restored deployments and currently observing stable performance. Customers may experience degraded functionality or delays in data processing and ingestion, which may take several hours to resolve, as recovery activities continue and remaining backlogs are cleared. Some customers may experience a significant increase in alerts as services restore. We will provide the next update within 30 minutes, or sooner if there are significant developments.

23. monitoring Sep 02, 2026, 01:08 AM UTC

    Mitigations have been successfully implemented and our team is actively monitoring the health of the restored deployments. We are continuing to observe stable performance. Customers may experience degraded functionality or delays in data processing and ingestion, which may take several hours to resolve, as recovery activities continue and remaining backlogs are cleared. Some customers may experience a significant increase in alerts as services restore. We will provide the next update within 60 minutes, or sooner if there are significant developments.

24. monitoring Sep 02, 2026, 02:01 AM UTC

    Our team is actively monitoring the restored deployments and we are continuing to observe stable performance. Some customers may experience degraded functionality, delays in data processing and ingestion, or a temporary increase in alerts. These issues are expected to resolve as backlogs are cleared. It may take several hours for some backlogs to clear and associated tenants to resume normal operations. We will provide the next update within 60 minutes, or sooner if there are significant developments.

25. monitoring Sep 02, 2026, 03:12 AM UTC

    We are continuing to observe stable performance and are maintaining active monitoring to ensure all deployments have an extended period of stable performance. Some customers may experience degraded functionality, delays in data processing and ingestion, or a temporary increase in alerts. These issues are expected to resolve as backlogs are cleared. It may take several hours for some backlogs to clear and associated tenants to resume normal operations. We will provide the next update within 60 minutes, or sooner if there are significant developments.

26. monitoring Sep 02, 2026, 04:55 AM UTC

    Performance across all restored deployments has remained stable as we continue active monitoring. The temporary degradation of functionality, delays in data processing and ingestion, or increase in alerts that some customers have experienced should be subsiding. These issues are expected to resolve as backlogs are cleared. It may take several hours for some backlogs to clear and associated tenants to resume normal operations. We will provide the next update within 60 minutes, or sooner if there are significant developments.

27. monitoring Sep 02, 2026, 06:01 AM UTC

    Performance across all restored deployments has remained stable as we continue active monitoring and providing hourly updates. The temporary degradation of functionality, delays in data processing and ingestion, or increase in alerts that some customers have experienced should be subsiding. These issues are expected to resolve as backlogs are cleared and we are investigating any potential data loss.

28. monitoring Sep 02, 2026, 07:04 AM UTC

    Performance across all deployments remains stable, and we continue to actively monitor service health. Recovery activities are ongoing. Some customers may still experience delays in data processing and ingestion, as well as a temporary increase in alerts, while systems return to normal operation. We are also assessing the impact of the incident on data processing completeness. We will provide the next update within 60 minutes, or sooner if significant new information becomes available.

29. monitoring Sep 02, 2026, 08:10 AM UTC

    Based on our current assessment and monitoring data, all previously affected services have been restored and are operating normally. We continue to monitor the platform closely and are performing additional measures to help ensure ongoing service stability. We will continue monitoring and provide the next update within two hours, or sooner if significant new information becomes available.

30. monitoring Sep 02, 2026, 10:12 AM UTC

    We continue to monitor the platform and are observing stable service operation across affected areas. The platform continues to perform as expected. We will maintain enhanced monitoring and provide the next update within two hours, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience throughout this incident.

31. monitoring Sep 02, 2026, 12:21 PM UTC

    We continue to observe stable platform performance and are actively monitoring service health. While the affected services have been restored and are operating normally, our assessment of the incident's impact has confirmed that some data generated during the affected period may not be recoverable. As a result, some customers may observe gaps in historical data or alerting for the duration of the incident. We will continue monitoring and provide the next update within two hours, or sooner if significant new information becomes available.

32. monitoring Sep 02, 2026, 02:14 PM UTC

    We continue to observe stable platform performance and active monitoring remains in progress. Verification of the affected services continues to progress. While the affected services have been restored and are operating normally, our assessment of the incident's impact has confirmed that some data collected during the affected period may not be recoverable. As a result, some customers may observe gaps in historical data or alerting for the duration of the incident. We will continue monitoring and provide the next update within four hours, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience throughout this incident.

33. monitoring Sep 02, 2026, 06:37 PM UTC

    Our platforms continue to demonstrate stable performance, and we are seeing positive results across our environments following the mitigation efforts. We have also increased alerting and are maintaining active monitoring across all environments to confirm that they remain healthy and operating as expected. We will continue monitoring platform health and provide the next update within 4 hours, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience throughout this incident.

34. monitoring Sep 02, 2026, 10:52 PM UTC

    Our platforms continue to demonstrate stable performance, and we are seeing positive results across our environments following the mitigation efforts. We have also increased alerting and are maintaining active monitoring across all environments to confirm that they remain healthy and operating as expected. We will continue monitoring platform health and provide the next update within 4 hours, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience throughout this incident.

35. monitoring Sep 03, 2026, 02:31 AM UTC

    Out team continues to observe stable performance across our platforms. We are prolonging our active monitoring and increased alerting to ensure all services are stable for an extended period. Our next status update will be within the next four hours, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience throughout this incident.

36. monitoring Sep 03, 2026, 06:29 AM UTC

    Performance remains stable across all platforms. We are prolonging our active monitoring and increased alerting to ensure all services are stable for an extended period. Our next status update will be within the next four hours, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience throughout this incident.

37. monitoring Sep 03, 2026, 10:12 AM UTC

    Performance remains stable across all platforms. We are prolonging our active monitoring and increased alerting to ensure all services are stable for an extended period. Our next status update will be within the next four hours, or sooner if significant new information becomes available. We apologize for the inconvenience and appreciate your patience throughout this incident.

Read the full incident report →

Started Aug 28, 2026, 12:53 PM UTC· resolved Aug 28, 2026, 04:38 PM UTC

1. investigating Aug 28, 2026, 12:53 PM UTC

   We are investigating issues with communicating via a Support case within the Support portal. Customers will experience errors communicating into cases on the Support portal. We will have an update within the next one hour unless new information is available. We apologize for the inconvenience this has caused.

2. monitoring Aug 28, 2026, 01:32 PM UTC

   We have identified and mitigated the issue affecting communication through the Support Portal. Customers should now be able to add comments to their support cases as expected. We will continue to monitor this situation to ensure stability and provide an update within the next 4 hours. We apologize for the disruption and appreciate your patience while we worked to resolve this.

Read the full incident report →

Started Aug 27, 2026, 06:18 PM UTC· resolved Aug 31, 2026, 08:54 AM UTC

1. investigating Aug 27, 2026, 06:18 PM UTC

   We are investigating reports of performance degradation affecting some customer environments in the US East region. We are actively working to determine the cause and will provide an update within one hour, or sooner as new information becomes available.

2. monitoring Aug 27, 2026, 06:49 PM UTC

   We have identified and mitigated the issue causing performance degradation for customer environments in the US East region. Performance has improved significantly, and we are receiving positive confirmation from affected customers. Our teams will continue to closely monitor the environments over the coming hours. We will provide our final update within the next hour, or sooner if additional information becomes available. We apologize for the impact this issue may have caused and appreciate your patience as we worked to resolve it.

3. resolved Aug 27, 2026, 07:59 PM UTC

   We have resolved the issue that caused performance degradation for customer environments in the US East region. Affected environments have returned to expected performance levels, and our teams will continue to monitor closely to ensure ongoing stability. If you continue to experience any issues, please open a support case so our team can investigate and assist you directly. We sincerely apologize for the disruption this issue caused and appreciate your patience while we worked to restore normal services.

4. investigating Aug 27, 2026, 10:09 PM UTC

   We are aware of a recurrence of the issue causing performance degradation for some customer environments in the US East region. Our teams are actively investigating and working toward mitigation to restore expected performance levels as quickly as possible. We will continue to monitor closely and provide updates as more information becomes available. We sincerely apologize for the continued impact and appreciate your patience while we work to resolve this issue.

5. investigating Aug 27, 2026, 11:18 PM UTC

   We are aware of a recurrence of the issue causing performance degradation for some customer environments in the US East region. Interventions have been implemented and we are currently observing that normal performance has resumed. We are still investigating the cause of this incident and are actively monitoring performance. The next update will be provided at 12:00 PM UTC. We sincerely apologize for the continued impact and appreciate your patience while we work to resolve this issue.

6. monitoring Aug 28, 2026, 12:01 AM UTC

   We experienced a recurrence of the issue causing performance degradation for some customer environments in the US East region. Interventions have been implemented and we are continuing to observe normal performance. We are also actively monitoring performance and will provide the next status update at 02:00AM UTC. We sincerely apologize for the continued impact and appreciate your patience while we work to resolve this issue.

7. monitoring Aug 28, 2026, 02:00 AM UTC

   Interventions have been successfully implemented, and we are continuing to observe normal performance in this region. We are maintaining active monitoring and will provide the next status update at 04:00AM UTC.

8. monitoring Aug 28, 2026, 03:58 AM UTC

   No further issues have been reported, and we are continuing to observe normal performance in this region. We are maintaining active monitoring and will provide the next status update at 06:00AM UTC.

9. monitoring Aug 28, 2026, 06:07 AM UTC

   No further issues have been reported, and we are continuing to observe normal performance in this region. We are maintaining active monitoring and will provide the next status update at 08:00AM UTC.

10. monitoring Aug 28, 2026, 07:59 AM UTC

    No further issues have been reported, and we are continuing to observe normal performance in this region. We are maintaining active monitoring and will provide the next status update at 10:00AM UTC.

11. monitoring Aug 28, 2026, 10:38 AM UTC

    No further issues have been reported, and we are continuing to observe normal performance in this region. We are maintaining active monitoring and will provide the next status update at 14:00AM UTC.

12. monitoring Aug 28, 2026, 02:00 PM UTC

    No further issues have been reported, and we continue to observe normal performance in this region. We are maintaining active monitoring over the weekend to ensure continued service stability. We will provide the next status update by Monday EOD UTC, or sooner if there is a significant change in status.

Read the full incident report →

Started Aug 20, 2026, 09:10 PM UTC· resolved Aug 24, 2026, 10:03 AM UTC

1. investigating Aug 20, 2026, 09:10 PM UTC

   We are aware of an issue resulting in a loss of monitoring visibility for Lambda functions on Node.js version 22. Our team is actively investigating this issue and are working towards mitigation. We understand the importance of reliable monitoring and will provide the next update within the next four hours, or sooner if additional information becomes available. Thank you for your patience and understanding.

2. investigating Aug 20, 2026, 11:05 PM UTC

   We are actively investigating an issue causing a loss of monitoring visibility for Lambda functions running on Node.js version 22. We recommend that customers avoid running nodejs:22.version 95 while our teams continue to assess scope, impact, and the path to mitigation. As an interim mitigation, customers may roll back to their previously working Node.js 22 runtime version. If assistance is needed to perform the rollback, please engage AWS Support. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience

3. identified Aug 21, 2026, 12:01 AM UTC

   We have identified the issue causing a loss of monitoring visibility for Lambda functions running on Node.js version 22. Classic Lambda layers do not work correctly with the newest AWS-provided Node.js 22 runtime version (nodejs:22.mainline.v95), causing affected Lambda functions to time out and lose OneAgent monitoring. To avoid this impact, we recommend that customers do not update to nodejs:22.mainline.v95. If you have already updated and are affected, you can roll back to the previously working Node.js 22 runtime (for example, v91). If assistance is needed to perform the rollback, customers should engage AWS Support. Our teams are working on a permanent fix and will continue to share updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

4. identified Aug 21, 2026, 08:04 AM UTC

   We continue to work on the identified issue affecting Lambda functions running on the AWS-provided Node.js 22 runtime version (nodejs:22.mainline.v95), causing affected Lambda functions to time out and lose OneAgent monitoring. We are actively working with AWS towards a permanent fix. In parallel, our teams are investigating additional mitigation options to help reduce customer impact. As a precaution, we continue to recommend that customers do not update to nodejs:22.mainline.v95. If you have already updated and are experiencing issues, you may roll back to a previously working Node.js 22 runtime version (for example, v91). Customers requiring assistance with a rollback should engage AWS Support. We will continue to provide updates as more information becomes available. We apologize for the inconvenience and appreciate your patience.

5. monitoring Aug 21, 2026, 08:05 PM UTC

   We have identified the root cause of the issue affecting monitoring visibility for Lambda functions running on the AWS-provided Node.js 22 runtime (nodejs:22.mainline.v95), and mitigations have been applied. A fix has been released in OneAgent 1.343 for SaaS environments. Investigation into fixes for additional supported versions is ongoing. We will provide updates as they become available. As an interim workaround, customers can continue to pin their Lambda runtime to a previously working Node.js 22 version (e.g., v91). Customers requiring assistance with a rollback should engage AWS Support. 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.

Read the full incident report →

Started Aug 13, 2026, 02:09 PM UTC· resolved Aug 13, 2026, 04:39 PM UTC

1. identified Aug 13, 2026, 02:09 PM UTC

   We have identified an issue affecting Dynatrace services hosted in AWS US East. Users may experience errors in the Dynatrace UI, slower-than-normal performance, and missing or delayed alerts. We are working to mitigate the impact and restore normal service. Please continue to monitor Dynatrace Status for updates. We apologize for the inconvenience and will provide an update within the next two hours or sooner if we have more information to share.

2. monitoring Aug 13, 2026, 03:16 PM UTC

   We have identified the issue affecting Dynatrace services hosted in AWS US East. Mitigation efforts have been implemented, and customers should begin to see service improvement. We are actively monitoring recovery to validate the effectiveness of these mitigations and confirm continued stabilization. We apologize for the inconvenience and thank you for your patience. The next update will be provided within two hours, or sooner if meaningful progress is confirmed.

Read the full incident report →

Started Aug 12, 2026, 06:34 PM UTC· resolved Aug 13, 2026, 12:05 PM UTC

1. investigating Aug 12, 2026, 06:34 PM UTC

   We are investigating an issue that may cause some customers located in East US Deployment to experience increased latency and slower response times within the user interface. Our teams are actively engaged and working toward a resolution. We will provide an update within two hours or if progress has been made. We apologize for the inconvenience and thank you for your patience.

2. identified Aug 12, 2026, 08:16 PM UTC

   We have identified the issue causing increased latency and slower response times within the user interface for some customers in the East US deployment. Our team is working to restore expected performance. We will provide the next update within four hours, or sooner if additional progress is available. We apologize for the disruption and appreciate your continued patience as we work to resolve this matter.

3. identified Aug 13, 2026, 12:27 AM UTC

   We have identified the issue causing increased latency and slower response times within the user interface for some customers in the East US deployment. We are currently implementing changes to restore expected performance. We will provide the next update at 01:30am UTC, or sooner if additional progress is available. We apologize for the disruption and appreciate your continued patience as we work to resolve this matter.

4. identified Aug 13, 2026, 01:39 AM UTC

   We have identified the issue causing increased latency and slower response times within the user interface for some customers in the East US deployment. We are continuing to implement changes to restore expected performance. We will provide the next update at 05:30am UTC, or sooner if additional progress is available. We apologize for the disruption and appreciate your continued patience as we work to resolve this matter.

5. monitoring Aug 13, 2026, 03:46 AM UTC

   We have implemented changes to address the increased latency and slower response times within the user interface that some customers in the East US deployment experienced. We are currently observing normal performance and will continue monitoring the situation prior to resolving this incident. If you experience further issues, please raise a support case.

Read the full incident report →

Started Aug 12, 2026, 04:50 PM UTC· resolved Aug 12, 2026, 07:14 PM UTC

1. identified Aug 12, 2026, 04:50 PM UTC

   We have identified an issue affecting Workflows functionality impacting event triggers for some customers. Our teams are actively investigating and working toward a fix. We will provide an update within the next two hours, or sooner when more information becomes available. We apologize for the inconvenience and appreciate your patience while we work to resolve this issue.

Read the full incident report →

Started Aug 11, 2026, 11:33 AM UTC· resolved Aug 11, 2026, 04:49 PM UTC

1. investigating Aug 11, 2026, 11:33 AM UTC

   We are investigating an issue affecting metric ingestion from a subset of AWS and Azure integrations. As a result, some customers may observe incomplete metric data and gaps in monitoring results. In addition, certain topology-related data may be delayed. Our teams are actively working to identify the cause and restore normal service. We will provide further updates as they become available. We apologize for any inconvenience this issue may cause.

2. monitoring Aug 11, 2026, 03:23 PM UTC

   We have implemented a fix for the issue affecting metric ingestion for a subset of AWS and Azure integrations. Customers should no longer experience incomplete metric data, gaps in monitoring results, or delays with certain topology-related data. Our teams are actively monitoring the fix to confirm service stability and ensure the issue remains resolved. We will provide an update in 2 hours. If you continue to experience any issues, please contact your account teams. We apologize for the disruption and appreciate your patience while we monitor the fix.

Read the full incident report →

Started Aug 07, 2026, 10:21 PM UTC· resolved Aug 10, 2026, 12:39 PM UTC

1. monitoring Aug 07, 2026, 10:21 PM UTC

   We have mitigated an issue affecting the Dynatrace Platform production environment (AWS-US East). During this time, customers may have experienced processing delays mainly with logs. Our teams are actively working to stabilize the environment, restore normal processing, and validate the scope of customer impact. We are closely monitoring service health and will provide additional updates as meaningful progress is made. If you are experiencing any issue please open a support case.

Read the full incident report →

Started Aug 04, 2026, 03:29 PM UTC· resolved Aug 05, 2026, 11:38 AM UTC

1. identified Aug 04, 2026, 03:29 PM UTC

   We have identified an issue impacting the AWS Lambda layer on Node.js for version 1.341 which is missing a runtime configuration for the SQS/SNS instrumentation, We are currently working on a fix to publish to all environments. There will be a progress update here within the next 4 hours. We apologize for the inconvenience this has caused.

2. identified Aug 04, 2026, 08:04 PM UTC

   Our teams continue to work on finalizing the build and deploying it across all customer environments. We will share our next update within 4 hours, including the latest progress on the rollout. We appreciate your patience as we work to complete this effort.

3. identified Aug 05, 2026, 12:17 AM UTC

   We have commenced deploying a fix for the issue impacting the AWS Lambda layer on Node.js for version 1.341 which is missing a runtime configuration for the SQS/SNS instrumentation. A progress update will be provided at 04:00am UTC 5 August.

4. identified Aug 05, 2026, 04:27 AM UTC

   A fix has been deployed for the issue impacting the AWS Lambda layer on Node.js for version 1.341 which was missing a runtime configuration for the SQS/SNS instrumentation. The fix is nearing full deployment, and a status update will be provided once it is completed.

Read the full incident report →

Started Jul 27, 2026, 04:13 PM UTC· resolved Jul 27, 2026, 07:15 PM UTC

1. investigating Jul 27, 2026, 04:13 PM UTC

   We are investigating an issue affecting access to the Platform BizEvents (Business Events) settings page in customer environments. As a result, some customers may be unable to create, modify, or disable BizEvents through the affected settings page: /ui/apps/dynatrace.settings/settings/bizevents. BizEvent processing is uninterrupted at this time. Our teams are actively working to restore access and minimize customer impact. We apologize for the disruption and will provide additional updates as more information becomes available.

Read the full incident report →

Started Jul 24, 2026, 09:08 PM UTC· resolved Jul 27, 2026, 11:44 AM UTC

1. investigating Jul 24, 2026, 09:08 PM UTC

   We have identified an issue that may prevent some customers from deploying Operator 1.10.1 on fresh deployments or upgrades where operator components have been deleted. In some cases, this may delay planned changes in production environments While we work toward a resolution, we have published a Community post with workaround guidance for impacted customers. Please refer to our Community post: https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/Unable-to-deploy-Operator-1-10-1-on-fresh-clusters-or-upgrades/ta-p/302391 We apologize for the inconvenience and appreciate your patience as we work to restore normal deployment functionality.

Read the full incident report →