Where does this status come from?

From Datadog's own status page API at https://status.datadoghq.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Datadog's words.

How can my agent or app check Datadog status?

Fetch https://upbutler.com/status/datadog/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"datadog"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Datadog's?

Add "datadog" to the dependencies of your UpButler workspace. When one of your monitors fails while Datadog has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Datadog down?

Right now

No. Datadog is operational.

No incidents reported.

Read from status.datadoghq.com 2 min ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/datadog/status.agent.json

MCP: upstream_status {"service":"datadog"}

Metrics, logs, traces and monitors (US1 site).

What Datadog reports

Operational

Taken as is from Datadog's own status page API. Incident titles and component names below are theirs.

Open status.datadoghq.com

UpButler's independent probe

There is no keyless endpoint of Datadog that says anything useful, so UpButler does not probe it. To check your own Datadog account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Datadog components

40 operational

APMOperational
App BuilderOperational
Application Security ManagementOperational
Application Vulnerability ManagementOperational
Audit TrailOperational
Bits AIOperational
CI VisibilityOperational
Cloud Cost ManagementOperational
Cloud Network MonitoringOperational
Cloud Security ManagementOperational
Cloud SIEMOperational
Code CoverageOperational
Code SecurityOperational
Container RegistryOperational
Continuous ProfilerOperational
Database MonitoringOperational
Data Jobs MonitoringOperational
Data Streams MonitoringOperational
Error TrackingOperational
Event ManagementOperational
Incident ResponseOperational
LLM ObservabilityOperational
Log ManagementOperational
Metrics and Infra MonitoringOperational
Mobile ApplicationOperational
MonitorsOperational
NDMOperational
Observability PipelinesOperational
Package RepositoriesOperational
Product AnalyticsOperational
RUMOperational
Sensitive Data ScannerOperational
ServerlessOperational
SyntheticsOperational
Test OptimizationOperational
Universal Service MonitoringOperational
Web ApplicationOperational
Workflow AutomationOperational
Workload ProtectionOperational
www.datadoghq.comOperational

Datadog incidents, last 90 days

2 finished incidents seen since UpButler started tracking on 2026-10-10.

Started (UTC)	Incident	Impact	Lasted
2026-10-02 12:46	Delayed RUM sessions	none	2 h 17 min
2026-09-30 18:02	Delayed Events	minor	48 min

Tell your outage from Datadog's

Declare that your project depends on Datadog. When one of your monitors fails while Datadog has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - datadog

Ask before you retry

curl -s https://upbutler.com/status/datadog/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "datadog",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Datadog down right now?: No. As of 2026-10-10 05:10 UTC, Datadog is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Datadog's own status page API at https://status.datadoghq.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Datadog's words.
How can my agent or app check Datadog status?: Fetch https://upbutler.com/status/datadog/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"datadog"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Datadog's?: Add "datadog" to the dependencies of your UpButler workspace. When one of your monitors fails while Datadog has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in observability and analytics

UpButler is not affiliated with Datadog. Status and incident text belong to Datadog and are read from their public status source; the probe result is UpButler's own measurement.