PagerDuty's notification delivery broke for 1h 44m starting at 21:42 UTC, hitting twelve components across its US region at once. This was on PagerDuty's own status page, not a guess from the outside.
Started
21:42 UTC
Duration
Lasted 1h 44m
Source
IsDown
Next time
PagerDuty is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Email (US), SMS (US), Voice (US), Push (US), External Status Page (US), PagerDuty Advance, Microsoft Teams (US), Incident Workflows (US), Web Application (US), Incident Timeline and Alert Logs (US), Business Services and Status Dashboard (US), Slack (US)
What happened?
PagerDuty opened an incident at 21:42 UTC titled "Investigating: Notification Delivery" and closed it 1h 44m later. Twelve components were listed as affected, covering SMS (US), Voice (US), Email (US), Push (US), Slack (US), Microsoft Teams (US), the Web Application (US), the External Status Page (US), Incident Workflows (US), Incident Timeline and Alert Logs (US), Business Services and Status Dashboard (US), and PagerDuty Advance. That spread matters because notification delivery is PagerDuty's core job: if it breaks, every channel that depends on it breaks with it, which is exactly what the component list shows. PagerDuty published no updates during the incident, so there is no timeline of what was tried, what was found, or when things started recovering. No user reports were filed during the window, which is unusual for an incident touching this many channels, but it is what the record shows. There is no cause on record. PagerDuty did not say whether this was a backend fault, a third-party notification provider issue, or something else. Over the past 90 days PagerDuty has logged 11 incidents with a median duration of 56 minutes, so this one ran longer than typical for the company. Across all time PagerDuty averages 3.9 incidents a month, putting this squarely within its normal pace of disruptions rather than an outlier event. No post-mortem has been published for this incident.
Learning
When a notification platform fails, your own monitoring of your endpoints tells you nothing about it, because the fault sits entirely on PagerDuty's side between your alert trigger and the channel that's supposed to deliver it. UptimeRobot's own checks over the last 30 days recorded 5 incidents on PagerDuty, all resolved, with a median duration of 56m, a pattern consistent with what showed up this day. The failure shape here is a single point breaking many downstream channels at once: SMS, voice, email, push, Slack and Teams integrations all rode on the same notification delivery layer, so one fault took all of them down together. This is the kind of outage you would only catch by watching PagerDuty itself, since your own systems would have fired the alert correctly and simply never heard back that it arrived. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.