Is Dynatrace Down?

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. --- [2026-10-01T14:09:04.249Z] (400) 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. --- [2026-10-01T15:07:32.818Z] (100) 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. --- [2026-10-01T18:03:21.194Z] (100) 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.

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. --- [2026-09-30T18:02:45.524Z] (400) 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. --- [2026-09-30T20:09:45.053Z] (400) 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. --- [2026-09-30T21:35:04.516Z] (400) 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. --- [2026-10-01T07:51:36.810Z] (100) 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.

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. --- [2026-09-30T12:43:05.667Z] (100) 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.