67 Datadog incidents · 2025年7月 — official updates, affected components, duration and resolution details.
我们正在调查增加的潜伏处理 CCD优化,代码覆盖,代码安全, 和DORA的数据。 由于这个问题,一些用户可能会看到测试运行和准备处决的拖延.
我们确定了问题所在.
我们正在监测这个问题.
我们已经采取了补救措施,恢复工作正在进行。 我们正在继续监测这一问题.
这个问题现已解决.
自动翻译自官方事件更新。
我们正在调查监测评估的延误,评估始于协调世界时2026年9月2日12:10.
我们确定了问题所在.
我们正在监测这个问题.
这个问题现已解决.
自动翻译自官方事件更新。
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:35开始.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个拖延摄取真实用户监测(RUM)计量度量衡、自定义流程度量衡以及一些客户分配度量衡子的问题。 因此,一些用户可能在RUM,自定义流程,以及发行度量衡中看到延迟或空白. 为防止被延迟的数据所引发的虚假警报,受到影响的显示器不会通知,一旦获得当前数据后将自动恢复. 所有其他监视器将正常运行。 没有丢失数据 。 我们将随着局势的发展提供进一步的最新情况.
我们正在继续调查这一问题.
这一问题已经确定,一个解决办法正在实施之中.
RUM的拖延已经解决了. 我们正在继续缓解分配指标的问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个进行合成测试的问题.
我们正在继续调查一期出版合成结果 合成测试正在进行,结果被延迟.
我们已经确定了出版合成结果的问题。 合成试验仍在继续进行,结果有延误.
已经实施了一个固定,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查Pages和Monitor的状态变化增加的延迟。 由于这个问题,一些用户可能会看到延误.
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.