← Back to the carnage
DATADOG
🟠 Datadog's monitor evaluations decided to process at geological timescales. They've identified the problem and are 'implementing a fix'—which in status-page speak means the oncall engineer finally stopped screaming into the void. (Auto-resolved: no updates in 24h)
// The official story
Delays in Monitor Evaluations
// Status page says
Feb 5 , 12:01 EST Update - We are observing recovery for the vast majority of monitors and are continuing to work on a full fix for this issue. Feb 5 , 11:50 EST Update - We are continuing to work on a fix for this issue. Feb 5 , 11:31 EST Identified - The issue has been identified and a fix is being implem
🔗 Official status page (for the PR-approved version)
https://status.datadoghq.com/incidents/g545g04n9xkrDatadog's Greatest Hits
🟢 DATADOG
Jul 29, 2026
🟡 Datadog's observability tools can't observe their own problems—RUM metrics, custom processes, and distributions are MIA. The irony is *chef's kiss*. Engineers are investigating, which means hitting F5 on their status page hoping for good news. (Auto-resolved: no updates in 24h)
🟢 DATADOG
Jul 03, 2026
🟡 Datadog's image registry decided to play hide-and-seek with container pulls. New deployments are getting ghosted, but your already-running containers are blissfully unaware of the chaos. Engineers are investigating why their own infrastructure won't cooperate with them. (Auto-resolved: no updates in 24h)
🟢 DATADOG
Apr 15, 2026
🟠 Datadog's Distribution Metrics decided speed is overrated—users watching their graphs load slower than dial-up. The irony of a monitoring tool that needs monitoring is apparently lost on everyone. (Auto-resolved: no updates in 24h)
🟢 DATADOG
Apr 10, 2026
🔴 Datadog's notification pipeline decided to go dark for an hour across US1, AP1, and AP2 regions. PagerDuty pages and Slack alerts got yeeted into the void and stayed there. Everything's 'resolved' now, but your oncall team probably still has trust issues. (Auto-resolved: no updates in 24h)