Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Datadog US3 Outage History

Every past Datadog US3 outage tracked by IsDown, with detection times, duration, and resolution details.

There were 110 Datadog US3 outages since April 2021. The 25 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major May 29, 2026

May 2026: Increased latency across multiple products

Detected May 29, 2026 1:29 AM EDT · Resolved May 29, 2026 1:25 PM EDT · Duration about 12 hours

Datadog US3 experienced increased latency across multiple products including RUM, App Builder, Audit Trail, APM, Metrics and Infra Monitoring, and Monitors, causing delays in data across the platform for users. The incident was caused by an underlying Azure infrastructure event and lasted 11.9 hours. All services were fully recovered with APM requiring additional time for trace backfilling, and the incident was resolved while monitoring continued due to the ongoing infrastructure event.

Major May 28, 2026

May 2026: Delayed Metrics and Distributed Metrics

Detected May 28, 2026 4:07 AM EDT · Resolved May 28, 2026 5:10 AM EDT · Duration about 1 hour

Datadog US3 experienced delays in Metrics and Distributed Metrics processing that caused Monitor evaluations to be skipped. The incident affected Metrics and Infra Monitoring along with Monitors functionality for 1.1 hours. Mitigation was implemented and the service fully recovered.

Major May 15, 2026

May 2026: Azure Metrics Reporting

Detected May 15, 2026 10:19 PM EDT · Resolved May 15, 2026 11:46 PM EDT · Duration about 1 hour

Datadog US3 experienced a major incident where Azure metrics could not be submitted, affecting the Metrics and Infra Monitoring components for 1.4 hours. The issue was identified and a fix was implemented, with the service returning to normal operation and Azure metrics reporting as expected.

Minor April 29, 2026

April 2026: Failing queries for Cloud Networking and Service Checks

Detected Apr 29, 2026 10:19 AM EDT · Resolved Apr 29, 2026 1:25 PM EDT · Duration about 3 hours

Datadog US3 experienced failing queries for Cloud Networking and Service Checks that affected historical data older than April 29th 13:00 UTC, while recent data queries remained unaffected. The Cloud Network Monitoring component was impacted during this incident. The issue was identified, fixed, and resolved after 3.1 hours of service disruption.

Major April 29, 2026

April 2026: Elevated Error Rates for Monitors

Detected Apr 29, 2026 7:50 AM EDT · Resolved Apr 29, 2026 8:23 AM EDT · Duration 32 minutes

Datadog US3 experienced elevated error rates and increased latency in processing Service Check and Cloud Network Monitoring, causing users to see gaps, delays, or partial query results in their monitors. The incident lasted 32 minutes, with the underlying issue identified and a fix implemented. The service was fully restored with no data loss reported.

Minor March 17, 2026

March 2026: Delayed Logs

Detected Mar 17, 2026 12:44 PM EDT · Resolved Mar 17, 2026 1:19 PM EDT · Duration 36 minutes

Datadog US3 experienced increased latency in log processing for 36 minutes, causing delays and gaps in log query results for some users. The Log Management component was affected, and monitors related to delayed data were temporarily disabled to prevent false alerts. The underlying issue was identified and resolved with a deployed fix, with all delayed data being backfilled once service was restored.

Minor March 2, 2026

March 2026: Increased latency across multiple products

Detected Mar 2, 2026 2:52 PM EST · Resolved Mar 2, 2026 3:53 PM EST · Duration about 1 hour

Datadog US3 experienced increased latency across multiple products including APM, Log Management, Metrics and Infrastructure Monitoring, RUM, Database Monitoring, and Agent Repository, causing delays in data visibility across the platform. The latency issues affected users for approximately 1 hour before returning to normal levels. The incident was fully resolved after continued monitoring confirmed system stability.