Datadog US3 incident

Increased latency across multiple products

Minor Resolved View vendor source →

Datadog US3 experienced a minor incident on June 23, 2026 affecting APM and Metrics and Infra Monitoring and 1 more component, lasting 8h 46m. The incident has been resolved; the full update timeline is below.

Started
Jun 23, 2026, 09:09 PM UTC
Resolved
Jun 24, 2026, 05:56 AM UTC
Duration
8h 46m
Detected by Pingoru
Jun 23, 2026, 09:09 PM UTC

Affected components

APMMetrics and Infra MonitoringMonitorsRUM

Update timeline

  1. investigating Jun 23, 2026, 09:09 PM UTC

    We are investigating delays in monitor evaluation, which began at 20:50 UTC.

  2. investigating Jun 23, 2026, 09:23 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jun 23, 2026, 10:25 PM UTC

    We're continuing to investigate elevated error rates in the Datadog product. Monitor evaluations are continuing as normal. We will provide an update as soon as possible once the error rates have abated

  4. identified Jun 23, 2026, 11:28 PM UTC

    We have identified the cause of elevated error rates in the Datadog product and are continuing to work to mitigate them, monitor evaluations continue to operate as normal. We will provide another update once error rates have fully abated

  5. identified Jun 24, 2026, 02:35 AM UTC

    We have implemented mitigations and are seeing improvements; however, slightly elevated error rates persist across some Datadog products. We are actively working with our cloud infrastructure partner on further mitigations and will provide a further update within the next hour. We apologize for the continued impact.

  6. identified Jun 24, 2026, 03:52 AM UTC

    We are continuing to work with our cloud infrastructure partner on further mitigations and will provide a further update in the next hour. We apologize for the continued impact

  7. identified Jun 24, 2026, 04:35 AM UTC

    We are continuing to work with our cloud infrastructure partner on further mitigations and will provide a further update in the next hour. We apologize for the continued impact.

  8. monitoring Jun 24, 2026, 05:33 AM UTC

    A fix has been implemented and we are monitoring the results.

  9. resolved Jun 24, 2026, 05:56 AM UTC

    This incident has been resolved.