Is PagerDuty down right now?

No. Our checks are finding no problems with PagerDuty right now. That verdict is live, and the banner at the top of this page carries it too. We re-check PagerDuty continuously using its official status feed, direct network probes and reports from visitors, stopping at the first check that gives a clear answer, and the page updates itself as soon as anything changes. A green verdict does not rule out a fault affecting only some users or regions.

The problems visitors report most often on this page are no notifications, API errors, can't connect, webhooks not firing, can't log in, no response / timing out, website / app down and email not arriving. Those are the options the report button offers for PagerDuty, chosen for how this service actually fails rather than a generic list, and the "user reports" chart above breaks down which ones people are picking right now.

Our checks run from one place on the internet, so a fault limited to your region or network can be real while our probes succeed. With PagerDuty specifically, PagerDuty's notification delivery, webhook ingestion, and API endpoints can fail independently. A user's monitoring tool may be able to reach PagerDuty's API but notifications may not route to phones, or webhooks may queue but never fire. That is why this page reports what it observed rather than declaring the service healthy, and why reports from other visitors count toward the verdict.

For PagerDuty, send a test notification from the dashboard to your phone and your email at once. Arriving by email but not as a push or an SMS points at that one channel or your carrier, and the incident timeline records every channel it tried and what each returned. A problem that follows you across networks and devices is very unlikely to be yours.

If this page shows evidence of problems, the fault is most likely on PagerDuty's side. Specifically: do not trigger test incidents to find out whether it is back. They page whoever is genuinely on call, during an outage they are already handling, and they leave duplicate records in the timeline you have to untangle afterwards. Reporting it here helps other people see they are not alone.

Continuously, around the clock. PagerDuty does not publish a machine-readable status feed, so we cannot read a verdict from them. We probe pagerduty.com directly over HTTP, fall back to an ICMP ping if that is inconclusive, and weigh reports from visitors. That means we can tell you the service is unreachable, but not what PagerDuty says about it. The verification tier box on this page names whichever check produced the verdict you are reading, so you can see how direct the evidence is.

Yes, at status.pagerduty.com, and it is linked further up this page. That is PagerDuty's own account of their service and it is the place to look for their estimate of a fix. We read it where we can, but we publish our own observations beside it rather than only repeating theirs, because an operator's status page can lag a problem their users are already hitting.

No. status.buzz is an independent monitoring site operated by LuzLab LLC, with no connection to PagerDuty or pagerduty.com. It reads publicly available endpoints and status feeds, and publishes what it observed. For account or billing problems you need PagerDuty's own support, not us.