Live

PagerDuty

PagerDuty is operational

Checked 44 s ago Operational

History

90 days agoToday

Incidents in 90 days

12

Days with an incident

11

Median duration

33 min

Longest incident

3 h 20 min

Components

65
Runbook Automation Operational
90 days agoNo incidentsToday
Workflow Automation Operational
90 days agoNo incidentsToday
Events API (US) Operational
90 days ago2 days with an incidentToday
Events API (EU) Operational
90 days agoNo incidentsToday
Incident Timeline and Alert Logs (EU) Operational
90 days agoNo incidentsToday
Incident Timeline and Alert Logs (US) Operational
90 days ago1 day with an incidentToday
Services (US) Operational
90 days agoNo incidentsToday
Services (EU) Operational
90 days agoNo incidentsToday
SMS (US) Operational
90 days ago4 days with an incidentToday
SMS (EU) Operational
90 days agoNo incidentsToday
Voice (US) Operational
90 days ago4 days with an incidentToday
Voice (EU) Operational
90 days agoNo incidentsToday
Push (US) Operational
90 days ago4 days with an incidentToday
Push (EU) Operational
90 days agoNo incidentsToday
Email (US) Operational
90 days ago4 days with an incidentToday
Email (EU) Operational
90 days agoNo incidentsToday
Responder Requests (US) Operational
90 days ago2 days with an incidentToday
Responder Requests (EU) Operational
90 days agoNo incidentsToday
Internal Status Page (US) Operational
90 days agoNo incidentsToday
Internal Status Page (EU) Operational
90 days agoNo incidentsToday
Webhooks (US) Operational
90 days ago2 days with an incidentToday
Webhooks (EU) Operational
90 days agoNo incidentsToday
Schedules and Escalation Policies (US) Operational
90 days ago1 day with an incidentToday
Schedules and Escalation Policies (EU) Operational
90 days agoNo incidentsToday

Past incidents

Provider status pageTimes in UTC

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.

Prompt
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.

RSS
https://outages.cc/feed.xml?providers=pagerduty
Slack
/feed subscribe https://outages.cc/feed.xml?providers=pagerduty

Go from tracking outages to fixing production issues with Polylane.

Try Polylane