Delayed Events

What to do

• Check whether your product depends on Datadog. 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-09-30 18:51 UTC and 2026-09-30 18:51 UTC may need a replay.

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

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

Root cause

To prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available.

Updates from Datadog 1

1. resolvedSep 30, 2026, 6:51 PM UTC

   Sep 30, 18:51 UTC Resolved - The issue is now resolved. Sep 30, 18:29 UTC Monitoring - We have deployed a mitigation and we are monitoring the results. Sep 30, 18:05 UTC Identified - We have identified the issue and are working on a mitigation strategy. Sep 30, 18:02 UTC Investigating - We are investigating increased latency processing Events generated by RUM, Trace Analytics, Service Checks, CI Visibility, Cloud Network Monitoring, and Error Tracking. As a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards since Sep 30, 2026, 5:25 PM UTC To prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once current data is available. All other monitors will operate normally.

   provider

Corrections

None so far.

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