Is Datadog Down? How to Check Datadog Status Right Now

Statusfield Team
7 min read

Datadog dashboards not loading, monitors not alerting, or APM traces missing? Learn how to check if Datadog is down right now, which components can fail independently, and how to get instant outage alerts.

Datadog is the observability platform for engineering and operations teams — metrics, traces, logs, and alerting in one place. When Datadog goes down, you lose the visibility you depend on to manage your own infrastructure. Dashboards go dark, alerts stop firing, and on-call rotations become blind. Here's how to determine if Datadog is down and what to check.

Is Datadog Down Right Now?

Check these in order:

  1. Statusfield — Datadog status — real-time monitoring of Datadog's platform health.
  2. Datadog's official status pagestatus.datadoghq.com publishes active incidents by product and region.
  3. Twitter/X — search datadog down sorted by Latest. SREs and platform engineers report issues quickly, especially during active incidents.
  4. Datadog Community Slack — many engineering teams share incident reports in Datadog's community Slack channels.

Datadog Products That Can Fail Independently

Datadog is a multi-product platform — outages can affect one product without impacting others:

ProductWhat breaks when it fails
MetricsTime-series data stops ingesting; dashboards show gaps or flat lines
APM & Distributed TracingTraces stop arriving; service maps become stale; latency breakdowns unavailable
Log ManagementLogs stop indexing; log-based monitors stop alerting; search returns stale results
Infrastructure MonitoringHost maps show offline agents; resource utilization charts go flat
Monitors & AlertingAlert conditions evaluate but notifications stop sending; PagerDuty/Slack integrations break
SyntheticsUptime checks and browser tests stop running; SLA data becomes inaccurate
RUM (Real User Monitoring)Frontend session data stops ingesting; Core Web Vitals charts go stale
CI VisibilityPipeline and test data stops flowing; build performance dashboards go blank
Database MonitoringQuery metrics and execution plans stop updating

Common Errors During a Datadog Outage

ErrorLikely cause
Dashboard shows "No data" or flat linesMetrics ingestion pipeline degraded
Monitors not firing despite known conditionsMonitor evaluation or notification pipeline degraded
Traces not appearing in APMTrace intake or indexing degraded
Logs returning "No results" for active servicesLog ingestion or indexing degraded
Datadog agent: WARN Error: API request failedDatadog API endpoint degraded; agent retrying
Alert notification sent but no Slack/PagerDuty messageWebhook delivery service degraded
Synthetic tests showing "Agent unreachable"Synthetic worker infrastructure degraded
Login page returns 503 or timeoutAuthentication service or edge infrastructure degraded

The Paradox: Your Monitoring Tool Is Down

Datadog outages create a specific problem: the tool you rely on to know when things break is itself broken. Engineering teams need a plan for this scenario:

  1. Redundant alerting — use a secondary alert path (status page monitoring, Statusfield) that doesn't depend on Datadog to deliver notifications
  2. Agent-side visibility — the Datadog agent logs its own state locally; check /var/log/datadog/agent.log for submission errors and queue size
  3. Direct metric sources — fall back to CloudWatch, Prometheus, or your cloud provider's native monitoring during an extended Datadog outage
  4. Status page subscriptions — subscribe to Datadog's status page at status.datadoghq.com for email/SMS notifications

Datadog Agent Behavior During Outages

The Datadog agent continues to collect metrics from your hosts even when the Datadog backend is degraded. Understanding what happens:

  • Metric buffer — the agent buffers unsent metrics in memory; the default buffer allows approximately 5 minutes of data to queue before dropping
  • Log forwarding — the agent's log forwarder also buffers; logs collected during the outage may be replayed after recovery depending on the buffer size and outage duration
  • Trace agent — APM traces have a separate buffer; long outages result in trace loss rather than delayed delivery
  • No agent restart needed — once the Datadog backend recovers, the agent resumes sending automatically; you do not need to restart or reconfigure the agent

Check agent health after an outage: datadog-agent status will show whether metrics, logs, and traces are flowing normally.

Datadog Monitors and PagerDuty During Outages

Datadog Monitors power on-call alerting for most SRE teams. During a monitor evaluation or notification outage:

  • Alert conditions may still evaluate — the evaluation pipeline is separate from the notification delivery pipeline; monitors may transition state without sending notifications
  • PagerDuty incidents may not be created — if Datadog's webhook delivery to PagerDuty fails, no incident is opened, even if a monitor fires
  • Recovery alerts may not send — teams may receive a delayed burst of recovery notifications after the outage resolves as queued deliveries flush

For critical on-call workflows, configure a backup alerting path in PagerDuty or use Statusfield to monitor Datadog itself and alert your on-call when the monitoring platform goes dark.

Datadog Regional Deployments

Datadog operates regional deployments. If you're on the EU or GovCloud region, check the appropriate status page:

RegionStatus PageStatusfield
US1 (default)status.datadoghq.comStatusfield US1
EU1status.datadoghq.euStatusfield EU
US3 / US5 / AP1Check your Datadog portal for region-specific status

US region incidents don't automatically affect EU, and vice versa. Always check the status page for your specific Datadog region.

How to Get Instant Datadog Outage Alerts

If Datadog goes down, your existing Datadog monitors won't tell you — they're part of the same platform that's failing. You need an independent monitoring layer.

Monitor Datadog on Statusfield — Statusfield monitors Datadog's platform health independently and sends an alert the moment any component changes. Route to email or a webhook into your on-call tool so you know Datadog is degraded before your engineers start wondering why dashboards are flat.

Start monitoring Datadog on Statusfield → — free, no credit card required.


Frequently Asked Questions

Is Datadog down for everyone or just me?

Check Statusfield or status.datadoghq.com. If Datadog's status page shows fully operational but you're seeing data gaps, the issue may be with your Datadog agent (check datadog-agent status), your network, or a specific integration pipeline that's degraded without a platform-wide incident being declared.

Datadog dashboards show "No data" but services are running — is this an outage?

Check status.datadoghq.com for the Metrics or Infrastructure components. "No data" can also be caused by a misconfigured time window, an agent version upgrade that broke tags, or a monitor threshold that excludes the current value. If the platform is healthy, run datadog-agent check disk (or another check) to confirm the agent is collecting data locally.

My Datadog monitors aren't firing — alerts aren't reaching PagerDuty

This can mean the monitor hasn't triggered (check evaluation in the Monitor detail view), the notification channel has a delivery issue (Datadog → PagerDuty webhook failing), or Datadog's notification pipeline is degraded. Check status.datadoghq.com for the Monitors and Webhooks components. Temporarily test with a manual test notification from the PagerDuty integration settings.

Can I use Datadog while one product is degraded?

Usually yes — Datadog's products share some backend infrastructure but degrade independently. If only Log Management is listed as degraded, metrics and APM typically continue normally. Check the specific product component on the status page before concluding that the full platform is unusable.

The Datadog agent is reporting errors — is this a Datadog outage or my configuration?

Run datadog-agent status to see the current state of each check. Look for API key validation failures (authentication issue), endpoint connection refused (network or endpoint down), or specific check failures (configuration issue). If multiple hosts report the same error at the same time, it's likely a Datadog-side issue. If only one host is affected, it's more likely local.

How often does Datadog go down?

Datadog publishes full incident history at status.datadoghq.com. Major full-platform outages are rare, but partial degradations — particularly for log ingestion, metrics at scale, and APM indexing — occur periodically. For SRE teams and platform engineers, monitoring Datadog independently provides the critical safety net that Datadog itself can't provide for its own failures.

Published: April 13, 2026. Check current Datadog status →