Datadog

Affected: RUM

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-10-02 12:46 UTC

   We are investigating increased latency processing RUM sessions. As a result of this issue, some users may see gaps or delays in RUM graphs as well as empty or partial query results on RUM Sessions, RUM Analytics, and RUM Application pages since Oct 2, 2026, 11:42 AM UTC To...

2. monitoring 2026-10-02 13:23 UTC

   The issue has been identified we're seeing signs of recovery and we are monitoring the issue.

3. monitoring 2026-10-02 13:47 UTC

   Latency has now resolved and monitors evaluation is being back to normal. We are still monitoring the issue for now.

4. resolved 2026-10-02 15:03 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, CI Visibility, Cloud Network Monitoring, Error Tracking, RUM

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-30 18:02 UTC

   We are investigating increased latency processing Events generated by RUM, Trace Analytics, Service Checks, CI Visibility, Cloud Network Monitoring, and Error Tracking. As a result of this issue, some users may see delays or gaps in the event stream or for event queries on...

2. identified 2026-09-30 18:05 UTC

   We have identified the issue and are working on a mitigation strategy.

3. monitoring 2026-09-30 18:29 UTC

   We have deployed a mitigation and we are monitoring the results.

4. resolved 2026-09-30 18:51 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Incident Response

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-25 15:11 UTC

   We are investigating an issue with users unable to acknowledge on call pages

2. investigating 2026-09-25 15:17 UTC

   We are investigating an issue with users unable to acknowledge, escalate, or resolve On-Call Pages.

3. identified 2026-09-25 15:23 UTC

   We have identified the issue with pages and are applying mitigations.

4. monitoring 2026-09-25 15:29 UTC

   We are monitoring the issue.

5. resolved 2026-09-25 15:38 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-21 09:44 UTC

   We are investigating delayed evaluations for metric, service check, composite, and SLO monitors in US1 which began at Sep 21, 2026, 9:18 AM UTC.

2. identified 2026-09-21 10:00 UTC

   We identified the issue and is working on a fix.

3. monitoring 2026-09-21 10:22 UTC

   We are monitoring the issue.

4. resolved 2026-09-21 10:30 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Incident Response

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-20 05:17 UTC

   We are investigating increased latency processing Events coming from inbound emails. As a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards and for events based workflows such as on-call notifications

2. resolved 2026-09-20 06:53 UTC

   The issue is now resolved. All events from emails are being timely processed and we went through the backfill.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: CI Visibility

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-03 17:20 UTC

   We are investigating increased latency processing CICD Optimization, Code Coverage, Code Security, and DORA data. As a result of this issue, some users may see delays with test runs and pipeline executions.

2. identified 2026-09-03 17:27 UTC

   We identified the issue.

3. monitoring 2026-09-03 17:45 UTC

   We are monitoring the issue.

4. identified 2026-09-03 17:59 UTC

   We identified the issue.

5. monitoring 2026-09-03 19:01 UTC

   We are monitoring the issue.

6. monitoring 2026-09-03 21:51 UTC

   We have applied remediations, and recovery is in progress. We are continuing to monitor the issue.

7. resolved 2026-09-03 23:01 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Database Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-02 01:07 UTC

   We are investigating delays in monitor evaluation, which began at Sep 2, 2026, 12:10 AM UTC.

2. identified 2026-09-02 01:16 UTC

   We identified the issue.

3. monitoring 2026-09-02 01:21 UTC

   We are monitoring the issue.

4. resolved 2026-09-02 01:24 UTC

   The issue is now resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-08-06 18:51 UTC

   We are investigating increased latency processing Processes data. As a result of this issue, some users may see delays or gaps for data based on Live Process Monitoring. To prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will...

2. identified 2026-08-06 19:18 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-08-06 19:27 UTC

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

4. resolved 2026-08-06 19:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-30 07:44 UTC

   We are investigating delays in Service Check monitors evaluation, which began at 6:35AM UTC.

2. identified 2026-07-30 07:49 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-30 08:16 UTC

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

4. resolved 2026-07-30 08:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring, Monitors, RUM

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-29 15:41 UTC

   We are currently investigating an issue delaying the ingestion of Real User Monitoring (RUM) measure metrics, custom process metrics, and a subset of distribution metrics for some customers. As a result, some users may see delays or gaps in RUM, custom process, and distribution...

2. investigating 2026-07-29 15:42 UTC

   We are continuing to investigate this issue.

3. identified 2026-07-29 16:35 UTC

   The issue has been identified and a fix is being implemented.

4. identified 2026-07-29 16:53 UTC

   The RUM delays have been resolved. We're continuing to mitigate the issues on distribution metrics.

5. monitoring 2026-07-29 17:12 UTC

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

6. resolved 2026-07-29 17:28 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Synthetics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-27 19:05 UTC

   We are currenting investigating an issue running Synthetic tests.

2. investigating 2026-07-27 19:25 UTC

   We're continuing to investigate an issue publishing Synthetic results. Synthetic tests are running and results are delayed.

3. identified 2026-07-27 19:36 UTC

   We've identified the issue publishing Synthetic results. Synthetic tests are continuing to run with delayed results.

4. monitoring 2026-07-27 19:46 UTC

   A fix has been implemented and we're monitoring the results.

5. resolved 2026-07-27 19:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-23 17:08 UTC

   We are investigating increased latency with Pages and Monitor state changes. As a result of this issue, some users may see delays.

2. identified 2026-07-23 17:31 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-23 18:02 UTC

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

4. resolved 2026-07-23 18:13 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Data Streams Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-10 14:09 UTC

   We are currently investigating an issue affecting Data Streams Monitoring (DSM) in our US1 datacenter. As a result, data stream latency metrics may be delayed or not updating for some users. If you have monitors configured on those metrics, they may fail to alert as expected...

2. investigating 2026-07-10 14:35 UTC

   We are continuing to investigate the issue.

3. monitoring 2026-07-10 15:18 UTC

   A fix has been implemented and we are monitoring the results. A small percentage of data sent between 6:23 UTC and 14:43 UTC is still being backfilled.

4. resolved 2026-07-10 15:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Container Registry

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-07-03 00:25 UTC

   We are investigating errors pulling Datadog container images from registry.datadoghq.com. As a result of this issue, some users may be unable to download or deploy the Datadog Agent, Cluster Agent, and other Datadog container images. Containers that are already running are not...

2. identified 2026-07-03 00:55 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-07-03 01:21 UTC

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

4. resolved 2026-07-03 01:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-07-01 18:31 UTC

   We are actively investigating elevated error rates across multiple Datadog products.

2. investigating 2026-07-01 18:57 UTC

   We are investigating elevated error rates across multiple products including: Fleet Automation, Security Products, Cloudcraft, Cloud Network Monitoring, Serverless, Kubernetes Autoscaling, and Database Monitoring.

3. identified 2026-07-01 19:10 UTC

   We have identified the issue of elevated error rates and are working through mitigation actions

4. monitoring 2026-07-01 19:19 UTC

   We have deployed mitigation actions and are monitoring the recovery.

5. monitoring 2026-07-01 19:43 UTC

   We are continuing to monitor the situation and are taking additional preventive measures.

6. resolved 2026-07-01 20:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, CI Visibility, Code Coverage, Database Monitoring, Error Tracking, Observability Pipelines, RUM, Synthetics, Test Optimization

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-30 17:51 UTC

   We are currently investigating an issue affecting CI Visibility, Test Optimization, Code Coverage, Software Delivery, Preemptive Alerting, Session Replay, RUM Explorer, Agent Observability, Database Monitoring, Event Correlation, Error Tracking, and all Security products in our...

2. investigating 2026-06-30 17:54 UTC

   We are continuing to investigate this issue.

3. investigating 2026-06-30 18:28 UTC

   We are continuing to investigate this issue.

4. investigating 2026-06-30 18:36 UTC

   We are continuing to investigate this issue.

5. identified 2026-06-30 18:57 UTC

   The issue has been identified and a fix is being implemented.

6. identified 2026-06-30 19:06 UTC

   We are continuing to work on a fix for this issue.

7. monitoring 2026-06-30 19:36 UTC

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

8. resolved 2026-06-30 20:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-30 10:35 UTC

   We are investigating delays in Monitors Notifications, which began at 09:52 UTC.

2. identified 2026-06-30 10:53 UTC

   We have identified the underlying issue and are working on a fix. It is important to note that no data has been lost, and notifications will be caught up once the service is operational again.

3. monitoring 2026-06-30 11:11 UTC

   We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.

4. resolved 2026-06-30 11:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-26 13:38 UTC

   We have identified increased latency processing APM Trace Metrics and are working on a fix. As a result of this issue, some users may see delayed APM Trace Metrics since 13:07 UTC. To prevent false monitor alerts due to delayed data, monitors affected by the delay will not...

2. monitoring 2026-06-26 13:41 UTC

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

3. resolved 2026-06-26 13:45 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: CI Visibility

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-25 23:23 UTC

   We are investigating increased latency processing CI Visibility data. As a result of this issue, some users may see delays with pipeline executions.

2. identified 2026-06-25 23:24 UTC

   We have identified the underlying issue and are working on a fix. It is important to note that no data has been lost, and it will be backfilled and available once the service is operational again.

3. resolved 2026-06-25 23:32 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-06-22 21:27 UTC

   We are currently investigating elevated latency on metrics queries. We will provide an update as soon as possible.

2. investigating 2026-06-22 21:43 UTC

   We are continuing to investigate this issue.

3. investigating 2026-06-22 22:09 UTC

   We are continuing to investigate this issue.

4. investigating 2026-06-22 22:28 UTC

   We are continuing to investigate this issue.

5. monitoring 2026-06-22 22:37 UTC

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

6. resolved 2026-06-22 22:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-06-18 16:13 UTC

   We are investigating increased latency processing Events. As a result of this issue, some users may see delays or gaps in the event stream or for event queries on dashboards To prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and...

2. monitoring 2026-06-18 16:22 UTC

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

3. resolved 2026-06-18 16:33 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, Metrics and Infra Monitoring, Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-12 17:12 UTC

   We are investigating delays in monitor evaluation, which began at 16:10 UTC.

2. identified 2026-06-12 17:59 UTC

   We are continuing to work on a fix for this issue.

3. identified 2026-06-12 18:30 UTC

   We are continuing to work on a fix for this issue.

4. identified 2026-06-12 18:39 UTC

   We are continuing to work on a fix for this issue.

5. identified 2026-06-12 19:01 UTC

   We are continuing to work on a fix for this issue.

6. identified 2026-06-12 19:08 UTC

   We are continuing to work on a fix for this issue. During this time, the following components are affected: Monitor evaluation Metrics and Infra Monitoring APM metrics Estimated usage metrics

7. monitoring 2026-06-12 19:23 UTC

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

8. resolved 2026-06-12 19:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Cloud Cost Management, Cloud Network Monitoring, Cloud Security Management, Database Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-06-08 11:05 UTC

   We are investigating and have identified a fix for increased latency across multiple products. As a result of this issue, some users may see delays in data across the platform.

2. monitoring 2026-06-08 11:21 UTC

   We have deployed a fix and we are monitoring the results.

3. monitoring 2026-06-08 12:21 UTC

   We are continuing to monitor the fix deployed earlier. We will provide another update once the issue is fully resolved.

4. resolved 2026-06-08 12:59 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-16 02:17 UTC

   We are investigating an issue submitting Azure metrics.

2. identified 2026-05-16 02:40 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-05-16 03:09 UTC

   We are continuing to work on a fix for this issue.

4. monitoring 2026-05-16 03:27 UTC

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

5. resolved 2026-05-16 03:43 UTC

   This incident has been resolved and Azure metrics are reporting as expected.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring, Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-14 18:24 UTC

   We are investigating increased latency querying Metrics. As a result of this issue, some users may experience delays loading graphs in dashboards and notebooks, and delayed monitor evaluations.

2. monitoring 2026-05-14 18:48 UTC

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

3. resolved 2026-05-14 19:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, Database Monitoring

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-13 15:16 UTC

   We are investigating degraded performance in the Database Monitoring pages and APM service pages. During this time, some customers may be experiencing: - The DBM database list page failing to load or displaying zero databases - 503 errors when attempting to access database...

2. monitoring 2026-05-13 15:36 UTC

   We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.

3. resolved 2026-05-13 15:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, CI Visibility, Error Tracking, Log Management, Metrics and Infra Monitoring, Monitors, RUM

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-05-08 00:06 UTC

   We are investigating delays in Monitors Notifications, which began at 23:39 UTC.

2. investigating 2026-05-08 00:24 UTC

   We are investigating increased latency across multiple products which began at 23:39 UTC. As a result of this issue, some users may see delays in data across the platform.

3. investigating 2026-05-08 00:47 UTC

   Due to upstream provider issues, we are also continuing to see unavailability of telemetry data coming from AWS into Datadog. https://health.aws.amazon.com/health/status

4. identified 2026-05-08 01:20 UTC

   We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are working on a fix. https://health.aws.amazon.com/health/status

5. identified 2026-05-08 02:02 UTC

   We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are working on a fix. https://health.aws.amazon.com/health/status

6. identified 2026-05-08 02:16 UTC

   We have identified due to upstream provider issues, we are continuing to see unavailability of telemetry data coming from AWS into Datadog. We are continuing to work on a fix. https://health.aws.amazon.com/health/status

7. identified 2026-05-08 02:59 UTC

   We have identified due to upstream provider issues, we are continuing to see unavailability of telemetry data coming from AWS into Datadog. We are continuing to work on a fix. https://health.aws.amazon.com/health/status For metrics we are still seeing delays in distribution...

8. identified 2026-05-08 04:13 UTC

   We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are continuing to work on a fix. https://health.aws.amazon.com/health/status For metrics, distribution metrics and point metrics are being...

9. identified 2026-05-08 04:48 UTC

   We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are continuing to work on a fix. https://health.aws.amazon.com/health/status For metrics, distribution metrics and point metrics are being...

10. identified 2026-05-08 05:30 UTC

    We have identified upstream provider issues and are continuing to experience delays in processing data across multiple products. We are continuing to work on a fix. https://health.aws.amazon.com/health/status For metrics, distribution metrics and point metrics are being...

11. identified 2026-05-08 05:44 UTC

    We have identified upstream provider issues. Metrics, Logs, APM and RUM data are being processed normally for all customers. Alerting is also functional. There are still processing delays for CI visibility. We are monitoring the situation....

12. monitoring 2026-05-08 06:21 UTC

    We have identified upstream provider issues. Metrics, Logs, APM, RUM and CI visibility data are being processed normally for all customers. Alerting is also functional. We are monitoring the situation. https://health.aws.amazon.com/health/status

13. resolved 2026-05-08 14:07 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-05-05 18:14 UTC

   We’re currently investigating an issue affecting APM monitor delays in our US1 datacenter. As a result, some users may experience delayed alert triggering or temporary inconsistencies in monitors.

2. identified 2026-05-05 18:29 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-05-05 18:44 UTC

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

4. resolved 2026-05-05 19:52 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-05-01 00:45 UTC

   We are actively investigating elevated error rates for Metrics Queries. As a result of this issue, some users may see errors with metrics graphs on the web application or API.

2. monitoring 2026-05-01 01:09 UTC

   We have deployed a fix and we are monitoring the results. We will provide another update once the service is fully operational.

3. resolved 2026-05-01 01:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring, Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS, Azure.

Started during Azure: Multiple services – Control plane issues in East US.

1. investigating 2026-04-24 16:27 UTC

   We are currently investigating this issue.

2. identified 2026-04-24 16:43 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-04-24 16:44 UTC

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

4. resolved 2026-04-24 16:50 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-15 22:38 UTC

   We are investigating increased latency processing Metrics. As a result of this issue, some users may see delays or gaps for metrics on graphs. To prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will automatically resume once...

2. investigating 2026-04-15 23:16 UTC

   We are investigating increased latency processing Distribution Metrics. As a result of this issue, some users may see delays or gaps for distribution metrics on graphs. To prevent false monitor alerts due to delayed data, monitors affected by the delay will not notify and will...

3. investigating 2026-04-15 23:54 UTC

   We are still investigating increased latency processing Distribution Metrics, delays have gone down but have not fully recovered.

4. monitoring 2026-04-16 00:32 UTC

   We have resolved the lag in distribution metrics and we are monitoring the results. We will provide another update once the issue is fully resolved.

5. resolved 2026-04-16 00:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-04-10 14:54 UTC

   We are investigating an issue to send notifications to Pagerduty, VictorOps, Slack, Webhook, Microsoft Teams and OpsGenie.

2. identified 2026-04-10 15:00 UTC

   The issue has been identified and a fix is being implemented.

3. identified 2026-04-10 15:23 UTC

   We are continuing to work on a fix for this issue.

4. identified 2026-04-10 15:42 UTC

   New notifications are now successfully delivered, and we are catching-up on past notifications that may have been delayed.

5. monitoring 2026-04-10 15:42 UTC

   New notifications are now successfully delivered, and we are catching-up on past notifications that may have been delayed

6. monitoring 2026-04-10 15:59 UTC

   We are still catching-up on past notifications that may have been delayed.

7. monitoring 2026-04-10 16:15 UTC

   We are still catching-up on past notifications that may have been delayed.

8. monitoring 2026-04-10 17:12 UTC

   Notifications for Opsgenie, VictorOps, BigPanda, Zendesk, and Sumologic are caught up. Webhooks, Microsoft Teams, Slack, JIRA, and ServiceNow are still catching up.

9. monitoring 2026-04-10 17:37 UTC

   Notifications for JIRA are now caught up.

10. monitoring 2026-04-10 18:33 UTC

    Notifications for ServiceNow and Microsoft Teams are now caught up. Webhooks and Slack notifications are still catching up.

11. monitoring 2026-04-10 19:02 UTC

    Webhooks and Slack notifications are still catching up.

12. monitoring 2026-04-10 19:44 UTC

    Webhooks and Slack notifications are still catching up.

13. monitoring 2026-04-10 20:13 UTC

    Webhooks and Slack notifications are still catching up.

14. resolved 2026-04-10 20:59 UTC

    Between approximately 9:42 AM and 10:38 AM ET on April 10, we observed delivery failures for customers in the US1, AP1, and AP2 regions. During this window, notifications to the following integrations were delayed or temporarily undelivered: • PagerDuty • Slack • Microsoft Teams...

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-27 18:57 UTC

   We are investigating increased latency in processing and storing Traces in APM. As a result of this issue, some users may see missing or delayed traces in APM Trace Search since 5pm UTC. They may also experience delay in APM trace-based monitors.

2. identified 2026-03-27 19:17 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-03-27 19:21 UTC

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

4. resolved 2026-03-27 19:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-26 14:24 UTC

   We are investigating delays in monitor notifications, which began at 12:00 UTC.

2. investigating 2026-03-26 14:55 UTC

   We are continuing investigating delays in monitor notifications that started at 12:00 UTC.

3. investigating 2026-03-26 15:32 UTC

   We are still continuing investigating delays in monitor notifications that started at 12:00 UTC. We've identified the root cause and are working on a fix.

4. investigating 2026-03-26 16:11 UTC

   We are continuing to investigate delays in monitor notifications.

5. identified 2026-03-26 16:48 UTC

   The issue has been identified and a fix is being implemented.

6. identified 2026-03-26 17:28 UTC

   We are continuing to work on a fix for this issue.

7. identified 2026-03-26 18:38 UTC

   We are continuing to work on a fix for this issue.

8. identified 2026-03-26 19:07 UTC

   We are continuing to work on a fix for this issue.

9. monitoring 2026-03-26 19:42 UTC

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

10. resolved 2026-03-26 19:56 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-19 00:54 UTC

   We are investigating an issue causing some metric monitors to intermittently report "No Data" status. This primarily affects monitors based on distribution metrics. Monitor alerting may be unreliable during this time. We are actively investigating and will provide updates as...

2. investigating 2026-03-19 01:27 UTC

   We are continuing to investigate the issue and will provide updates as available.

3. investigating 2026-03-19 02:04 UTC

   We are continuing to investigate the issue and will provide updates as available.

4. monitoring 2026-03-19 02:39 UTC

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

5. resolved 2026-03-19 02:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Web Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-03-13 09:26 UTC

   We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.

2. investigating 2026-03-13 09:27 UTC

   We are continuing to investigate this issue.

3. investigating 2026-03-13 09:32 UTC

   We are continuing to investigate this issue.

4. investigating 2026-03-13 09:52 UTC

   We are continuing to investigate this issue.

5. identified 2026-03-13 10:00 UTC

   The issue has been identified and a fix is being implemented.

6. monitoring 2026-03-13 10:05 UTC

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

7. resolved 2026-03-13 10:30 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Cloud Cost Management, RUM

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-24 04:31 UTC

   We are investigating increased latency processing RUM data. As a result of this issue, some users may see gaps or delays in RUM graphs as well as empty or partial query results on RUM Sessions, RUM Analytics, RUM Application, and Error Tracking pages.

2. identified 2026-02-24 05:29 UTC

   We have identified the underlying issue and are working on a fix. It is important to note that no data has been lost, and it will be backfilled and available once the service is operational again.

3. monitoring 2026-02-24 05:52 UTC

   We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.

4. resolved 2026-02-24 07:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, Data Streams Monitoring, Log Management, Metrics and Infra Monitoring, Monitors, RUM, Universal Service Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-02-18 19:30 UTC

   We are investigating delays in a subset of Distribution Metrics and Monitor Evaluations, which began at 18:33 UTC.

2. resolved 2026-02-18 20:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, Metrics and Infra Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-02-12 00:57 UTC

   We are investigating increased latency processing Traces in APM Trace Search and AWS streams metrics. As a result of this issue, some users may see missing or delayed traces in APM Trace Search, and delayed AWS stream metrics since 00:13 UTC.

2. identified 2026-02-12 01:20 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2026-02-12 01:32 UTC

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

4. monitoring 2026-02-12 01:49 UTC

   The remaining impact is limited to AWS Streams metrics. We are continuing to monitor for any further issues.

5. resolved 2026-02-12 02:08 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-11 20:56 UTC

   We are investigating increased latency processing Traces in APM Trace Search. As a result of this issue, some users may see missing or delayed traces in APM Trace Search and delayed APM Trace Monitors since 21:30 UTC.

2. identified 2026-02-11 21:18 UTC

   Teams have identified the issue and are working to mitigate at this time

3. identified 2026-02-11 21:51 UTC

   Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed and Distribution Metrics monitors are delayed starting from 21:35 UTC

4. identified 2026-02-11 22:28 UTC

   Teams continue to work to mitigate the impact of this issue. At this time, APM Trace Processing, APM Trace Monitors are still delayed. Distribution Metrics monitors were delayed between 21:35 and 22:15 UTC

5. monitoring 2026-02-11 23:28 UTC

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

6. resolved 2026-02-11 23:44 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, Application Security Management, Cloud SIEM, Incident Response, Log Management, Metrics and Infra Monitoring, Monitors, RUM, Synthetics

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-05 15:24 UTC

   We are currently investigating this issue.

2. investigating 2026-02-05 16:04 UTC

   We are continuing to investigate this issue.

3. investigating 2026-02-05 16:10 UTC

   We are continuing to investigate this issue.

4. investigating 2026-02-05 16:11 UTC

   We are continuing to investigate this issue.

5. investigating 2026-02-05 16:28 UTC

   We are continuing to investigate this issue.

6. identified 2026-02-05 16:31 UTC

   The issue has been identified and a fix is being implemented.

7. identified 2026-02-05 16:50 UTC

   We are continuing to work on a fix for this issue.

8. identified 2026-02-05 17:01 UTC

   We are observing recovery for the vast majority of monitors and are continuing to work on a full fix for this issue.

9. monitoring 2026-02-05 17:23 UTC

   We have observed full recovery of monitors and will continue to monitor

10. resolved 2026-02-05 17:43 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-29 17:35 UTC

   We are investigating delays in Monitors evaluations, which began at 17:15 UTC.

2. identified 2026-01-29 17:46 UTC

   We have identified the underlying issue and are working on a fix. It is important to note that no data has been lost, and evaluations will be caught up once the service is operational again.

3. identified 2026-01-29 18:06 UTC

   We are continuing to work on a fix for this issue. It is important to note that no data has been lost, and evaluations will be caught up once the service is operational again.

4. monitoring 2026-01-29 18:36 UTC

   We have deployed a fix and we are monitoring the results. We will continue to provide regular updates.

5. monitoring 2026-01-29 19:09 UTC

   We are continuing to monitor the fix and will continue to provide regular updates.

6. resolved 2026-01-29 19:55 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-28 20:30 UTC

   We are investigating delays in service checks monitors evaluation, which began at 20:26 1/28/2026 UTC.

2. investigating 2026-01-28 21:21 UTC

   We are continuing to investigate this issue.

3. identified 2026-01-28 22:08 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2026-01-28 23:13 UTC

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

5. resolved 2026-01-28 23:36 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: APM, App Builder, Application Security Management, Application Vulnerability Management, Audit Trail, CI Visibility, Cloud Cost Management, Cloud Network Monitoring, Cloud Security Management, Cloud SIEM, Code Security, Continuous Profiler, Database Monitoring, Data Jobs Monitoring, Data Streams Monitoring, Incident Response, LLM Observability, Log Management, Metrics and Infra Monitoring, Mobile Application, Monitors, NDM, Observability Pipelines, Package Repositories, RUM, Sensitive Data Scanner, Serverless, Synthetics, Universal Service Monitoring, Web Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-01-22 18:51 UTC

   We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application. Please note that data processing and alerts are not affected by this incident.

2. investigating 2026-01-22 19:01 UTC

   We are continuing to investigate this issue.

3. monitoring 2026-01-22 19:13 UTC

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

4. resolved 2026-01-22 19:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-01-18 12:33 UTC

   We are investigating increased latency processing Events. As a result of this issue, some users may see delays or gaps in the event stream or for event based widgets or event based monitors.

2. identified 2026-01-18 12:35 UTC

   We have identified the issue and scaled up for recovery, with a recovery estimated to be around 14h30 UTC. We'll continue to give updates as recovery progresses.

3. identified 2026-01-18 13:26 UTC

   Recovery is in progress and the new estimated time of recovery would be 14h30 UTC.

4. resolved 2026-01-18 14:24 UTC

   This incident is resolved. There's no more delay for the processing of Events, nor impact on the event stream, event based widgets and event based monitors.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-12 21:49 UTC

   We are investigating increased latency processing Processes data. As a result of this issue, some users may see delays or gaps for data based on Process Monitoring. To prevent spurious alerts, we have temporarily disabled monitors based on this data.

2. investigating 2025-12-12 21:53 UTC

   We are continuing to investigate this issue.

3. identified 2025-12-12 22:41 UTC

   The issue has been identified and a fix is being implemented.

4. monitoring 2025-12-12 23:31 UTC

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

5. resolved 2025-12-12 23:43 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-12 18:37 UTC

   We are currently investigating lag in ingesting apm metrics, which affects monitor evaluation.

2. investigating 2025-12-12 18:55 UTC

   We are continuing to investigate this issue.

3. investigating 2025-12-12 19:26 UTC

   We are currently investigating lag in ingesting apm and process metrics, which affects monitor evaluation and in some cases led to incorrect monitor alerts.

4. identified 2025-12-12 20:53 UTC

   We have identified the issue affecting ingestion delays in apm and process metrics and are working on recovery

5. resolved 2025-12-12 21:52 UTC

   All impact related to APM metrics has been resolved. A separate incident has been created to track the remaining impact in live process data.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Metrics and Infra Monitoring

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-09 20:16 UTC

   We’re currently monitoring an issue causing delays in distribution metric processing in our US1 region.

2. identified 2025-12-09 20:36 UTC

   The issue has been identified and a fix is being implemented.

3. monitoring 2025-12-09 21:00 UTC

   Live distribution metrics are available and being evaluated for all monitors. Gaps in graphs from the beginning of the incident are in the process of being backfilled.

4. resolved 2025-12-09 21:08 UTC

   This incident has been resolved. Live data is being processed normally and gaps in distribution metrics on graphs will be backfilled within the next hour.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Web Application

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-19 19:08 UTC

   We are investigating loading issues on our web application. As a result, some users might be getting errors when loading the web application.

2. investigating 2025-11-19 19:28 UTC

   We continue investigating the issue with web application. Data processing and alerting remain operational.

3. monitoring 2025-11-19 19:37 UTC

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

4. resolved 2025-11-19 19:44 UTC

   This incident has been resolved as of 2:32PM ET.

Excerpts are shortened. Read the full incident on Datadog's status page.

Affected: Monitors

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 13:17 UTC

   We are investigating delays in RUM-based Monitors Notifications, which began at 11:30am UTC.

2. resolved 2025-11-18 13:53 UTC

   This incident has been resolved. Notification delays were only affecting our internal monitoring and were due to the ongoing Cloudflare incident: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7/.

Excerpts are shortened. Read the full incident on Datadog's status page.