Incident Workflow, SRE Agent, Search, and Status Page Issues
We have resolved an incident where PagerDuty customers in the US service region experienced issues with with Incident Workflows and the PagerDuty Advance SRE Agent. The issue with duplicated notifications from our Status page has also been resolved. Event ingestion and incident notification...
The latest update from PagerDuty.
State
Resolved
Started
59 d ago
2026-09-03 22:21 UTC
Lasted
1 h 7 min
until 2026-09-03 23:29 UTC
Worst impact
Degraded
Timeline
5 updatesInvestigating
1 h 7 min 100%
Updates
Times in UTCAs posted by PagerDuty
We have resolved an incident where PagerDuty customers in the US service region experienced issues with with Incident Workflows and the PagerDuty Advance SRE Agent. The issue with duplicated notifications from our Status page has also been resolved. Event ingestion and incident notification...
We are continuing to monitor improvement in an incident with Incident Workflows and the PagerDuty Advance SRE Agent, and we expect systems to continue to improve. We are also investigating issues with our Status Page sending duplicate updates. Event ingestion and incident notification delivery...
We are monitoring improvement in an incident with Incident Workflows and the PagerDuty Advance SRE Agent. We are expecting systems to continue to improve. Event ingestion and incident notification delivery are not affected. We will provide an update within the next 15 minutes.
We are continuing to investigate an incident where some PagerDuty customers in the US service region are experiencing issues with Incident Workflows starting or completing. Additionally, customers using the PagerDuty Advance SRE Agent may see errors when using connectors. Event ingestion and...
We are investigating an incident where some PagerDuty customers in the US service region are experiencing issues with Incident Workflows. Impacted customers may see Incident Workflows fail to start or complete. Event ingestion and incident notification delivery are not affected. We will provide...
Affected components
2PagerDuty in the last 90 days
Full historyIncidents in 90 days
12
Days with an incident
11
Median duration
33 min
This incident
2.0× the median
Other PagerDuty incidents
All incidentsPagerDuty·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...
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...
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...
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...
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...
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=pagerdutyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane