Datadog's RUM pipeline fell behind starting at 12:46 UTC on 2 October 2026, leaving you with gaps or delays in RUM graphs and partial query results. The delay originated inside Datadog's own session processing, not in anything you run.
Started
12:46 UTC
Duration
Ongoing
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: RUM
What happened?
Datadog opened this incident at 12:46 UTC, reporting increased latency processing RUM sessions. The filing says the underlying data lag actually began earlier, at 11:42 UTC on 2 October, before Datadog had posted anything. During the window, RUM Sessions, RUM Analytics and RUM Application pages could show empty or partial results, and graphs could show gaps. Datadog also noted that monitors affected by the delay would not notify and would resume automatically once current data arrived, while other monitors kept operating normally. At 13:23 UTC Datadog posted a second update saying the issue had been identified, that they were seeing signs of recovery, and that they were monitoring. No further update has been published since, so the incident remains open on Datadog's own status page as of that last note. Only one component is listed as affected: RUM. No other Datadog service is named in this filing. No user reports were filed during this window, so there is nothing from the field to cross-check against Datadog's account. Datadog has not published a post-mortem, and the record does not say what caused the latency in the first place. Over the past 90 days Datadog has logged 13 incidents with a median duration of 51 minutes, and across all time it averages 4.3 incidents a month, so this kind of delay is not unusual for the service.
Learning
This incident sat inside Datadog's own RUM ingestion pipeline, the layer that collects, processes and renders session data after it leaves your application. If your product was sending RUM events normally during this window, your own instrumentation would show nothing wrong, because the delay happened downstream, inside Datadog's processing, not in your code or your network path. That is why an uptime check hitting your endpoints can stay green while your RUM dashboards show gaps: the two are watching different layers, and both readings can be correct at once. Datadog itself flagged this risk by disabling notifications on monitors affected by the delay, which tells you the company expected its own alerting to be unreliable during the window. Over Datadog's last 30 days, 6 incidents were logged with a median duration of 51 minutes, and 5 of those were resolved, so this pattern of delay and recovery is a recurring shape rather than a one-off. Your monitoring covers your half of the picture, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
