DATADOG

🔴 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)

⏰ Apr 10, 2026 Fixed (for now) spotted via status_rss

// The official story

Notifications to Pagerduty, VictorOps, Slack, Webhook, Microsoft Teams and OpsGenie are not delivered

// Status page says

Apr 10 , 16:59 EDT Resolved - The issue impacting notification delivery has been fully resolved. Between approximately 9:42 AM and 10:38 AM ET on April 10 we observed delivery failures for customers in the US1, AP1, and AP2 regions. All delayed notifications have been replayed with the following two exceptions: PagerDuty pages and Slack notifications queued during the outage window were not replayed, as they were no longer actionable a

🔗 Official status page (for the PR-approved version)

https://status.datadoghq.com/incidents/q2njm9l08tjb

Datadog'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 Feb 05, 2026

🟠 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)