Datadog favicon

Datadog US1 outage on 2026-10-26

datadoghq.com
October 2026 26 Major incident

Datadog's US1 region hit elevated error rates for 58 minutes on 26 October, affecting App Builder and Workflow Automation along with Bits Code and Agent Builder. The fault sat on Datadog's side and was confirmed and fixed by their own engineering team.

Started

17:26 UTC

Duration

Lasted 58m

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: App Builder, Workflow Automation

What happened?

Datadog opened an incident at 17:26 UTC covering Workflow Automation, App Builder, Bits Code and Agent Builder in the US1 datacenter. Their notice was specific about the symptom: workflows containing JavaScript or Python actions failing to run, including those used for incident and on-call automation, App Builder apps using JavaScript or Python failing or behaving unexpectedly, Bits Code sessions failing to start or complete, and Agent Builder agents with Bits Code enabled unable to start code sessions or use bash tools. Four minutes later, at 17:30 UTC, Datadog said they had identified the underlying issue and were working on a fix. By 17:40 UTC they had deployed that fix and moved to monitoring. The incident closed at 18:23 UTC, 58 minutes after it opened, with a single line: the issue is now resolved. Datadog's status page does not say what the underlying issue actually was, so the cause is not on the record beyond "identified and fixed". No user reports were filed during the window on this page. This was Datadog's own filing throughout, with no third party confirmation, so the 58 minute duration and the component list both rest entirely on what Datadog chose to publish. Over the past 90 days Datadog has logged 11 incidents with a median duration of 52 minutes, so this one ran slightly longer than typical but not far off. Across all time Datadog averages 4.2 incidents a month, putting this squarely in the pattern rather than as an outlier.

Learning

This incident sat inside Datadog's own application layer, in the code execution paths behind App Builder, Workflow Automation, Bits Code and Agent Builder, not in basic reachability of the US1 endpoint. That's a layer an external uptime check on your own product would never see, because your probes test whether your service responds, not whether a third party's internal JavaScript or Python execution is working underneath it. UptimeRobot's own 30 day data shows 3 incidents against Datadog US1 with a median duration of 58 minutes, almost identical to this one, meaning external monitoring aimed at the provider itself catches this pattern reliably even when your own checks stay green. If your workflows or on-call automation depend on Datadog's JavaScript or Python actions, this kind of failure looks like your automation silently not firing, with nothing to show in your own dashboards. That's the gap: your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.