67 Datadog incidents · 2025年7月 — official updates, affected components, duration and resolution details.
CICDの最適化、コードカバレッジ、コードセキュリティ、DORAデータ処理の遅延の増加を調査しています。 この問題の結果として、一部のユーザーは、テストの実行とパイプラインの実行の遅延を見ることができます.
問題を特定しました.
問題を監視しています.
修正を加え、回復が進んでいます。 問題を監視し続けています.
問題は解決しました.
公式のインシデント更新を自動翻訳しています。
2026年9月2日、12:10 AM UTCにてモニター評価の遅延を調査しています.
問題を特定しました.
問題を監視しています.
問題は解決しました.
公式のインシデント更新を自動翻訳しています。
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
6:35AM UTCにてサービスチェックモニター評価の遅延を調査しています.
問題が特定され、修正が実装されています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
現在、Real User Monitoring (RUM) の測定メトリック、カスタム プロセス メトリック、および一部の顧客の分布メトリックのサブセットを遅延する問題について調査しています。 その結果、一部のユーザーは、RUMの遅延やギャップ、カスタムプロセス、および分布メトリックを見ることができます。 遅延データによる誤警報を防ぐため、影響を受けたモニターが通知されず、現在データが利用可能になったら自動的に再開されます。 他のすべてのモニターは普通作動します。 データの紛失は行いません。 状況が進むにつれて、さらなるアップデートが提供されます.
今後もこの問題について調査を続けてまいります.
問題が特定され、修正が実装されています.
RUM遅延が解決しました。 分布メトリックに関する問題を軽減し続けています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
合成テストを実行している問題の調査を行っています.
発行の合成結果の調査を続けております。 合成テストが実行され、結果が遅延します.
合成結果を発行する問題を特定しました。 合成テストは、結果が遅れて実行し続けています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
ページやモニターの状態の変化でレイテンシーを増加させる調査を行っています。 この問題の結果として、一部のユーザーは遅延が発生する可能性があります.
問題が特定され、修正が実装されています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
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.
We are continuing to investigate the issue.
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.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are actively investigating elevated error rates across multiple Datadog products.
We are investigating elevated error rates across multiple products including: Fleet Automation, Security Products, Cloudcraft, Cloud Network Monitoring, Serverless, Kubernetes Autoscaling, and Database Monitoring.
We have identified the issue of elevated error rates and are working through mitigation actions
We have deployed mitigation actions and are monitoring the recovery.
We are continuing to monitor the situation and are taking additional preventive measures.
This incident has been resolved.
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.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating delays in Monitors Notifications, which began at 09:52 UTC.
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.
We have deployed a fix and we are monitoring the results. We will provide another update once the issue is fully resolved.
This incident has been resolved.
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..
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating increased latency processing CI Visibility data. As a result of this issue, some users may see delays with pipeline executions.
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.
This incident has been resolved.
We are currently investigating elevated latency on metrics queries. We will provide an update as soon as possible.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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..
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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)
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating delays in monitor evaluation, which began at 16:10 UTC.
We are continuing to work on a fix for this issue.
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
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
We have deployed a fix and we are monitoring the results.
We are continuing to monitor the fix deployed earlier. We will provide another update once the issue is fully resolved.
This incident has been resolved.
We are investigating an issue submitting Azure metrics.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved and Azure metrics are reporting as expected.