PagerDuty reported "Issue Identified - Errors utilizing the PagerDuty MCP" on its status page at 2026-09-22 16:03 UTC.

PagerDuty did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-09-22 16:03 UTC and ended at 2026-09-22 16:59 UTC. It lasted 56 min.

How do I get alerts for PagerDuty?

Subscribe to the PagerDuty live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of PagerDuty. outages.live reads it every few minutes and keeps every update.

PagerDutyIncident · 2026-09-22 16:03 UTC

Issue Identified - Errors utilizing the PagerDuty MCP

ResolvedOfficial update

We have resolved an incident where PagerDuty customers in the US Service Region were experiencing issues with our public MCP. Impacted customers may have seen 500 errors using our MCP. Event ingestion and incident notification delivery are not affected.

The latest update from PagerDuty.

State

Resolved

Started

40 d ago

2026-09-22 16:03 UTC

Lasted

56 min

until 2026-09-22 16:59 UTC

Worst impact

Degraded

Timeline

4 updates

16:0316:1716:3116:4516:59

DegradedUpdate postedTimes in UTC

Investigating

21 min 37%

Detected

35 min 63%

Updates

Times in UTC

As posted by PagerDuty

Resolved2026-09-22 16:59 UTC

Detected2026-09-22 16:48 UTC

We are seeing improvement with the incident where PagerDuty customers in the US Service Region are experiencing issues with our public MCP. Impacted customers may see 500 or 429 errors using our MCP. Event ingestion and incident notification delivery are not affected. We will provide further...

Detected2026-09-22 16:23 UTC

We are continuing to investigate an incident where PagerDuty customers in the US Service Region are experiencing issues with our public MCP. Impacted customers may see 500 errors using our MCP. Event ingestion and incident notification delivery are not affected. We will provide further updates...

Investigating2026-09-22 16:03 UTC

We are investigating an incident where PagerDuty customers in the US Service Region are experiencing issues with our public MCP. Impacted customers may see 500 errors using our MCP. Event ingestion and incident notification delivery are not affected. We will provide further updates within 20...

PagerDuty in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

33 min

This incident

1.7× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

3 h 20 min

median 33 min

90 days agoToday

Other PagerDuty incidents

All incidents

PagerDuty·Issue Resolved - Delays Across the PagerDuty Platform

We have resolved an incident where all PagerDuty customers in the US service region experienced issues with delays in incident notifications. Event ingestion was not affected. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to support@pagerduty.com if...

Resolvedresolved 9 d ago

PagerDuty·Issue Resolved - Delays Across the PagerDuty Platform

We have resolved an incident where all PagerDuty customers in the US service region experienced issues with delays across the PagerDuty platform. Event ingestion was not affected. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to support@pagerduty.com...

Resolvedresolved 13 d ago

PagerDuty·Issue Resolved - Delayed escalation of incidents and responder request invitations

We have identified and resolved an incident where PagerDuty customers in the US Service Region were experiencing issues with escalation of incidents and responder requests. The incident is now resolved, and there is no ongoing impact to customers. Event ingestion and incident notification...

Resolvedresolved 18 d ago

PagerDuty·Event Processing, Notification, and Platform Functionality Issues

We have resolved an incident where PagerDuty customers in the US service region may have experienced delayed event ingestion and notifications. Performance has recovered across impacted services, including incident creation, alert attachments, web UI, Ops Console, email fan-out, and incident...

Resolvedresolved 36 d ago

PagerDuty·Issue Identified - Incident Workflows experiencing delays

We have resolved an incident where customers in all Service Regions were experiencing issues with Incident Workflows. Impacted customers may have seen delays with a run Javascript action in Incident Workflows that could have caused delays with workflow related notifications. Event ingestion and...

Resolvedresolved 37 d ago

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

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane