Dynatrace

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

1. investigating 2026-10-16 16:01 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...

2. investigating 2026-10-16 16:59 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...

3. investigating 2026-10-16 18:51 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...

4. monitoring 2026-10-16 22:24 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...

5. monitoring 2026-10-19 21:30 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...

6. resolved 2026-10-21 20:15 UTC

   We recognize that a subset of customers may experience difficulty accessing the support portal, despite a fix being previously applied. Unfortunately, a new scenario has been identified and as such we are targeting a permanent fix scheduled for release on November 4, 2026 In the...

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-10-14 17:38 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...

2. monitoring 2026-10-14 18:46 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...

3. monitoring 2026-10-14 21:28 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...

4. monitoring 2026-10-15 20:18 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...

5. resolved 2026-10-16 22:35 UTC

   The issue has been resolved. Service remains stable, and data processing is operating as expected across the affected services. We apologize for the inconvenience and thank you for your patience while we resolved this issue.

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-10-09 17:42 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...

2. investigating 2026-10-09 18:49 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...

3. investigating 2026-10-09 19:53 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...

4. investigating 2026-10-09 20:57 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...

5. monitoring 2026-10-09 21:42 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 2026-10-10 07:15 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.

7. resolved 2026-10-12 14:26 UTC

   The issue affecting Gen3 apps and queries for our customers on US-East-1 has been resolved, and all services are operating normally. Thank you for your patience while we worked to resolve this issue.

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: AWS, Azure, Google Cloud.

1. identified 2026-10-07 14:54 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...

2. identified 2026-10-07 20:00 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...

3. monitoring 2026-10-07 22:13 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...

4. identified 2026-10-08 02:03 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...

5. identified 2026-10-08 05:19 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 2026-10-08 09:10 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...

7. resolved 2026-10-09 07:17 UTC

   We have completed the rollout of the updated OneAgent version across AWS, Azure, and GCP environments. The updated version addresses the Oracle compatibility issue that may have impacted customers using the Orabase command-line interface (CLI) tool with OneAgent version 1.347....

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: Google Cloud.

1. investigating 2026-10-01 13:35 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,...

2. investigating 2026-10-01 14:09 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...

3. monitoring 2026-10-01 15:07 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...

4. monitoring 2026-10-01 18:03 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...

5. resolved 2026-10-01 20:59 UTC

   Our cloud provider has confirmed that the service disruption affecting the GCP US-East region has been fully resolved. Telemetry ingestion has recovered, delayed log data has processed as expected, and related Dynatrace services are now stable. Our team has also validated...

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

1. investigating 2026-09-30 17:11 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...

2. investigating 2026-09-30 18:02 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;...

3. investigating 2026-09-30 20:09 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,...

4. investigating 2026-09-30 21:35 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...

5. investigating 2026-10-01 07:51 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...

6. resolved 2026-10-02 07:03 UTC

   The issue affecting EdgeConnect service availability has been resolved. Customers can now access EdgeConnect normally, and the previously communicated workaround is no longer required. We identified the underlying cause of the issue and restored service stability. Additional...

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. investigating 2026-09-30 11:33 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...

2. monitoring 2026-09-30 12:43 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...

3. resolved 2026-09-30 14:26 UTC

   This issue has been resolved. Processing of logs, metrics, and events has fully recovered, the backlog has been cleared, and ingestion is operating normally. During the incident, customers may have experienced delays in the ingestion and processing of logs, metrics, and events....

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by deepseek/deepseek-v4.1-flash with medium confidence (taxonomy v0.3).

Names an upstream provider: AWS, Azure, Google Cloud.

1. investigating 2026-09-25 21:57 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...

2. identified 2026-09-26 14:17 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...

3. identified 2026-09-28 10:13 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...

4. identified 2026-09-28 16:09 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...

5. identified 2026-09-28 20:22 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...

6. identified 2026-09-29 02:51 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...

7. identified 2026-09-29 07:13 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...

8. identified 2026-09-29 12:55 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...

9. identified 2026-09-29 15:45 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...

10. identified 2026-09-29 20:03 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...

11. identified 2026-09-29 22:59 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...

12. identified 2026-09-30 03:03 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...

13. identified 2026-09-30 06:53 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...

14. identified 2026-09-30 10:57 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...

15. identified 2026-09-30 18:40 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...

16. monitoring 2026-10-01 02:50 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...

17. resolved 2026-10-01 08:54 UTC

    Deployment of the fix for the issue affecting User Session Exports has been completed across all impacted environments. Monitoring confirms that the rollout was successful. The issue is now resolved. We apologize for the disruption and appreciate your patience throughout this...

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by deepseek/deepseek-v4.1-flash with low confidence (taxonomy v0.3).

1. investigating 2026-09-23 14:16 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,...

2. identified 2026-09-23 14:34 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....

3. monitoring 2026-09-23 14:59 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...

4. resolved 2026-09-23 15:53 UTC

   The service access issue affecting multiple regions has been resolved. Customers should no longer experience intermittent errors when logging in or accessing services in the affected regions, and data ingestion remained unaffected throughout the event. Our mitigation efforts,...

Excerpts are shortened. Read the full incident on Dynatrace's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by deepseek/deepseek-v4.1-flash with high confidence (taxonomy v0.3).

Names an upstream provider: AWS.

1. investigating 2026-09-16 15:16 UTC

   We are aware of an issue affecting 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...

2. identified 2026-09-16 15:56 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...

3. identified 2026-09-16 17:12 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...

4. monitoring 2026-09-16 19:40 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...

5. resolved 2026-09-16 21:06 UTC

   The issue affecting Dynatrace services in the IL-CENTRAL-1 Region has been resolved. AWS has completed remediation, and our teams have confirmed service recovery. We apologize for the disruption and appreciate your continued patience while service was restored.

Excerpts are shortened. Read the full incident on Dynatrace's status page.