Datadog incident: Delayed Traces in APM Trace Search

Affected components

• APM
• Monitors

1. resolvedFeb 11, 2026, 23:44 UTC

   This incident has been resolved.

2. monitoringFeb 11, 2026, 23:28 UTC

   A fix has been implemented and we are monitoring the results.

3. identifiedFeb 11, 2026, 22:28 UTC

   Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed. Distribution Metrics monitors were delayed between 21:35 and 22:15 UTC

4. identifiedFeb 11, 2026, 21:51 UTC

   Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed and Distribution Metrics monitors are delayed starting from 21:35 UTC

5. identifiedFeb 11, 2026, 21:18 UTC

   Teams have identified the issue and are working to mitigate at this time

6. investigatingFeb 11, 2026, 20:56 UTC

   We are investigating increased latency processing Traces in APM Trace Search. As a result of this issue, some users may see missing or delayed traces in APM Trace Search and delayed APM Trace Monitors since 21:30 UTC.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Datadog's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: All new cluster creations in Azure westus3, southcentralus, and eastus2 are failingMajor · Feb 11, 2026, 22:14 UTC
• LaunchDarkly: Observability – Degraded OTel Telemetry ProcessingMinor · Feb 11, 2026, 13:03 UTC

How often does Datadog have incidents?

Datadog reported 12 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 47 min. See Datadog's uptime and incident history