# Dynatrace: Major incident: Issue with Dynatrace Platform

**Summary:** Dynatrace reported a major authentication issue affecting service access and potentially causing data processing and extraction errors or delays; ingestion continued. The incident started at 2026-09-01 11:54 UTC and was resolved at 2026-09-03 14:10 UTC, lasting 2 days 2 h, with normal operation verified after extended monitoring. _(machine-written, sol)_
- Kind: Major incident · Label: outage (model (Jev))
- Changed: 2026-09-01 11:54 UTC · Detected: 2026-10-18 05:07 UTC
- [Source: https://dynatrace.status.io/pages/incident/546d8cb6af8407b6730000cb/6a96bcf4df35e104e603060f](https://dynatrace.status.io/pages/incident/546d8cb6af8407b6730000cb/6a96bcf4df35e104e603060f)
- [Company: Dynatrace](https://rewindex.com/company/dynatrace.md)
- Versions: before (none: first archived) → after incident\_version:275/6a96bcf4df35e104e603060f@6fc68b539595
- Change 1 of 1 for this incident

Incident page (full timeline): [Issue with Dynatrace Platform](https://rewindex.com/company/dynatrace/incidents/6a96bcf4df35e104e603060f.md)
## What changed

**1. Added: Title**

```diff
+ Issue with Dynatrace Platform
```

**2. Added: Impact**

```diff
+ major
```

**3. Added: Status**

```diff
+ resolved
```

**4. Added: Start time**

```diff
+ 2026-09-01 11:54 UTC
```

**5. Added: Resolved time**

```diff
+ 2026-09-03 14:10 UTC
```

**6. Added: Affected components**

```diff
+ Dynatrace Product
```

**7. Added: Update** (investigating) · 2026-09-01 11:54 UTC

```diff
+ 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.
```

**8. Added: Update** (investigating) · 2026-09-01 12:13 UTC

```diff
+ 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.
```

**9. Added: Update** (identified) · 2026-09-01 12:41 UTC

```diff
+ 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.
```

**10. Added: Update** (identified) · 2026-09-01 13:10 UTC

```diff
+ 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.
```

**11. Added: Update** (identified) · 2026-09-01 13:41 UTC

```diff
+ 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.
```

**12. Added: Update** (identified) · 2026-09-01 14:11 UTC

```diff
+ 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.
```

**13. Added: Update** (identified) · 2026-09-01 14:45 UTC

```diff
+ 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.
```

**14. Added: Update** (identified) · 2026-09-01 15:14 UTC

```diff
+ 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.
```

**15. Added: Update** (identified) · 2026-09-01 15:47 UTC

```diff
+ 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.
```

**16. Added: Update** (identified) · 2026-09-01 16:19 UTC

```diff
+ We continue to make progress in mitigating the issue affecting Dynatrace Platform. 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.
```

**17. Added: Update** (identified) · 2026-09-01 16:53 UTC

```diff
+ 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.
```

**18. Added: Update** (identified) · 2026-09-01 17:35 UTC

```diff
+ 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.
```

**19. Added: Update** (identified) · 2026-09-01 18:10 UTC

```diff
+ 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.
```

**20. Added: Update** (identified) · 2026-09-01 18:42 UTC

```diff
+ 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.
```

**21. Added: Update** (identified) · 2026-09-01 19:24 UTC

```diff
+ 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.
```

**22. Added: Update** (identified) · 2026-09-01 20:31 UTC

```diff
+ 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.
```

**23. Added: Update** (identified) · 2026-09-01 21:03 UTC

```diff
+ 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.
```

**24. Added: Update** (identified) · 2026-09-01 21:34 UTC

```diff
+ 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.
```

**25. Added: Update** (identified) · 2026-09-01 22:20 UTC

```diff
+ 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.
```

**26. Added: Update** (identified) · 2026-09-01 23:07 UTC

```diff
+ 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.
```

**27. Added: Update** (identified) · 2026-09-01 23:47 UTC

```diff
+ 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.
```

**28. Added: Update** (monitoring) · 2026-09-02 00:27 UTC

```diff
+ 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.
```

**29. Added: Update** (monitoring) · 2026-09-02 01:08 UTC

```diff
+ 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.
```

**30. Added: Update** (monitoring) · 2026-09-02 02:01 UTC

```diff
+ 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.
```

**31. Added: Update** (monitoring) · 2026-09-02 03:12 UTC

```diff
+ 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.
```

**32. Added: Update** (monitoring) · 2026-09-02 04:55 UTC

```diff
+ 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.
```

**33. Added: Update** (monitoring) · 2026-09-02 06:01 UTC

```diff
+ 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.
```

**34. Added: Update** (monitoring) · 2026-09-02 07:04 UTC

```diff
+ 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.
```

**35. Added: Update** (monitoring) · 2026-09-02 08:10 UTC

```diff
+ 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.
```

**36. Added: Update** (monitoring) · 2026-09-02 10:12 UTC

```diff
+ 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.
```

**37. Added: Update** (monitoring) · 2026-09-02 12:21 UTC

```diff
+ 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.
```

**38. Added: Update** (monitoring) · 2026-09-02 14:14 UTC

```diff
+ 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.
```

**39. Added: Update** (monitoring) · 2026-09-02 18:37 UTC

```diff
+ 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.
```

**40. Added: Update** (monitoring) · 2026-09-02 22:52 UTC

```diff
+ 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.
```

**41. Added: Update** (monitoring) · 2026-09-03 02:31 UTC

```diff
+ 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.
```

**42. Added: Update** (monitoring) · 2026-09-03 06:29 UTC

```diff
+ 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.
```

**43. Added: Update** (monitoring) · 2026-09-03 10:12 UTC

```diff
+ 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.
```

**44. Added: Update** (resolved) · 2026-09-03 14:10 UTC

```diff
+ The issue affecting the Dynatrace Platform has been resolved. All affected services remained stable throughout the extended monitoring period, and verification activities have confirmed that services are operating normally We truly apologize for the disruption this caused and recognize the impact it may have had on your operations. Thank you for your patience, understanding, and partnership as we worked with urgency toward resolution.
```

## History of this incident

| When (UTC) | Change | Label |
| --- | --- | --- |
| 2026-09-01 11:54 UTC | Major incident: Issue with Dynatrace Platform (this change) | outage |

All Dynatrace changes: [timeline](https://rewindex.com/company/dynatrace/changes.md)
_Diff excerpts are shown on normalized text: dates, counters and tokens appear as ‹date›, ‹count›, ‹tok›; noise-only edits are hidden. Rewindex shows the changed passages, not a copy of the page._


---
Canonical: https://rewindex.com/change/i0d14760dac9961 · Markdown: https://rewindex.com/change/i0d14760dac9961.md · JSON: https://rewindex.com/api/v1/changes/i0d14760dac9961 · Generated 2026-10-18T11:25:21.724Z