Datadog US1 had a metrics disruption lasting 2h 31m on 28 October 2026. Dashboards and metric queries were affected while data processing and alerts kept running, and the fault sat on Datadog's side.
Started
16:10 UTC
Duration
Lasted 2h 31m
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: Metrics and Infra Monitoring, Cloud Cost Management, Cloud Network Monitoring, RUM, APM, Monitors
What happened?
Datadog's status page opened an incident at 16:10 UTC titled "Metrics query are disrupted". The first update said some users might not be able to load dashboards or query metrics, and explicitly noted that data processing and alerts were not affected. Six components were listed as touched: Monitors, APM, Metrics and Infra Monitoring, Cloud Cost Management, Cloud Network Monitoring, and RUM. That spread suggests the fault sat in a shared query layer rather than in any single product, since metrics querying underpins all six. Datadog stayed in "investigating" status for over an hour, posting a second update at 16:40 UTC that added no new detail. At 17:26 UTC the status moved to "identified", over an hour after the first report. Monitoring began at 18:18 UTC, and the incident was marked resolved at 18:39 UTC, closing out at 2h 31m total. Datadog has not published a post-mortem explaining what the underlying fault actually was, so the cause beyond "metrics query disruption" is not on the record. No user reports were filed during the window. Over the past 90 days Datadog has logged 10 incidents with a median duration of 55 minutes, so this one ran well past typical.
Learning
This incident shows how a query-layer fault can ripple across a vendor's dashboard without taking down the underlying data pipeline, which is why Datadog could say alerts and processing kept working while you still couldn't see your own metrics on screen. If your own monitoring only checks that your services respond, or that Datadog's API accepts writes, it would have stayed green through this because the break was specifically in reading and rendering metrics back to you, not in collecting them. That's a layer most teams never instrument themselves, since it belongs entirely to the vendor. Over the trailing 30 days, UptimeRobot recorded 4 incidents against this provider with a median duration of 1h 38m, all resolved, which puts this 2h 31m incident above that recent median too. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.