Data processing disruption on GCP US-East deployment

What to do

• Check whether you use Dynatrace in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 0m it lasted.

  Anything that failed between 2026-10-01 20:59 UTC and 2026-10-01 20:59 UTC may need a replay.

• Subscribe to Dynatrace's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=dynatrace works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Root cause

The root cause points to a service disruption on our cloud provider’s side, which has since subsided.

Category: Upstream dependency

Updates from Dynatrace 1

1. resolvedOct 1, 2026, 8:59 PM UTC

   October 1, 2026 1:35PM UTC Investigating - 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. October 1, 2026 2:09PM UTC Investigating - 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. October 1, 2026 3:07PM UTC Monitoring - 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. October 1, 2026 6:03PM UTC Monitoring - 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. October 1, 2026 8:59PM UTC Resolved - 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 sustained stability across the impacted services.  We appreciate your patience while we resolved this incident.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.