Changes / Datadog / Intermittent "No Data" Status for Monitors
Datadog: Major incident: Intermittent "No Data" Status for Monitors
Summary
Datadog reported a major incident where some metric monitors intermittently showed "No Data," primarily affecting distribution-metric monitors and making alerting potentially unreliable. It started at 2026-03-19 00:54 UTC and lasted 1 h 59 min, resolving at 2026-03-19 02:53 UTC; a fix was implemented.
Machine-written from the diff below (Sol; type: incident degradation). Check the diff before relying on it.
Major incidentLabel: degradation (model (Jev), 92%)Changed Detected Source: stspg.io (opens in new tab)
What changed
Before: not present
After: Intermittent "No Data" Status for Monitors
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-03-19 00:54 UTC
Before: not present
After: 2026-03-19 02:53 UTC
Before: not present
After: Monitors
Before: not present
After: We are investigating an issue causing some metric monitors to intermittently report "No Data" status. This primarily affects monitors based on distribution metrics. Monitor alerting may be unreliable during this time. We are actively investigating and will provide updates as available.
Before: not present
After: We are continuing to investigate the issue and will provide updates as available.
Before: not present
After: We are continuing to investigate the issue and will provide updates as available.
Before: not present
After: A fix has been implemented and we are monitoring the results.
Before: not present
After: This incident has been resolved.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Intermittent "No Data" Status for Monitors (this change) Datadog reported a major incident where some metric monitors intermittently showed "No Data," primarily affecting distribution-metric monitors and making alerting potentially unreliable. It started at 2026-03-19 00:54 UTC and lasted 1 h 59 min, resolving at 2026-03-19 02:53 UTC; a fix was implemented. | Major incident |