Historial de interrupciones de Datadog

1. September 3, 2026 at 5:20 PM UTCinvestigating

   Estamos investigando el aumento de latencia procesando datos de optimización de CICD, cobertura de códigos, seguridad de códigos y DORA. Como resultado de este problema, algunos usuarios pueden ver retrasos con carreras de pruebas y ejecuciones de oleoductos.

2. September 3, 2026 at 5:59 PM UTCidentified

   Identificamos la cuestión.

3. September 3, 2026 at 7:01 PM UTCmonitoring

   Estamos monitoreando la cuestión.

4. September 3, 2026 at 9:51 PM UTCmonitoring

   Hemos aplicado medidas correctivas, y la recuperación está en marcha. Seguimos vigilando la cuestión.

5. September 3, 2026 at 11:01 PM UTCresolved

   La cuestión se resuelve ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. September 2, 2026 at 1:07 AM UTCinvestigating

   Estamos investigando retrasos en la evaluación del monitor, que comenzó el 2 de septiembre de 2026, 12:10 AM UTC.

2. September 2, 2026 at 1:16 AM UTCidentified

   Identificamos la cuestión.

3. September 2, 2026 at 1:21 AM UTCmonitoring

   Estamos monitoreando la cuestión.

4. September 2, 2026 at 1:24 AM UTCresolved

   La cuestión se resuelve ahora.

Traducido automáticamente desde la actualización oficial del incidente.

1. August 6, 2026 at 6:51 PM UTCinvestigating

   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 automatically resume once current data is available. All other monitors will operate normally.

2. August 6, 2026 at 7:18 PM UTCidentified

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

3. August 6, 2026 at 7:27 PM UTCmonitoring

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

4. August 6, 2026 at 7:37 PM UTCresolved

   This incident has been resolved.

1. July 30, 2026 at 7:44 AM UTCinvestigating

   Estamos investigando retrasos en la evaluación de monitores Service Check, que comenzó a las 6:35AM UTC.

2. July 30, 2026 at 7:49 AM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. July 30, 2026 at 8:16 AM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. July 30, 2026 at 8:27 AM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 29, 2026 at 3:41 PM UTCinvestigating

   Actualmente estamos investigando un problema que retrasa la ingestión de métricas de medición del usuario real (RUM), métricas de procesos personalizados y un subconjunto de métricas de distribución para algunos clientes. Como resultado, algunos usuarios pueden ver retrasos o lagunas en RUM, proceso personalizado y métricas de distribución. Para evitar falsas alertas causadas por datos retrasados, los monitores afectados no notificarán y reanudarán automáticamente una vez que estén disponibles los datos actuales. Todos los demás monitores funcionarán normalmente. No se han perdido datos. Proporcionaremos más actualizaciones a medida que avance la situación.

2. July 29, 2026 at 3:42 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 29, 2026 at 4:35 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

4. July 29, 2026 at 4:53 PM UTCidentified

   Se han resuelto los retrasos de la RUM. Continuamos atenuando los problemas de las métricas de distribución.

5. July 29, 2026 at 5:12 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

6. July 29, 2026 at 5:28 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 27, 2026 at 7:05 PM UTCinvestigating

   Estamos investigando un problema con pruebas sintéticas.

2. July 27, 2026 at 7:25 PM UTCinvestigating

   Continuamos investigando un problema publicando resultados sintéticos. Se están ejecutando exámenes sintéticos y se retrasan los resultados.

3. July 27, 2026 at 7:36 PM UTCidentified

   Hemos identificado el número publicando resultados sintéticos. Los exámenes sintéticos siguen funcionando con resultados retrasados.

4. July 27, 2026 at 7:46 PM UTCmonitoring

   Se ha implementado una solución y estamos monitoreando los resultados.

5. July 27, 2026 at 7:52 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 23, 2026 at 5:08 PM UTCinvestigating

   Estamos investigando un aumento de latencia con Pages y Monitor cambios estatales. Como resultado de esta cuestión, algunos usuarios pueden ver retrasos.

2. July 23, 2026 at 5:31 PM UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. July 23, 2026 at 6:02 PM UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. July 23, 2026 at 6:13 PM UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. July 10, 2026 at 2:09 PM UTCinvestigating

   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 during this incident. We are not aware of any data loss at this time. Our engineering team is actively working on a fix, and we'll follow up with more information shortly.

2. July 10, 2026 at 2:35 PM UTCinvestigating

   We are continuing to investigate the issue.

3. July 10, 2026 at 3:18 PM UTCmonitoring

   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. July 10, 2026 at 3:59 PM UTCresolved

   This incident has been resolved.

1. July 3, 2026 at 12:25 AM UTCinvestigating

   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 affected.

2. July 3, 2026 at 12:55 AM UTCidentified

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

3. July 3, 2026 at 1:21 AM UTCmonitoring

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

4. July 3, 2026 at 1:29 AM UTCresolved

   This incident has been resolved.

1. July 1, 2026 at 6:31 PM UTCinvestigating

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

2. July 1, 2026 at 6:57 PM UTCinvestigating

   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. July 1, 2026 at 7:10 PM UTCidentified

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

4. July 1, 2026 at 7:19 PM UTCmonitoring

   We have deployed mitigation actions and are monitoring the recovery.

5. July 1, 2026 at 7:43 PM UTCmonitoring

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

6. July 1, 2026 at 8:37 PM UTCresolved

   This incident has been resolved.

1. June 30, 2026 at 5:51 PM UTCinvestigating

   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 US1 datacenter. As a result, some users may experience delays in data processing and errors when using affected products. Our engineering teams have identified the issue and are actively working on a resolution. Our engineering teams are actively working to resolve the issue, and we'll follow up with more information shortly. Please let us know if you have any questions or need anything else in the meantime.

2. June 30, 2026 at 6:36 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 30, 2026 at 6:57 PM UTCidentified

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

4. June 30, 2026 at 7:06 PM UTCidentified

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

5. June 30, 2026 at 7:36 PM UTCmonitoring

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

6. June 30, 2026 at 8:32 PM UTCresolved

   This incident has been resolved.

1. June 30, 2026 at 10:35 AM UTCinvestigating

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

2. June 30, 2026 at 10:53 AM UTCidentified

   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. June 30, 2026 at 11:11 AM UTCmonitoring

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

4. June 30, 2026 at 11:18 AM UTCresolved

   This incident has been resolved.

1. June 26, 2026 at 1:38 PM UTCidentified

   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 notify and will automatically resume once current data is available. All other monitors will operate normally..

2. June 26, 2026 at 1:41 PM UTCmonitoring

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

3. June 26, 2026 at 1:45 PM UTCresolved

   This incident has been resolved.

1. June 25, 2026 at 11:23 PM UTCinvestigating

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

2. June 25, 2026 at 11:24 PM UTCidentified

   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. June 25, 2026 at 11:32 PM UTCresolved

   This incident has been resolved.

1. June 22, 2026 at 9:27 PM UTCinvestigating

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

2. June 22, 2026 at 10:28 PM UTCinvestigating

   We are continuing to investigate this issue.

3. June 22, 2026 at 10:37 PM UTCmonitoring

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

4. June 22, 2026 at 10:41 PM UTCresolved

   This incident has been resolved.

1. June 18, 2026 at 4:13 PM UTCinvestigating

   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 will automatically resume once current data is available. All other monitors will operate normally..

2. June 18, 2026 at 4:22 PM UTCmonitoring

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

3. June 18, 2026 at 4:33 PM UTCresolved

   This incident has been resolved.

1. June 16, 2026 at 5:42 PM UTCidentified

   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. (edited)

2. June 16, 2026 at 6:23 PM UTCidentified

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

3. June 16, 2026 at 6:29 PM UTCmonitoring

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

4. June 16, 2026 at 6:33 PM UTCresolved

   This incident has been resolved.

1. June 12, 2026 at 5:12 PM UTCidentified

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

2. June 12, 2026 at 7:01 PM UTCidentified

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

3. June 12, 2026 at 7:08 PM UTCidentified

   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

4. June 12, 2026 at 7:23 PM UTCmonitoring

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

5. June 12, 2026 at 7:39 PM UTCresolved

   This incident has been resolved.

1. June 8, 2026 at 11:05 AM UTCidentified

   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. June 8, 2026 at 11:21 AM UTCmonitoring

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

3. June 8, 2026 at 12:21 PM UTCmonitoring

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

4. June 8, 2026 at 12:59 PM UTCresolved

   This incident has been resolved.

1. May 16, 2026 at 2:17 AM UTCinvestigating

   We are investigating an issue submitting Azure metrics.

2. May 16, 2026 at 2:40 AM UTCidentified

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

3. May 16, 2026 at 3:09 AM UTCidentified

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

4. May 16, 2026 at 3:27 AM UTCmonitoring

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

5. May 16, 2026 at 3:43 AM UTCresolved

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