PagerDuty favicon

PagerDuty outage on 2026-10-23

pagerduty.com
October 2026 23 Major incident

PagerDuty's notification delivery broke for 36 minutes on 23 October 2026, delaying incident alerts sent by SMS, voice, email and push in the US. The fault sat on PagerDuty's side, in the pipeline that gets an alert from their system to yours.

Started

22:34 UTC

Duration

Lasted 36m

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: Voice (US), Email (US), SMS (US), Push (US)

What happened?

PagerDuty logged one incident on 23 October 2026, titled "Issue with Delays in Incident Notifications", starting at 22:34 UTC and lasting 36 minutes. Four components were listed as affected: SMS (US), Voice (US), Email (US) and Push (US), meaning every major notification channel for US users was touched at once. PagerDuty published no updates during the incident, so there is no timeline of what they tried or when they considered it fixed beyond the recorded 36 minute duration. No cause has been given. PagerDuty's status page does not say why notifications were delayed, only that they were. No user reports were filed during the window, so there is no first-hand account of how late alerts arrived or whether any were dropped outright rather than delayed. Over the past 90 days, PagerDuty has recorded 11 incidents with a median duration of 36 minutes, which puts this one exactly in line with their recent pattern rather than standing out as unusual. Across all time, PagerDuty averages 3.9 incidents a month, a rate that suggests this kind of brief notification delay is a recurring feature of running the service rather than a rare event. With four channels affected simultaneously and no breakdown of which failed first or worst, it is not possible to say from the record whether one channel was hit harder than the others.

Learning

If you rely on PagerDuty to tell you when something is wrong, this incident is a reminder that the alerting layer itself can be the thing that is broken, and nothing you monitor on your own end would show that. Your probes watch your services and your endpoints, and those can be perfectly healthy while the notification pipeline that should be paging your on-call engineer sits delayed for half an hour. That is the specific shape of this failure: not a crash, not downtime in the usual sense, but delivery that is late across SMS, voice, email and push all at once. PagerDuty's own four 30-day incidents, with a median resolution time of 28 minutes, show this kind of short, self-resolving disruption is their normal operating pattern, not a one-off. Watching your own stack tells you nothing about whether PagerDuty can reach you when it matters. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.