Datadog driftsforstyrrelser

1. 3. september 2026 kl. 17.20 UTCinvestigating

   Vi undersøger øget latency behandling CICD Optimering, Code Coverage, Code Security, og DORA data. Som et resultat af dette spørgsmål, nogle brugere kan se forsinkelser med testkørsler og rørledninger henrettelser.

2. 3. september 2026 kl. 17.59 UTCidentified

   Vi identificerede problemet.

3. 3. september 2026 kl. 19.01 UTCmonitoring

   Vi overvåger sagen.

4. 3. september 2026 kl. 21.51 UTCmonitoring

   Vi har anvendt oprensninger, og opsvinget er i gang. Vi fortsætter med at overvåge spørgsmålet.

5. 3. september 2026 kl. 23.01 UTCresolved

   Spørgsmålet er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 2. september 2026 kl. 01.07 UTCinvestigating

   Vi undersøger forsinkelser i overvågning evaluering, som begyndte på Sep 2, 2026, 12: 10 AM UTC.

2. 2. september 2026 kl. 01.16 UTCidentified

   Vi identificerede problemet.

3. 2. september 2026 kl. 01.21 UTCmonitoring

   Vi overvåger sagen.

4. 2. september 2026 kl. 01.24 UTCresolved

   Spørgsmålet er nu løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 6. august 2026 kl. 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 kl. 19.18 UTCidentified

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

3. 6. august 2026 kl. 19.27 UTCmonitoring

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

4. 6. august 2026 kl. 19.37 UTCresolved

   This incident has been resolved.

1. 30. juli 2026 kl. 07.44 UTCinvestigating

   Vi undersøger forsinkelser i Service Check overvåger evaluering, som begyndte kl. 6: 35AM UTC.

2. 30. juli 2026 kl. 07.49 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 30. juli 2026 kl. 08.16 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 30. juli 2026 kl. 08.27 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 29. juli 2026 kl. 15.41 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem forsinke indtagelse af Real User Monitoring (RUM) foranstaltning målinger, brugerdefinerede proces målinger, og en delmængde af distribution målinger for nogle kunder. Som et resultat, nogle brugere kan se forsinkelser eller huller i RUM, brugerdefinerede proces, og distribution målinger. For at forhindre falske indberetninger forårsaget af forsinkede data, vil berørte monitorer ikke underrette og vil automatisk genoptage, når aktuelle data er tilgængelige. Alle andre overvågningsenheder vil fungere normalt. Ingen data er gået tabt. Vi vil levere yderligere opdateringer, efterhånden som situationen skrider frem.

2. 29. juli 2026 kl. 15.42 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 29. juli 2026 kl. 16.35 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

4. 29. juli 2026 kl. 16.53 UTCidentified

   RUM-forsinkelserne er blevet løst. Vi fortsætter med at mindske problemerne med fordelingsmålinger.

5. 29. juli 2026 kl. 17.12 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

6. 29. juli 2026 kl. 17.28 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 27. juli 2026 kl. 19.05 UTCinvestigating

   Vi undersøger et problem med syntetiske test.

2. 27. juli 2026 kl. 19.25 UTCinvestigating

   Vi fortsætter med at undersøge et problem med syntetiske resultater. Syntetiske test kører, og resultaterne er forsinkede.

3. 27. juli 2026 kl. 19.36 UTCidentified

   Vi har identificeret problemet med at offentliggøre syntetiske resultater. Syntetiske test fortsætter med forsinkede resultater.

4. 27. juli 2026 kl. 19.46 UTCmonitoring

   Et fix er blevet implementeret, og vi overvåger resultaterne.

5. 27. juli 2026 kl. 19.52 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 23. juli 2026 kl. 17.08 UTCinvestigating

   Vi undersøger øget latenstid med Sider og overvågning stat ændringer. Som et resultat af dette spørgsmål, nogle brugere kan se forsinkelser.

2. 23. juli 2026 kl. 17.31 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 23. juli 2026 kl. 18.02 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 23. juli 2026 kl. 18.13 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 10. juli 2026 kl. 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. juli 2026 kl. 14.35 UTCinvestigating

   We are continuing to investigate the issue.

3. 10. juli 2026 kl. 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. juli 2026 kl. 15.59 UTCresolved

   This incident has been resolved.

1. 3. juli 2026 kl. 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. juli 2026 kl. 00.55 UTCidentified

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

3. 3. juli 2026 kl. 01.21 UTCmonitoring

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

4. 3. juli 2026 kl. 01.29 UTCresolved

   This incident has been resolved.

1. 1. juli 2026 kl. 18.31 UTCinvestigating

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

2. 1. juli 2026 kl. 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. juli 2026 kl. 19.10 UTCidentified

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

4. 1. juli 2026 kl. 19.19 UTCmonitoring

   We have deployed mitigation actions and are monitoring the recovery.

5. 1. juli 2026 kl. 19.43 UTCmonitoring

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

6. 1. juli 2026 kl. 20.37 UTCresolved

   This incident has been resolved.

1. 30. juni 2026 kl. 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. juni 2026 kl. 18.36 UTCinvestigating

   We are continuing to investigate this issue.

3. 30. juni 2026 kl. 18.57 UTCidentified

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

4. 30. juni 2026 kl. 19.06 UTCidentified

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

5. 30. juni 2026 kl. 19.36 UTCmonitoring

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

6. 30. juni 2026 kl. 20.32 UTCresolved

   This incident has been resolved.

1. 30. juni 2026 kl. 10.35 UTCinvestigating

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

2. 30. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 11.18 UTCresolved

   This incident has been resolved.

1. 26. juni 2026 kl. 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. juni 2026 kl. 13.41 UTCmonitoring

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

3. 26. juni 2026 kl. 13.45 UTCresolved

   This incident has been resolved.

1. 25. juni 2026 kl. 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. juni 2026 kl. 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. juni 2026 kl. 23.32 UTCresolved

   This incident has been resolved.

1. 22. juni 2026 kl. 21.27 UTCinvestigating

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

2. 22. juni 2026 kl. 22.28 UTCinvestigating

   We are continuing to investigate this issue.

3. 22. juni 2026 kl. 22.37 UTCmonitoring

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

4. 22. juni 2026 kl. 22.41 UTCresolved

   This incident has been resolved.

1. 18. juni 2026 kl. 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. juni 2026 kl. 16.22 UTCmonitoring

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

3. 18. juni 2026 kl. 16.33 UTCresolved

   This incident has been resolved.

1. 16. juni 2026 kl. 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. juni 2026 kl. 18.23 UTCidentified

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

3. 16. juni 2026 kl. 18.29 UTCmonitoring

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

4. 16. juni 2026 kl. 18.33 UTCresolved

   This incident has been resolved.

1. 12. juni 2026 kl. 17.12 UTCidentified

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

2. 12. juni 2026 kl. 19.01 UTCidentified

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

3. 12. juni 2026 kl. 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. juni 2026 kl. 19.23 UTCmonitoring

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

5. 12. juni 2026 kl. 19.39 UTCresolved

   This incident has been resolved.

1. 8. juni 2026 kl. 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. juni 2026 kl. 11.21 UTCmonitoring

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

3. 8. juni 2026 kl. 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. juni 2026 kl. 12.59 UTCresolved

   This incident has been resolved.

1. 16. maj 2026 kl. 02.17 UTCinvestigating

   We are investigating an issue submitting Azure metrics.

2. 16. maj 2026 kl. 02.40 UTCidentified

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

3. 16. maj 2026 kl. 03.09 UTCidentified

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

4. 16. maj 2026 kl. 03.27 UTCmonitoring

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

5. 16. maj 2026 kl. 03.43 UTCresolved

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