Elevated Error Rates Across Web UI Actions
PagerDuty reports elevated error rates for some customers in the US Service Region when they use actions on the web interfaces. The Web Application (US) component is affected. Event ingestion and incident notification delivery are not affected. PagerDuty is investigating and has implemented a mitigation. The incident started at 16:44 UTC and continues.
State
Investigating
Started
Ongoing for
1 h 3 min
Worst impact
Partial outage
Timeline
4 updatesInvestigating
1 h 3 min 100%
Updates
Times in UTCAs posted by PagerDuty
We are continuing to investigate an incident where some PagerDuty customers in the US Service Region are experiencing elevated error rates when performing various actions against the web interfaces. We have implemented a mitigation and are currently monitoring system behavior for signs of...
We are continuing to investigate an incident where some PagerDuty customers in the US Service Region are experiencing issues with elevated error rates when performing various actions against the web interfaces. Event ingestion and incident notification delivery are not affected. We will provide...
We are continuing to investigate an incident where some PagerDuty customers in the US Service Region are experiencing issues with elevated error rates when performing various actions against the web interfaces. Event ingestion and incident notification delivery are not affected. We will provide...
We are investigating an incident where some PagerDuty customers in the US Service Region are experiencing issues with elevated error rates when performing various actions against the web interfaces. Event ingestion and incident notification delivery are not affected. We will provide further...
Affected components
1PagerDuty in the last 90 days
Full historyIncidents in 90 days
11
Days with an incident
10
Median duration
45 min
This incident
1.4× the median
Other PagerDuty incidents
All incidentsPagerDuty·Issues with WhatsApp notifications
PagerDuty WhatsApp notifications had issues in the US and EU regions. Some customers saw duplicate WhatsApp notifications and could not acknowledge or resolve incidents by replying. The incident is resolved and lasted about 4 hours.
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...
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...
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.live/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.live/feed.xml?providers=pagerduty/feed subscribe https://outages.live/feed.xml?providers=pagerdutyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane