Istoricul incidentelor Datadog

1. 3 septembrie 2026 la 17:20 UTCinvestigating

   Investigăm creșterea procesării latenței Optimizarea CICD, acoperirea codului, securitatea codului și datele DORA. Ca urmare a acestei probleme, unii utilizatori pot vedea întârzieri cu rulaje de testare și execuție conducte.

2. 3 septembrie 2026 la 17:59 UTCidentified

   Am identificat problema.

3. 3 septembrie 2026 la 19:01 UTCmonitoring

   Monitorizăm problema.

4. 3 septembrie 2026 la 21:51 UTCmonitoring

   Am aplicat măsuri de remediere, iar redresarea este în curs. Continuăm să monitorizăm problema.

5. 3 septembrie 2026 la 23:01 UTCresolved

   Problema este acum rezolvată.

Traducere automată din actualizarea oficială a incidentului.

1. 2 septembrie 2026 la 01:07 UTCinvestigating

   Investigăm întârzieri în evaluarea monitorizării, care a început la 2 sep 2026, 12:10 AM UTC.

2. 2 septembrie 2026 la 01:16 UTCidentified

   Am identificat problema.

3. 2 septembrie 2026 la 01:21 UTCmonitoring

   Monitorizăm problema.

4. 2 septembrie 2026 la 01:24 UTCresolved

   Problema este acum rezolvată.

Traducere automată din actualizarea oficială a incidentului.

1. 6 august 2026 la 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 august 2026 la 19:18 UTCidentified

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

3. 6 august 2026 la 19:27 UTCmonitoring

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

4. 6 august 2026 la 19:37 UTCresolved

   This incident has been resolved.

1. 30 iulie 2026 la 07:44 UTCinvestigating

   Investigăm întârzierile în evaluarea monitoarelor de verificare a serviciului, care a început la ora 6:35 AM UTC.

2. 30 iulie 2026 la 07:49 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 30 iulie 2026 la 08:16 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 30 iulie 2026 la 08:27 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 29 iulie 2026 la 15:41 UTCinvestigating

   În prezent, investigăm o problemă care întârzie ingerarea Monitoring Real Utilizator (RUM) măsoară indicatorii, indicatorii de proces personalizați și un subset de indicatori de distribuție pentru unii clienți. Prin urmare, unii utilizatori pot vedea întârzieri sau lacune în RUM, procese personalizate și indicatori de distribuție. Pentru a preveni alertele false cauzate de datele întârziate, monitoarele afectate nu vor notifica și se vor relua automat după ce datele actuale sunt disponibile. Toate celelalte monitoare vor funcţiona normal. Nu s-au pierdut date. Vom furniza noi actualizări pe măsură ce situaţia progresează.

2. 29 iulie 2026 la 15:42 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 29 iulie 2026 la 16:35 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

4. 29 iulie 2026 la 16:53 UTCidentified

   Întârzierile RUM au fost rezolvate. Continuăm să atenuăm problemele privind indicatorii de distribuţie.

5. 29 iulie 2026 la 17:12 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

6. 29 iulie 2026 la 17:28 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 27 iulie 2026 la 19:05 UTCinvestigating

   Investigăm o problemă care rulează teste sintetice.

2. 27 iulie 2026 la 19:25 UTCinvestigating

   Continuăm să investigăm o problemă de publicare a rezultatelor sintetice. Testele sintetice se execută și rezultatele sunt întârziate.

3. 27 iulie 2026 la 19:36 UTCidentified

   Am identificat problema publicării rezultatelor sintetice. Testele sintetice continuă cu rezultate întârziate.

4. 27 iulie 2026 la 19:46 UTCmonitoring

   A fost implementat un fix şi monitorizăm rezultatele.

5. 27 iulie 2026 la 19:52 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 23 iulie 2026 la 17:08 UTCinvestigating

   Investigăm creşterea latenţei cu Pagini şi monitorizarea schimbărilor de stat. Ca urmare a acestei probleme, unii utilizatori pot vedea întârzieri.

2. 23 iulie 2026 la 17:31 UTCidentified

   Problema a fost identificată și se pune în aplicare o soluție.

3. 23 iulie 2026 la 18:02 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 23 iulie 2026 la 18:13 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 10 iulie 2026 la 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 iulie 2026 la 14:35 UTCinvestigating

   We are continuing to investigate the issue.

3. 10 iulie 2026 la 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 iulie 2026 la 15:59 UTCresolved

   This incident has been resolved.

1. 3 iulie 2026 la 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 iulie 2026 la 00:55 UTCidentified

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

3. 3 iulie 2026 la 01:21 UTCmonitoring

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

4. 3 iulie 2026 la 01:29 UTCresolved

   This incident has been resolved.

1. 1 iulie 2026 la 18:31 UTCinvestigating

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

2. 1 iulie 2026 la 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 iulie 2026 la 19:10 UTCidentified

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

4. 1 iulie 2026 la 19:19 UTCmonitoring

   We have deployed mitigation actions and are monitoring the recovery.

5. 1 iulie 2026 la 19:43 UTCmonitoring

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

6. 1 iulie 2026 la 20:37 UTCresolved

   This incident has been resolved.

1. 30 iunie 2026 la 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 iunie 2026 la 18:36 UTCinvestigating

   We are continuing to investigate this issue.

3. 30 iunie 2026 la 18:57 UTCidentified

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

4. 30 iunie 2026 la 19:06 UTCidentified

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

5. 30 iunie 2026 la 19:36 UTCmonitoring

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

6. 30 iunie 2026 la 20:32 UTCresolved

   This incident has been resolved.

1. 30 iunie 2026 la 10:35 UTCinvestigating

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

2. 30 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 11:18 UTCresolved

   This incident has been resolved.

1. 26 iunie 2026 la 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 iunie 2026 la 13:41 UTCmonitoring

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

3. 26 iunie 2026 la 13:45 UTCresolved

   This incident has been resolved.

1. 25 iunie 2026 la 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 iunie 2026 la 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 iunie 2026 la 23:32 UTCresolved

   This incident has been resolved.

1. 22 iunie 2026 la 21:27 UTCinvestigating

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

2. 22 iunie 2026 la 22:28 UTCinvestigating

   We are continuing to investigate this issue.

3. 22 iunie 2026 la 22:37 UTCmonitoring

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

4. 22 iunie 2026 la 22:41 UTCresolved

   This incident has been resolved.

1. 18 iunie 2026 la 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 iunie 2026 la 16:22 UTCmonitoring

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

3. 18 iunie 2026 la 16:33 UTCresolved

   This incident has been resolved.

1. 16 iunie 2026 la 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 iunie 2026 la 18:23 UTCidentified

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

3. 16 iunie 2026 la 18:29 UTCmonitoring

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

4. 16 iunie 2026 la 18:33 UTCresolved

   This incident has been resolved.

1. 12 iunie 2026 la 17:12 UTCidentified

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

2. 12 iunie 2026 la 19:01 UTCidentified

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

3. 12 iunie 2026 la 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 iunie 2026 la 19:23 UTCmonitoring

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

5. 12 iunie 2026 la 19:39 UTCresolved

   This incident has been resolved.

1. 8 iunie 2026 la 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 iunie 2026 la 11:21 UTCmonitoring

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

3. 8 iunie 2026 la 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 iunie 2026 la 12:59 UTCresolved

   This incident has been resolved.

1. 16 mai 2026 la 02:17 UTCinvestigating

   We are investigating an issue submitting Azure metrics.

2. 16 mai 2026 la 02:40 UTCidentified

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

3. 16 mai 2026 la 03:09 UTCidentified

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

4. 16 mai 2026 la 03:27 UTCmonitoring

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

5. 16 mai 2026 la 03:43 UTCresolved

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