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

Affected components

• Monitors

1. resolvedApr 10, 2026, 20:59 UTC

   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. During this window, notifications to the following integrations were delayed or temporarily undelivered: • PagerDuty • Slack • Microsoft Teams • Webhooks • Jira • ServiceNow • OpsGenie • VictorOps • BigPanda • Zendesk • Sumologic All delayed notifications have been replayed with the following exceptions: PagerDuty pages and Slack notifications queued during the outage window were not replayed, as they were no longer actionable at the time of recovery. Webhook notifications will be reprocessed and delivered at a later date. No monitoring data was lost during this incident. Monitor evaluations continued normally — only the delivery of triggered notifications was affected. Thank you for your patience.

2. monitoringApr 10, 2026, 20:13 UTC

   Webhooks and Slack notifications are still catching up.

3. monitoringApr 10, 2026, 19:44 UTC

   Webhooks and Slack notifications are still catching up.

4. monitoringApr 10, 2026, 19:02 UTC

   Webhooks and Slack notifications are still catching up.

5. monitoringApr 10, 2026, 18:33 UTC

   Notifications for ServiceNow and Microsoft Teams are now caught up. Webhooks and Slack notifications are still catching up.

6. monitoringApr 10, 2026, 17:37 UTC

   Notifications for JIRA are now caught up.

7. monitoringApr 10, 2026, 17:12 UTC

   Notifications for Opsgenie, VictorOps, BigPanda, Zendesk, and Sumologic are caught up. Webhooks, Microsoft Teams, Slack, JIRA, and ServiceNow are still catching up.

8. monitoringApr 10, 2026, 16:15 UTC

   We are still catching-up on past notifications that may have been delayed.

9. monitoringApr 10, 2026, 15:59 UTC

   We are still catching-up on past notifications that may have been delayed.

10. monitoringApr 10, 2026, 15:42 UTC

    New notifications are now successfully delivered, and we are catching-up on past notifications that may have been delayed

11. identifiedApr 10, 2026, 15:42 UTC

    New notifications are now successfully delivered, and we are catching-up on past notifications that may have been delayed.

12. identifiedApr 10, 2026, 15:23 UTC

    We are continuing to work on a fix for this issue.

13. identifiedApr 10, 2026, 15:00 UTC

    The issue has been identified and a fix is being implemented.

14. investigatingApr 10, 2026, 14:54 UTC

    We are investigating an issue to send notifications to Pagerduty, VictorOps, Slack, Webhook, Microsoft Teams and OpsGenie.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Datadog's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Confluent Cloud: Elevated error rates in AWS me-south-1 and me-central-1 regionsMajor · Apr 1, 2026, 19:52 UTC
• Elasticsearch: Privatelink hostnames reported by API are incorrectMajor · Apr 9, 2026, 20:46 UTC

How often does Datadog have incidents?

Datadog reported 12 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 47 min. See Datadog's uptime and incident history