Datadog's US1 region had a 51-minute event processing delay on 30 September 2026, affecting APM, CI Visibility, Cloud Network Monitoring and RUM. The fault was Datadog's own event pipeline, not anything in your product.
Started
18:02 UTC
Duration
Lasted 51m
Source
IsDown
Next time
Datadog is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: APM, CI Visibility, Cloud Network Monitoring, RUM
What happened?
Datadog opened an incident at 18:02 UTC for increased latency processing events across RUM, Trace Analytics, Service Checks, CI Visibility, Cloud Network Monitoring and Error Tracking. Datadog's own note says the delay had actually begun earlier, at 17:25 UTC, meaning their status page lagged the real start by 37 minutes. The visible symptom for you would have been delays or gaps in the event stream, or missing data on dashboard queries, rather than a hard outage. Datadog said monitors affected by the delay would not notify and would resume automatically once data caught up, while all other monitors kept operating normally. At 18:05 UTC Datadog said the issue was identified, at 18:29 UTC they said a mitigation had been deployed and they were monitoring results, and at 18:51 UTC they marked it resolved. That gives a total incident length of 51 minutes from Datadog's own stated start time. No cause is given beyond "we have identified the issue", so what actually broke in their pipeline is not on the record. No post-mortem has been published for this incident. No user reports were filed during the window, so the only account of impact is Datadog's own four status updates. This is the twelfth incident Datadog has logged on US1 in the past 90 days, with a median duration of 51 minutes, so this one lands exactly on their usual pattern. Across all time Datadog has logged 328 incidents on this service, averaging 4.3 per month.
Learning
This incident sat in Datadog's event processing layer, the pipeline that takes in RUM, APM and CI Visibility data and turns it into dashboards and alerts, not in the reachability of the Datadog API or UI itself. That is why a basic uptime check against Datadog's endpoints could have stayed green the whole time while your actual monitors on dashboards were showing gaps or stale data. Datadog's own mitigation of suppressing alerts from affected monitors during the delay is a tell: they knew their own alerting couldn't be trusted during this window either. For your own product built on top of Datadog, the risk isn't that Datadog goes down, it's that your dashboards quietly fall behind while everything looks nominal. Watching your own endpoints only tells you your side is fine, it says nothing about whether the data flowing through Datadog is current. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
