PagerDuty
PagerDuty is operational
History
Incidents in 90 days
12
Days with an incident
11
Median duration
33 min
Longest incident
3 h 20 min
Components
65Sep 16, 2026
We have resolved an incident where some PagerDuty customers in the US service region experienced issues with delayed event processing. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to support@pagerduty.com</...status.pagerduty.com
We have identified and resolved an incident where PagerDuty customers in both the EU and US service regions experienced an incorrect message popup being displayed upon login to their account regarding paused notifications. The popup message has been removed. The incident is now resolved, and...status.pagerduty.com
Follow PagerDuty
Your coding agent knows when PagerDuty is down, and tells you when a failure is theirs, not yours. You can also get PagerDuty incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "pagerduty" and tell me if PagerDuty has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=pagerduty/feed subscribe https://outages.cc/feed.xml?providers=pagerdutyGo from tracking outages to fixing production issues with Polylane.
Try Polylane