Histórico de interrupções do Datadog

1. 3 Gwengolo 2026 da 17:20 UTCinvestigating

   Estamos investigando o aumento do processamento da latência dos dados CICD Optimization, Code Coverage, Code Security e DORA. Como resultado desta questão, alguns usuários podem ver atrasos com as execuções de testes e pipeline.

2. 3 Gwengolo 2026 da 17:59 UTCidentified

   Identificámos a questão.

3. 3 Gwengolo 2026 da 19:01 UTCmonitoring

   Estamos a acompanhar a questão.

4. 3 Gwengolo 2026 da 21:51 UTCmonitoring

   Aplicámos remediações e a recuperação está em curso. Continuamos a acompanhar a questão.

5. 3 Gwengolo 2026 da 23:01 UTCresolved

   A questão está agora resolvida.

Traduzido automaticamente da atualização oficial do incidente.

1. 2 Gwengolo 2026 da 01:07 UTCinvestigating

   Estamos investigando atrasos na avaliação do monitor, iniciada em 2 de setembro de 2026, 12:10 UTC.

2. 2 Gwengolo 2026 da 01:16 UTCidentified

   Identificámos a questão.

3. 2 Gwengolo 2026 da 01:21 UTCmonitoring

   Estamos a acompanhar a questão.

4. 2 Gwengolo 2026 da 01:24 UTCresolved

   A questão está agora resolvida.

Traduzido automaticamente da atualização oficial do incidente.

1. 6 Eost 2026 da 18:51 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. 6 Eost 2026 da 19:18 UTCidentified

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

3. 6 Eost 2026 da 19:27 UTCmonitoring

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

4. 6 Eost 2026 da 19:37 UTCresolved

   This incident has been resolved.

1. 30 Gouere 2026 da 07:44 UTCinvestigating

   Estamos investigando atrasos na avaliação dos monitores do Service Check, que começou às 6:35 AM UTC.

2. 30 Gouere 2026 da 07:49 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 30 Gouere 2026 da 08:16 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 30 Gouere 2026 da 08:27 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 29 Gouere 2026 da 15:41 UTCinvestigating

   Atualmente estamos investigando um problema que atrasa a ingestão de métricas de medidas do Real User Monitoring (RUM), métricas de processos personalizados e um subconjunto de métricas de distribuição para alguns clientes. Como resultado, alguns usuários podem ver atrasos ou lacunas em métricas de RUM, processo personalizado e distribuição. Para evitar alertas falsos causados por dados atrasados, os monitores afetados não notificarão e retornarão automaticamente quando os dados atuais estiverem disponíveis. Todos os outros monitores funcionarão normalmente. Nenhum dado foi perdido. Providenciaremos novas atualizações à medida que a situação progride.

2. 29 Gouere 2026 da 15:42 UTCinvestigating

   Continuamos a investigar esta questão.

3. 29 Gouere 2026 da 16:35 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

4. 29 Gouere 2026 da 16:53 UTCidentified

   Os atrasos no RUM foram resolvidos. Continuamos a mitigar os problemas das métricas de distribuição.

5. 29 Gouere 2026 da 17:12 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

6. 29 Gouere 2026 da 17:28 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 27 Gouere 2026 da 19:05 UTCinvestigating

   Estamos a investigar um problema a executar testes sintéticos.

2. 27 Gouere 2026 da 19:25 UTCinvestigating

   Continuamos a investigar uma edição publicando resultados sintéticos. Os testes sintéticos estão em execução e os resultados são atrasados.

3. 27 Gouere 2026 da 19:36 UTCidentified

   Identificámos a edição publicando resultados sintéticos. Os testes sintéticos continuam a correr com resultados atrasados.

4. 27 Gouere 2026 da 19:46 UTCmonitoring

   Foi implementada uma solução e estamos a monitorizar os resultados.

5. 27 Gouere 2026 da 19:52 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 23 Gouere 2026 da 17:08 UTCinvestigating

   Estamos investigando o aumento da latência com as alterações de estado de Pages e Monitor. Como resultado desta questão, alguns usuários podem ver atrasos.

2. 23 Gouere 2026 da 17:31 UTCidentified

   A questão foi identificada e está a ser implementada uma solução.

3. 23 Gouere 2026 da 18:02 UTCmonitoring

   Foi implementada uma correção e estamos monitorando os resultados.

4. 23 Gouere 2026 da 18:13 UTCresolved

   Este incidente foi resolvido.

Traduzido automaticamente da atualização oficial do incidente.

1. 10 Gouere 2026 da 14:09 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. 10 Gouere 2026 da 14:35 UTCinvestigating

   We are continuing to investigate the issue.

3. 10 Gouere 2026 da 15:18 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. 10 Gouere 2026 da 15:59 UTCresolved

   This incident has been resolved.

1. 3 Gouere 2026 da 00:25 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. 3 Gouere 2026 da 00:55 UTCidentified

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

3. 3 Gouere 2026 da 01:21 UTCmonitoring

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

4. 3 Gouere 2026 da 01:29 UTCresolved

   This incident has been resolved.

1. 1 Gouere 2026 da 18:31 UTCinvestigating

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

2. 1 Gouere 2026 da 18:57 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. 1 Gouere 2026 da 19:10 UTCidentified

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

4. 1 Gouere 2026 da 19:19 UTCmonitoring

   We have deployed mitigation actions and are monitoring the recovery.

5. 1 Gouere 2026 da 19:43 UTCmonitoring

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

6. 1 Gouere 2026 da 20:37 UTCresolved

   This incident has been resolved.

1. 30 Mezheven 2026 da 17:51 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. 30 Mezheven 2026 da 18:36 UTCinvestigating

   We are continuing to investigate this issue.

3. 30 Mezheven 2026 da 18:57 UTCidentified

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

4. 30 Mezheven 2026 da 19:06 UTCidentified

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

5. 30 Mezheven 2026 da 19:36 UTCmonitoring

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

6. 30 Mezheven 2026 da 20:32 UTCresolved

   This incident has been resolved.

1. 30 Mezheven 2026 da 10:35 UTCinvestigating

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

2. 30 Mezheven 2026 da 10:53 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. 30 Mezheven 2026 da 11:11 UTCmonitoring

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

4. 30 Mezheven 2026 da 11:18 UTCresolved

   This incident has been resolved.

1. 26 Mezheven 2026 da 13:38 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. 26 Mezheven 2026 da 13:41 UTCmonitoring

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

3. 26 Mezheven 2026 da 13:45 UTCresolved

   This incident has been resolved.

1. 25 Mezheven 2026 da 23:23 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. 25 Mezheven 2026 da 23:24 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. 25 Mezheven 2026 da 23:32 UTCresolved

   This incident has been resolved.

1. 22 Mezheven 2026 da 21:27 UTCinvestigating

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

2. 22 Mezheven 2026 da 22:28 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 Mezheven 2026 da 22:37 UTCmonitoring

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

4. 22 Mezheven 2026 da 22:41 UTCresolved

   This incident has been resolved.

1. 18 Mezheven 2026 da 16:13 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. 18 Mezheven 2026 da 16:22 UTCmonitoring

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

3. 18 Mezheven 2026 da 16:33 UTCresolved

   This incident has been resolved.

1. 16 Mezheven 2026 da 17:42 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. 16 Mezheven 2026 da 18:23 UTCidentified

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

3. 16 Mezheven 2026 da 18:29 UTCmonitoring

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

4. 16 Mezheven 2026 da 18:33 UTCresolved

   This incident has been resolved.

1. 12 Mezheven 2026 da 17:12 UTCidentified

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

2. 12 Mezheven 2026 da 19:01 UTCidentified

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

3. 12 Mezheven 2026 da 19:08 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. 12 Mezheven 2026 da 19:23 UTCmonitoring

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

5. 12 Mezheven 2026 da 19:39 UTCresolved

   This incident has been resolved.

1. 8 Mezheven 2026 da 11:05 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. 8 Mezheven 2026 da 11:21 UTCmonitoring

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

3. 8 Mezheven 2026 da 12:21 UTCmonitoring

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

4. 8 Mezheven 2026 da 12:59 UTCresolved

   This incident has been resolved.

1. 16 Mae 2026 da 02:17 UTCinvestigating

   We are investigating an issue submitting Azure metrics.

2. 16 Mae 2026 da 02:40 UTCidentified

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

3. 16 Mae 2026 da 03:09 UTCidentified

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

4. 16 Mae 2026 da 03:27 UTCmonitoring

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

5. 16 Mae 2026 da 03:43 UTCresolved

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