Störungsverlauf von Datadog

1. 3. September 2026 um 17:20 UTCinvestigating

   Wir untersuchen erhöhte Latenzverarbeitung CICD Optimierung, Code Coverage, Code Security und DORA Daten. Als Folge dieses Problems können einige Benutzer Verzögerungen bei Testläufen und Pipelineausführungen sehen.

2. 3. September 2026 um 17:59 UTCidentified

   Wir haben das Problem erkannt.

3. 3. September 2026 um 19:01 UTCmonitoring

   Wir verfolgen das Problem.

4. 3. September 2026 um 21:51 UTCmonitoring

   Wir haben Abhilfemaßnahmen ergriffen, und die Rückforderung ist im Gange. Wir verfolgen die Angelegenheit weiterhin.

5. 3. September 2026 um 23:01 UTCresolved

   Das Problem ist nun gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 2. September 2026 um 01:07 UTCinvestigating

   Wir untersuchen Verzögerungen bei der Monitorauswertung, die am 2. September 2026, 12:10 Uhr UTC begannen.

2. 2. September 2026 um 01:16 UTCidentified

   Wir haben das Problem erkannt.

3. 2. September 2026 um 01:21 UTCmonitoring

   Wir verfolgen das Problem.

4. 2. September 2026 um 01:24 UTCresolved

   Das Problem ist nun gelöst.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

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

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

3. 6. August 2026 um 19:27 UTCmonitoring

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

4. 6. August 2026 um 19:37 UTCresolved

   This incident has been resolved.

1. 30. Juli 2026 um 07:44 UTCinvestigating

   Wir untersuchen Verzögerungen bei der Bewertung von Service Check-Monitoren, die um 6:35 Uhr UTC begannen.

2. 30. Juli 2026 um 07:49 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 30. Juli 2026 um 08:16 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 30. Juli 2026 um 08:27 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 29. Juli 2026 um 15:41 UTCinvestigating

   Wir untersuchen derzeit ein Problem, das die Aufnahme von Real User Monitoring (RUM) Messmetriken, benutzerdefinierten Prozessmetriken und einer Teilmenge von Verteilungsmetriken für einige Kunden verzögert. Infolgedessen können einige Benutzer Verzögerungen oder Lücken in RUM, benutzerdefinierten Prozess- und Verteilungsmetriken sehen. Um Fehlalarme durch verzögerte Daten zu verhindern, werden betroffene Monitore nicht benachrichtigt und automatisch wieder aufgenommen, sobald aktuelle Daten verfügbar sind. Alle anderen Monitore funktionieren normal. Es sind keine Daten verloren gegangen. Wir werden weitere Updates bereitstellen, wenn die Situation fortschreitet.

2. 29. Juli 2026 um 15:42 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 29. Juli 2026 um 16:35 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

4. 29. Juli 2026 um 16:53 UTCidentified

   Die RUM-Verzögerungen wurden behoben. Wir werden weiterhin die Probleme mit den Verteilungsmetriken mildern.

5. 29. Juli 2026 um 17:12 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

6. 29. Juli 2026 um 17:28 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 27. Juli 2026 um 19:05 UTCinvestigating

   Wir untersuchen derzeit ein Problem mit synthetischen Tests.

2. 27. Juli 2026 um 19:25 UTCinvestigating

   Wir untersuchen weiterhin ein Problem, das synthetische Ergebnisse veröffentlicht. Synthetische Tests laufen und die Ergebnisse verzögern sich.

3. 27. Juli 2026 um 19:36 UTCidentified

   Wir haben das Problem identifiziert, Synthetische Ergebnisse zu veröffentlichen. Synthetische Tests laufen weiterhin mit verzögerten Ergebnissen.

4. 27. Juli 2026 um 19:46 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

5. 27. Juli 2026 um 19:52 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 23. Juli 2026 um 17:08 UTCinvestigating

   Wir untersuchen erhöhte Latenz mit Pages und Monitor Zustandsänderungen. Als Folge dieses Problems können einige Benutzer Verzögerungen sehen.

2. 23. Juli 2026 um 17:31 UTCidentified

   Das Problem wurde identifiziert und ein Fix wird implementiert.

3. 23. Juli 2026 um 18:02 UTCmonitoring

   Ein Fix wurde implementiert und wir überwachen die Ergebnisse.

4. 23. Juli 2026 um 18:13 UTCresolved

   Dieser Vorfall wurde behoben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

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

   We are continuing to investigate the issue.

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

   This incident has been resolved.

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

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

3. 3. Juli 2026 um 01:21 UTCmonitoring

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

4. 3. Juli 2026 um 01:29 UTCresolved

   This incident has been resolved.

1. 1. Juli 2026 um 18:31 UTCinvestigating

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

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

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

4. 1. Juli 2026 um 19:19 UTCmonitoring

   We have deployed mitigation actions and are monitoring the recovery.

5. 1. Juli 2026 um 19:43 UTCmonitoring

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

6. 1. Juli 2026 um 20:37 UTCresolved

   This incident has been resolved.

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

   We are continuing to investigate this issue.

3. 30. Juni 2026 um 18:57 UTCidentified

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

4. 30. Juni 2026 um 19:06 UTCidentified

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

5. 30. Juni 2026 um 19:36 UTCmonitoring

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

6. 30. Juni 2026 um 20:32 UTCresolved

   This incident has been resolved.

1. 30. Juni 2026 um 10:35 UTCinvestigating

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

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

   This incident has been resolved.

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

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

3. 26. Juni 2026 um 13:45 UTCresolved

   This incident has been resolved.

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

   This incident has been resolved.

1. 22. Juni 2026 um 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 um 22:28 UTCinvestigating

   We are continuing to investigate this issue.

3. 22. Juni 2026 um 22:37 UTCmonitoring

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

4. 22. Juni 2026 um 22:41 UTCresolved

   This incident has been resolved.

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

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

3. 18. Juni 2026 um 16:33 UTCresolved

   This incident has been resolved.

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

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

3. 16. Juni 2026 um 18:29 UTCmonitoring

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

4. 16. Juni 2026 um 18:33 UTCresolved

   This incident has been resolved.

1. 12. Juni 2026 um 17:12 UTCidentified

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

2. 12. Juni 2026 um 19:01 UTCidentified

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

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

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

5. 12. Juni 2026 um 19:39 UTCresolved

   This incident has been resolved.

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

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

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

   This incident has been resolved.

1. 16. Mai 2026 um 02:17 UTCinvestigating

   We are investigating an issue submitting Azure metrics.

2. 16. Mai 2026 um 02:40 UTCidentified

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

3. 16. Mai 2026 um 03:09 UTCidentified

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

4. 16. Mai 2026 um 03:27 UTCmonitoring

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

5. 16. Mai 2026 um 03:43 UTCresolved

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