PagerDuty had an issue with WhatsApp notifications starting at 18:44 UTC that lasted 3h 52m. The fault sat with PagerDuty's notification delivery, not with your own alerting setup.
Started
18:44 UTC
Duration
Lasted 3h 52m
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.
What happened?
The record shows one incident on this day, titled "Issues with WhatsApp notifications", starting at 18:44 UTC and running for 3h 52m before resolution. PagerDuty published no updates during that window, so there is no account of what broke inside WhatsApp delivery or why it took nearly four hours to clear. No components are listed as affected on PagerDuty's status page for this incident, which tells you the provider scoped the problem narrowly rather than flagging a wider platform issue. No user reports were filed during the window, so there is no firsthand account of what this looked like for someone waiting on a WhatsApp alert. Over the past 90 days PagerDuty has logged 10 incidents with a median duration of 46 minutes, which puts this one well above typical. Across all time PagerDuty has recorded 302 incidents, averaging 3.9 a month, so incidents of some kind are a regular feature of this provider's history, even if most resolve faster than this one did. With zero updates published, the single filing of the incident itself is the only record of what happened, and it carries exactly as much weight as that: an opening and a closing timestamp, nothing more. PagerDuty's status page does not say why WhatsApp notifications failed, and no post-mortem has been published.
Learning
This incident sat specifically in notification delivery over WhatsApp, a channel that depends on PagerDuty's integration with WhatsApp's own messaging infrastructure, not on anything running in your product. If your own monitoring of your endpoints stayed green through this window, that is because the fault never touched your infrastructure. It lived entirely on the delivery path between PagerDuty and WhatsApp, a layer your own checks have no visibility into. UptimeRobot's own 30 day figures for PagerDuty show 4 incidents, all resolved, with a median duration of 1h 10m, which gives you a sense of how this provider behaves even when nothing makes the news. The lesson here is a narrow one: a failure in a third party notification channel will not show up in checks aimed at your own servers, however carefully you run them. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.