Changes / Dynatrace / Data processing disruption on GCP US-East deployment

Dynatrace: Major incident: Data processing disruption on GCP US-East deployment

Summary

Summary pending. The diff below shows exactly what changed.

Major incidentLabel: major (vendor)Changed Detected Source: dynatrace.status.io (opens in new tab)

Incident page: full timeline of updates →

What changed

AddedTitle#1
Before: not present
After: Data processing disruption on GCP US-East deployment
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-10-01 13:35 UTC
AddedResolved time#5
Before: not present
After: 2026-10-01 20:59 UTC
AddedAffected components#6
Before: not present
After: Dynatrace Product
AddedUpdateinvestigating#7
Before: not present
After: 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.
AddedUpdateinvestigating#8
Before: not present
After: 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.
AddedUpdatemonitoring#9
Before: not present
After: 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.
AddedUpdatemonitoring#10
Before: not present
After: 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.
AddedUpdateresolved#11
Before: not present
After: 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.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

History of this incident

When (UTC)ChangeKind
Major incident: Data processing disruption on GCP US-East deployment (this change)Major incident

All Dynatrace changes → · Dynatrace profile · Markdown · JSON