Official provider signal

Is Datadog US1 down?

Datadog's US1 site: metric and log intake, dashboards, monitors and APM. Other Datadog sites publish their own status and are not covered here.

Operational

Current status

Components

APM
Application Performance Monitoring (services and traces)
Operational
App Builder
Operational
Application Security Management
Operational
Application Vulnerability Management
Operational
Audit Trail
Operational
Bits AI
Operational
CI Visibility
Operational
Cloud Cost Management
Operational
Cloud Network Monitoring
Operational
Cloud Security Management
Operational
Cloud SIEM
Operational
Code Coverage
Operational
Code Security
Operational
Container Registry
Operational
Continuous Profiler
Operational
Database Monitoring
Operational
Data Jobs Monitoring
Operational
Data Streams Monitoring
APM / Data Streams Monitoring
Operational
Error Tracking
Operational
Incident Response
Operational
LLM Observability
Operational
Log Management
Operational
Metrics and Infra Monitoring
Operational
Mobile Application
Operational
Monitors
Operational
NDM
Network Device Monitoring
Operational
Observability Pipelines
Operational
Package Repositories
Operational
Product Analytics
Operational
RUM
Real User Monitoring
Operational
Sensitive Data Scanner
Operational
Serverless
Serverless Workload Monitoring
Operational
Synthetics
Synthetic Monitoring
Operational
Test Optimization
Operational
Universal Service Monitoring
Operational
Web Application
Operational
Workflow Automation
Operational
Workload Protection
Operational
www.datadoghq.com
Our public site, hosting our documentation for using Datadog.
Operational

Official timeline

Active incidents

incidentDelayed Monitors Notifications
monitoring
Timeline →
incidentDelayed events triggered by emails
investigating
Timeline →

Data confidence

Source & freshness

Source: Datadog US1 Status ↗
Collected: Sep 23, 2026, 6:37 PM UTC
Provider updated: Sep 23, 2026, 6:35 PM UTC

Operational means no issue is currently reported by the provider. It is not proof that every user or region is unaffected.

While this is open

What should I check next?

Read the incident timeline. The provider updates say what is affected and what they have already ruled out.
Match the affected components against the calls your system actually makes before assuming this incident is yours.
Hold off on rolling back your own deploy. A rollback during a provider incident removes a variable you will want later.
Queue or fail over the work if you can. Aggressive retries against a degraded provider usually make the backlog worse.
Watch the timeline rather than polling the API. It updates as the provider posts, including the resolution.