PagerDuty Outage History

PagerDuty is up right now

PagerDuty had 49 outages in the last 2 years totaling 220h 23m of downtime — averaging 2 incidents per month.

There were 49 PagerDuty outages since November 4, 2025 totaling 220h 23m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pagerduty.com

Minor October 19, 2026

Investigating: Notification Delivery

Detected by Pingoru
Oct 19, 2026, 09:38 PM UTC
Resolved
Oct 19, 2026, 11:24 PM UTC
Duration
1h 46m
Affected: Incident Timeline and Alert Logs (US) (Incident Timeline and Alert Logs (US))SMS (US) (SMS (US))Voice (US) (Voice (US))Push (US) (Push (US))Email (US) (Email (US))Business Services and Status Dashboard (US) (Business Services and Status Dashboard (US))Web Application (US) (Web Application (US))External Status Page (US) (External Status Page (US))Microsoft Teams (US) (Microsoft Teams (US))Slack (US) (Slack (US))Incident Workflows (US) (Incident Workflows (US))PagerDuty Advance (PagerDuty Advance)
Timeline · 8 updates
  1. identified Oct 19, 2026, 09:38 PM UTC

    We are investigating an issue affecting notification delivery in PagerDuty. We will provide details and recommended actions within 15 minutes.

  2. investigating Oct 19, 2026, 10:16 PM UTC

    We are investigating an incident where all PagerDuty customers in the US Service Region are experiencing delays across the platform, including incident notifications, webhook deliveries, and Incident Workflows. We have identified the root cause and are working on a remediation for the incident....

  3. investigating Oct 19, 2026, 10:21 PM UTC

    We are monitoring improvement in an incident with delays across the PagerDuty platform. We have deployed a fix, and we expect systems to continue to improve. Event ingestion is not affected. We will provide an update within the next 15 minutes.

  4. investigating Oct 19, 2026, 10:32 PM UTC

    We are continuing to monitor improvement in an incident with delays across the PagerDuty platform. We have deployed a fix, and we expect systems to continue to improve. Event ingestion is not affected. We will provide an update within the next 15 minutes.

  5. investigating Oct 19, 2026, 10:44 PM UTC

    A fix has been deployed and we are seeing continued improvement across the PagerDuty platform. We are monitoring as systems recover. Event ingestion remains unaffected. Our next update will be within 15 minutes.

  6. investigating Oct 19, 2026, 11:03 PM UTC

    We are continuing to monitor improvement in an incident with delays across the PagerDuty platform. We have deployed a fix, and most services have recovered. Business Service impact data and Automated Status Page posts may still be delayed for some customers, and we expect these to continue to...

  7. investigating Oct 19, 2026, 11:15 PM UTC

    Most PagerDuty services have recovered following the fix we deployed. The remaining delays affect Business Service impact data and Automated Status Page posts for some customers, and we are continuing to monitor as these improve. Event ingestion is not affected. Our next update will be within 15...

  8. resolved Oct 19, 2026, 11:24 PM UTC

    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 [email protected]...

Read the full incident report →

Minor October 14, 2026

Issue Resolved - Delayed escalation of incidents and responder request invitations

Detected by Pingoru
Oct 14, 2026, 03:07 PM UTC
Resolved
Oct 14, 2026, 03:24 PM UTC
Duration
17m
Timeline · 2 updates
  1. investigating Oct 14, 2026, 03:07 PM UTC

    We are investigating an incident where PagerDuty customers in the US Service Region are experiencing issues with escalation of incidents and responder requests. Event ingestion and incident notification delivery are not affected. We will provide further updates within 20 minutes.

  2. resolved Oct 14, 2026, 03:24 PM UTC

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

Read the full incident report →

Minor September 27, 2026

Event Processing, Notification, and Platform Functionality Issues

Detected by Pingoru
Sep 27, 2026, 01:22 AM UTC
Resolved
Sep 27, 2026, 01:36 AM UTC
Duration
14m
Affected: Events API (US) (Events API (US))SMS (US) (SMS (US))Voice (US) (Voice (US))Push (US) (Push (US))Email (US) (Email (US))Responder Requests (US) (Responder Requests (US))Web Application (US) (Web Application (US))REST API (US) (REST API (US))Incident Workflows (US) (Incident Workflows (US))
Timeline · 2 updates
  1. investigating Sep 27, 2026, 01:22 AM UTC

    We are investigating an incident where all PagerDuty customers in the US service region may have experienced delayed event ingestion and notifications. Impacted customers may have encountered errors in incident creation, alert attachment, acknowledgements, the web UI, Ops Console, email fan-out,...

  2. resolved Sep 27, 2026, 01:36 AM UTC

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

Read the full incident report →

Minor September 25, 2026

Issue Identified - Incident Workflows experiencing delays

Detected by Pingoru
Sep 25, 2026, 01:39 PM UTC
Resolved
Sep 25, 2026, 02:57 PM UTC
Duration
1h 17m
Affected: Incident Workflows (US) (Incident Workflows (US))Incident Workflows (EU) (Incident Workflows (EU))
Timeline · 4 updates
  1. investigating Sep 25, 2026, 01:39 PM UTC

    We are investigating an incident where PagerDuty customers in all Service Regions are experiencing issues with delays in Incident Workflows. Impacted customers may see delays with a run Javascript action in Incident Workflows. Event ingestion and incident notification delivery are not affected....

  2. identified Sep 25, 2026, 02:08 PM UTC

    We continue to investigate an incident where PagerDuty customers in all Service Regions are experiencing issues with Incident Workflows. Impacted customers may see delays with a run Javascript action in Incident Workflows that can cause delays with workflow related notifications. Event...

  3. investigating Sep 25, 2026, 02:38 PM UTC

    We are monitoring improvement in an incident where PagerDuty 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 cause delays with workflow related notifications.</...

  4. resolved Sep 25, 2026, 02:57 PM UTC

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

Read the full incident report →

Minor September 22, 2026

Issue Identified - Errors utilizing the PagerDuty MCP

Detected by Pingoru
Sep 22, 2026, 04:03 PM UTC
Resolved
Sep 22, 2026, 04:59 PM UTC
Duration
55m
Affected: PagerDuty Advance (PagerDuty Advance)
Timeline · 4 updates
  1. investigating Sep 22, 2026, 04:03 PM 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...

  2. identified Sep 22, 2026, 04:23 PM 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...

  3. identified Sep 22, 2026, 04:48 PM 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...

  4. resolved Sep 22, 2026, 04:59 PM UTC

    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.

Read the full incident report →

Minor September 16, 2026

Event Processing Delays

Detected by Pingoru
Sep 16, 2026, 02:35 PM UTC
Resolved
Sep 16, 2026, 03:08 PM UTC
Duration
32m
Affected: Events API (US) (Events API (US))SMS (US) (SMS (US))Voice (US) (Voice (US))Push (US) (Push (US))Email (US) (Email (US))Responder Requests (US) (Responder Requests (US))Schedules and Escalation Policies (US) (Schedules and Escalation Policies (US))Web Application (US) (Web Application (US))REST API (US) (REST API (US))
Timeline · 3 updates
  1. identified Sep 16, 2026, 02:35 PM UTC

    We are investigating an issue affecting event processing in the US service region. We will provide details and recommended actions within 15 minutes.

  2. investigating Sep 16, 2026, 02:52 PM UTC

    We are investigating an issue affecting event processing in the US service region. Impacted customers may experience delays in event processing. We have identified the cause of the issue and are actively implementing a fix. We will provide further updates within 20 minutes.

  3. resolved Sep 16, 2026, 03:08 PM UTC

    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 [email protected]</...

Read the full incident report →

Minor September 16, 2026

Issue Identified - Notification message

Detected by Pingoru
Sep 16, 2026, 07:59 AM UTC
Resolved
Sep 16, 2026, 08:11 AM UTC
Duration
11m
Affected: Web Application (US) (Web Application (US))Web Application (EU) (Web Application (EU))
Timeline · 2 updates
  1. investigating Sep 16, 2026, 07:59 AM UTC

    We are investigating an incident where PagerDuty customers in all Service Regions are experiencing a notice upon login regarding notifications. Impacted customers may see a notice in the web UI upon login declaring "Your notifications are paused". This message is not correct and notifications are...

  2. resolved Sep 16, 2026, 08:11 AM UTC

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

Read the full incident report →

Minor September 3, 2026

Incident Workflow, SRE Agent, Search, and Status Page Issues

Detected by Pingoru
Sep 03, 2026, 10:21 PM UTC
Resolved
Sep 03, 2026, 11:29 PM UTC
Duration
1h 7m
Affected: External Status Page (US) (External Status Page (US))Incident Workflows (US) (Incident Workflows (US))PagerDuty Advance (PagerDuty Advance)
Timeline · 5 updates
  1. investigating Sep 03, 2026, 10:21 PM UTC

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

  2. investigating Sep 03, 2026, 10:37 PM UTC

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

  3. investigating Sep 03, 2026, 10:44 PM UTC

    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.

  4. investigating Sep 03, 2026, 11:05 PM UTC

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

  5. resolved Sep 03, 2026, 11:29 PM UTC

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

Read the full incident report →

Minor August 13, 2026

404 Error returned in the Web UI for Integration management pages.

Detected by Pingoru
Aug 13, 2026, 11:24 PM UTC
Resolved
Aug 13, 2026, 11:24 PM UTC
Duration
—
Affected: Web Application (US) (Web Application (US))Web Application (EU) (Web Application (EU))
Timeline · 1 update
  1. resolved Aug 13, 2026, 11:24 PM UTC

    We have detected and resolved an incident where all PagerDuty customers in both the US and EU service regions experienced issues accessing integration management pages. Triggering, receiving notifications for, and resolving incidents were NOT impacted by this issue. The incident is now...

Read the full incident report →

Minor August 10, 2026

Issues when attempting to post new incidents to external status pages

Detected by Pingoru
Aug 10, 2026, 05:23 AM UTC
Resolved
Aug 10, 2026, 05:31 AM UTC
Duration
7m
Affected: External Status Page (US) (External Status Page (US))External Status Page (EU) (External Status Page (EU))
Timeline · 3 updates
  1. investigating Aug 10, 2026, 05:23 AM UTC

    We are investigating an incident where some PagerDuty customers are experiencing issues with external status pages. Impacted customers may encounter errors or delays when attempting to post new incidents to their external status pages. Internal incident management, alerting, and...

  2. investigating Aug 10, 2026, 05:26 AM UTC

    We are monitoring improvement in an incident with external status pages. We have deployed a fix, and we expect systems to continue to improve. Internal incident management, alerting, and mobile/web application features remain fully functional.

  3. resolved Aug 10, 2026, 05:31 AM UTC

    We have resolved an incident where some PagerDuty customers in both the US and EU service regions experienced issues with external status pages. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to ...

Read the full incident report →

Minor August 7, 2026

PagerDuty Analytics Dashboard not updating correctly (EU)

Detected by Pingoru
Aug 07, 2026, 07:55 AM UTC
Resolved
Aug 07, 2026, 11:15 AM UTC
Duration
3h 19m
Affected: Analytics (EU) (Analytics (EU))
Timeline · 5 updates
  1. investigating Aug 07, 2026, 07:55 AM UTC

    We are investigating an incident where some PagerDuty customers in the EU Service Region is experiencing issues with the PagerDuty Analytics dashboard. Impacted customers may see the Analytics Dashboard has not updated in 48 hours Event ingestion and incident notification delivery...

  2. investigating Aug 07, 2026, 08:14 AM UTC

    We are continuing to investigate an where some PagerDuty customers in the EU Service Region is experiencing issues with the PagerDuty Analytics dashboard. Impacted customers may see that the Analytics Dashboard has not updated in 48 hours Event ingestion and incident notification...

  3. investigating Aug 07, 2026, 08:39 AM UTC

    We are continuing to investigate an issue where some PagerDuty customers in the EU Service Region are experiencing issues with the PagerDuty Analytics dashboard. Impacted customers may see that the Analytics Dashboard has not updated in 2 days. We have investigated internally, and...

  4. investigating Aug 07, 2026, 09:51 AM UTC

    We are continuing to monitor improvement for an issue where all PagerDuty customers in the EU Service Region experienced issues with the PagerDuty Analytics dashboard. Impacted customers see that the Analytics Dashboard has not updated in 2 days. We have deployed a fix, and we...

  5. resolved Aug 07, 2026, 11:15 AM UTC

    We have resolved an incident where all PagerDuty customers in the EU service region experienced issues with the PagerDuty Analytics dashboard. The Analytics Dashboard is now up to date. Event ingestion and incident notification delivery were not affected. The...

Read the full incident report →

Minor July 24, 2026

Issues accessing PagerDuty Web UI

Detected by Pingoru
Jul 24, 2026, 12:09 PM UTC
Resolved
Jul 24, 2026, 01:23 PM UTC
Duration
1h 14m
Affected: Web Application (US) (Web Application (US))
Timeline · 5 updates
  1. investigating Jul 24, 2026, 12:09 PM UTC

    We are investigating an incident where A small number of PagerDuty customers in The US Service Region are experiencing issues accessing the PagerDuty Web UI. Impacted customers may see "This site can't be reached" error messages trying to access the PagerDuty Web UI. Event ingestion and incident...

  2. investigating Jul 24, 2026, 12:26 PM UTC

    We are investigating an incident where A small number of PagerDuty customers in The US Service Region are experiencing issues accessing PagerDuty Web UI. Impacted customers may see "This site can't be reached" error messages trying to access the PagerDuty Web UI. Event ingestion and incident...

  3. investigating Jul 24, 2026, 12:44 PM UTC

    We are continuing to investigate an incident where A small number of PagerDuty customers in The US Service Region are experiencing issues accessing the PagerDuty Web UI. Impacted customers may see "This site can't be reached" error messages trying to access the PagerDuty Web UI. Event ingestion...

  4. investigating Jul 24, 2026, 12:55 PM UTC

    We are continuing to monitor improvement in an incident with accessing PagerDuty Web UI. Event ingestion and incident notification delivery are not affected. We will provide an update within the next 60 minutes.

  5. resolved Jul 24, 2026, 01:23 PM UTC

    We have resolved an incident where A small number of PagerDuty customers in The US Service Region are experienced issues accessing the PagerDuty Web UI. Event ingestion and incident notification delivery were not affected. The incident is now resolved, and there is no ongoing impact to customers....

Read the full incident report →

Minor July 21, 2026

Resolved: SMS and Voice Notification Delivery Issues on Reliance Jio Carrier Network in India

Detected by Pingoru
Jul 21, 2026, 11:15 PM UTC
Resolved
Jul 29, 2026, 05:51 PM UTC
Duration
7d 18h
Affected: SMS (US) (SMS (US))SMS (EU) (SMS (EU))Voice (US) (Voice (US))Voice (EU) (Voice (EU))
Timeline · 3 updates
  1. investigating Jul 21, 2026, 11:15 PM UTC

    We are aware of delivery failures affecting some SMS and voice notifications for users on the Reliance Jio carrier network in India . This is a carrier-level infrastructure issue outside of our control, and our platform services remain fully operational. Immediate Action...

  2. investigating Jul 23, 2026, 07:05 PM UTC

    We are observing improved deliverability of SMS and voice notifications for users on the Reliance Jio carrier network in India . This is a carrier-level infrastructure issue outside of our control, and PagerDuty platform services remain fully operational. We are awaiting...

  3. resolved Jul 29, 2026, 05:51 PM UTC

    The issue with SMS and voice notification delivery failures on the Reliance Jio carrier network in India has been resolved and there is no ongoing impact to customers. This incident was not caused by a PagerDuty system failure. The disruption originated with Reliance Jio, impacting SMS and...

Read the full incident report →

Minor July 15, 2026

Issue Identified with Saving Incident Workflows

Detected by Pingoru
Jul 15, 2026, 11:39 AM UTC
Resolved
Jul 15, 2026, 01:44 PM UTC
Duration
2h 5m
Affected: Workflow Automation (Workflow Automation)
Timeline · 7 updates
  1. identified Jul 15, 2026, 11:39 AM UTC

    We are investigating an incident where all PagerDuty customers in all Service Regions are experiencing issues with Incident Type triggers not saving when being added to an Incident Workflow. Impacted customers may not be able to save new Incident Workflow triggers at this time. Event ingestion...

  2. investigating Jul 15, 2026, 11:56 AM UTC

    We are continuing to investigate an incident where PagerDuty customers in all Service Regions are experiencing issues with Incident Type triggers not saving when being added to an Incident Workflow. Impacted customers may not be able to save new Incident Workflow triggers at this time. Event...

  3. investigating Jul 15, 2026, 12:17 PM UTC

    We are continuing to investigate an incident where PagerDuty customers in all Service Regions are experiencing issues with Incident Type triggers not saving when being added to an Incident Workflow. Impacted customers may not be able to save new Incident Workflow triggers at this time....

  4. investigating Jul 15, 2026, 12:35 PM UTC

    We are continuing to investigate an incident where PagerDuty customers in all Service Regions are experiencing issues with Incident Type triggers not displaying correctly when added to an Incident Workflow. Impacted customers may not be able to see newly saved Incident...

  5. investigating Jul 15, 2026, 12:53 PM UTC

    We are monitoring improvement in an incident where PagerDuty customers in all Service Regions are experiencing issues with Incident Type triggers not displaying correctly when added to an Incident Workflow. Impacted customers may not be able to see newly saved Incident Workflow trigger...

  6. investigating Jul 15, 2026, 01:08 PM UTC

    We are monitoring improvement in an incident where PagerDuty customers in all Service Regions are experiencing issues with Incident Type triggers not displaying correctly when added to an Incident Workflow. Impacted customers may not be able to see newly saved Incident Workflow trigger...

  7. resolved Jul 15, 2026, 01:44 PM UTC

    We have resolved an incident where all PagerDuty customers in all Service Regions experienced issues with Incident Type triggers not displaying correctly when added to an Incident Workflow. Impacted customers were not able to see newly saved Incident Workflow trigger updates within the UI -...

Read the full incident report →

Minor July 8, 2026

Voice Notification contents Issue Identified

Detected by Pingoru
Jul 08, 2026, 06:42 AM UTC
Resolved
Jul 08, 2026, 08:18 AM UTC
Duration
1h 36m
Affected: Voice (US) (Voice (US))Voice (EU) (Voice (EU))
Timeline · 5 updates
  1. investigating Jul 08, 2026, 06:42 AM UTC

    We are investigating an incident where PagerDuty customers in all Service Regions are experiencing issues with the contents of Incident Voice Notifications. Impacted customers may see voice notifications for incidents have an incomplete title when announcing the incident. Event ingestion and...

  2. investigating Jul 08, 2026, 07:11 AM UTC

    We are continuing to investigate an incident where PagerDuty customers in all Service Regions are experiencing issues with the contents of Incident Voice Notifications. Impacted customers may see voice notifications for incidents have an incomplete title when announcing the incident. PagerDuty's...

  3. investigating Jul 08, 2026, 07:30 AM UTC

    We are continuing to investigate an incident where PagerDuty customers in all Service Regions are experiencing issues with the contents of Incident Voice Notifications. Impacted customers may see voice notifications for incidents have an incomplete title when announcing the incident. PagerDuty's...

  4. investigating Jul 08, 2026, 07:53 AM UTC

    We are continuing to investigate an incident where PagerDuty customers in all Service Regions are experiencing issues with the contents of Incident Voice Notifications. Impacted customers may see voice notifications for incidents have an incomplete title when announcing the incident. PagerDuty's...

  5. resolved Jul 08, 2026, 08:18 AM UTC

    We have resolved an incident where PagerDuty customers in all service regions experienced issues with Incident Voice Notifications. PagerDuty's core platform; event ingestion pipeline; mobile, SMS and voice notifications; notification delivery, and web application remained fully operational. The...

Read the full incident report →

Minor June 24, 2026

PagerDuty Advance Experiencing Delays and Timeouts

Detected by Pingoru
Jun 24, 2026, 09:09 PM UTC
Resolved
Jun 24, 2026, 09:41 PM UTC
Duration
31m
Affected: PagerDuty Advance (PagerDuty Advance)
Timeline · 3 updates
  1. investigating Jun 24, 2026, 09:09 PM UTC

    We are investigating an incident where all PagerDuty customers in the US service region are experiencing issues with PagerDuty Advance requests. Impacted customers may experience delays and timeouts while using PagerDuty Advance. Event ingestion and incident notification delivery are not affected....

  2. investigating Jun 24, 2026, 09:29 PM UTC

    We are continuing to investigate an incident where all PagerDuty customers in the US service region are experiencing latency issues with PagerDuty Advance. Event ingestion and incident notification delivery are not affected. We will provide further updates within 20 minutes.

  3. resolved Jun 24, 2026, 09:41 PM UTC

    We have resolved an incident where all PagerDuty customers in the US service region experienced latency issues with PagerDuty Advance. Event ingestion and incident notification delivery were not affected. The incident is now resolved, and there is no ongoing impact to customers. Please reach out...

Read the full incident report →

Minor June 24, 2026

Unable to update or delete shift-based schedules

Detected by Pingoru
Jun 24, 2026, 07:07 PM UTC
Resolved
Jun 24, 2026, 07:23 PM UTC
Duration
15m
Affected: Schedules and Escalation Policies (US) (Schedules and Escalation Policies (US))Schedules and Escalation Policies (EU) (Schedules and Escalation Policies (EU))
Timeline · 2 updates
  1. investigating Jun 24, 2026, 07:07 PM UTC

    We are investigating an incident where all PagerDuty customers in both the US and EU service regions are experiencing issues with shift-based schedules. Impacted customers may see that they are unable to update or delete their shift-based schedules. Event ingestion and incident notification...

  2. resolved Jun 24, 2026, 07:23 PM UTC

    We have resolved an incident where all PagerDuty customers in both the US and EU service regions experienced issues with updating or deleteing shift-based schedules. Event ingestion and incident notification delivery were not affected. The incident is now resolved, and there is no ongoing impact...

Read the full incident report →

Minor June 10, 2026

Delays to Escalations and Responder notifications

Detected by Pingoru
Jun 10, 2026, 12:47 AM UTC
Resolved
Jun 10, 2026, 01:33 AM UTC
Duration
45m
Affected: Responder Requests (US) (Responder Requests (US))Schedules and Escalation Policies (US) (Schedules and Escalation Policies (US))
Timeline · 3 updates
  1. investigating Jun 10, 2026, 12:47 AM UTC

    We are investigating an incident where PagerDuty customers in the US Service Region are experiencing issues with delays in timed escalations. Impacted customers may see a delay in an incident automatically moving to the next level on an Escalation Policy. Additionally, add responder and status...

  2. investigating Jun 10, 2026, 01:12 AM UTC

    We are monitoring improvements in an incident with delays in timed escalations, add responder notifications, and status update notifications for PagerDuty customers in the US Service Region. We have deployed a fix, and we expect systems to continue to improve. We will provide further updates...

  3. resolved Jun 10, 2026, 01:33 AM UTC

    We have resolved an incident where PagerDuty customers in the US service region experienced issues with delays in timed escalations, add responder notifications, and status update notifications. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to...

Read the full incident report →

Minor June 3, 2026

Issue Identified calling the Schedules API

Detected by Pingoru
Jun 03, 2026, 01:48 PM UTC
Resolved
Jun 03, 2026, 02:18 PM UTC
Duration
30m
Affected: REST API (US) (REST API (US))REST API (EU) (REST API (EU))
Timeline · 3 updates
  1. investigating Jun 03, 2026, 01:48 PM UTC

    We are investigating an incident where some PagerDuty customers in the EU Service Region are experiencing issues with the schedules API. Impacted customers may see 401 unauthorised errors when querying the schedules API. Event ingestion and incident notification delivery are not affected. We will...

  2. investigating Jun 03, 2026, 02:14 PM UTC

    We are monitoring improvement in an incident with the Schedules API. We have deployed a fix, and we expect systems to continue to improve; Mobile and Web UIs were not impacted. Event ingestion and incident notification delivery are not affected. We will provide an update within the next 15...

  3. resolved Jun 03, 2026, 02:18 PM UTC

    We have resolved an incident with the Schedules API. We have deployed a fix, and we expect systems to continue to improve; Mobile and Web UIs were not impacted. Event ingestion and incident notification delivery were not affected. The incident is now resolved, and there is no ongoing impact to...

Read the full incident report →

Minor May 28, 2026

Issue Identified - Slack Outage

Detected by Pingoru
May 28, 2026, 12:31 AM UTC
Resolved
May 28, 2026, 10:27 AM UTC
Duration
9h 56m
Affected: Slack (US) (Slack (US))Slack (EU) (Slack (EU))
Timeline · 7 updates
  1. investigating May 28, 2026, 12:31 AM UTC

    We are investigating an incident where PagerDuty customers in all Service Regions are experiencing issues with Slack functionality, due to an ongoing Incident at Slack. The PagerDuty web application continues to be available. Impacted customers may see issues with Slack workflows /...

  2. investigating May 28, 2026, 12:50 AM UTC

    We are continuing to monitor an incident where PagerDuty customers in all Service Regions are experiencing issues with Slack functionality, due to an ongoing Incident at Slack. The PagerDuty web application continues to be available. Impacted customers may see issues with Slack...

  3. investigating May 28, 2026, 01:57 AM UTC

    We are continuing to monitor an incident where PagerDuty customers in all Service Regions are experiencing issues with Slack functionality, due to an ongoing Incident at Slack. We are seeing improvements in Slack notification delivery, and will continue to monitor for further issues. The...

  4. investigating May 28, 2026, 03:12 AM UTC

    We are continuing to monitor an incident where PagerDuty customers in all Service Regions are experiencing issues with Slack functionality, due to an ongoing Incident at Slack. Issues with Slack notification delivery and Slack Incident card updates should now be resolved. The PagerDuty...

  5. investigating May 28, 2026, 04:11 AM UTC

    We are continuing to monitor an incident where PagerDuty customers in all Service Regions are experiencing issues with Slack functionality, due to an ongoing Incident at Slack. Issues with Slack notification delivery and Slack Incident card updates should now be resolved. The PagerDuty...

  6. investigating May 28, 2026, 05:18 AM UTC

    We are continuing to monitor an incident where PagerDuty customers in all Service Regions are experiencing issues with Slack functionality, due to an ongoing Incident at Slack. Issues with Slack notification delivery and Slack Incident card updates should now be resolved. The PagerDuty web...

  7. resolved May 28, 2026, 10:27 AM UTC

    We have resolved an incident where PagerDuty customers in all Service Regions experienced issues with Slack functionality, due to an Incident at Slack. Event ingestion and incident notification delivery were not affected. The incident is now resolved, and there is no ongoing impact to customers....

Read the full incident report →

Minor May 13, 2026

Resolved: Issues with EU Service Region

Detected by Pingoru
May 13, 2026, 11:56 PM UTC
Resolved
May 14, 2026, 12:56 AM UTC
Duration
1h
Affected: Events API (EU) (Events API (EU))Incident Timeline and Alert Logs (EU) (Incident Timeline and Alert Logs (EU))Incident Timeline and Alert Logs (US) (Incident Timeline and Alert Logs (US))Services (EU) (Services (EU))SMS (EU) (SMS (EU))Voice (EU) (Voice (EU))Push (EU) (Push (EU))Email (EU) (Email (EU))Responder Requests (EU) (Responder Requests (EU))Internal Status Page (EU) (Internal Status Page (EU))Webhooks (EU) (Webhooks (EU))Business Services and Status Dashboard (EU) (Business Services and Status Dashboard (EU))Web Application (EU) (Web Application (EU))
Timeline · 5 updates
  1. identified May 13, 2026, 11:56 PM UTC

    We are investigating an issue affecting event processing in PagerDuty for the EU Service Region. We will provide details and recommended actions within 15 minutes.

  2. investigating May 14, 2026, 12:06 AM UTC

    We are investigating an incident where PagerDuty customers in The EU Service Region are experiencing issues with accessing the Website, REST API and Events API. Impacted customers may see errors when trying to access the website and other PagerDuty functionality in the EU service region. Event...

  3. investigating May 14, 2026, 12:22 AM UTC

    We are continuing to investigate an incident where PagerDuty customers in the EU Service Region are experiencing issues with PagerDuty. Event ingestion and incident notification delivery are affected in the EU service region only. We will provide further updates within 20 minutes.

  4. investigating May 14, 2026, 12:39 AM UTC

    We are monitoring improvement in an incident with PagerDuty in the EU service region. We have deployed a fix, and we expect systems to continue to improve. We will provide an update within the next 15 minutes.

  5. resolved May 14, 2026, 12:56 AM UTC

    We have resolved an incident where PagerDuty customers in the EU service region experienced issues with web access, REST API, and event proccessing . Event ingestion and incident notification delivery were affected for the EU service region and customers may now experience some triggered...

Read the full incident report →

Minor May 12, 2026

AIOps and Event Intelligence feature issues

Detected by Pingoru
May 12, 2026, 02:02 PM UTC
Resolved
May 12, 2026, 03:20 PM UTC
Duration
1h 18m
Timeline · 6 updates
  1. investigating May 12, 2026, 02:01 PM UTC

    We are investigating an incident where AIOps and Event Intelligence PagerDuty customers in the US Service Region may be experiencing issues with incident correlation. Affected customers may not see intelligent change correlation, probable origin or suggested service dependencies being populated....

  2. investigating May 12, 2026, 02:02 PM UTC

    We are investigating an incident where AIOps and Event Intelligence PagerDuty customers in the US Service Region may be experiencing issues with incident correlation. Affected customers may not see intelligent change correlation or probable origins being populated on the incident details page....

  3. investigating May 12, 2026, 02:22 PM UTC

    We are continuing to investige an incident where AIOps and Event Intelligence PagerDuty customers in the US Service Region may be experiencing issues with incident correlation. Impacted customers may not see intelligent change correlation, probable origin or suggested service dependencies being...

  4. investigating May 12, 2026, 02:41 PM UTC

    We have identified, and are remediating, the cause of an incident where AIOps and Event Intelligence PagerDuty customers in the US Service Region may be experiencing issues with incident correlation. Impacted customers may not see intelligent change correlation, probable origin or suggested...

  5. investigating May 12, 2026, 03:03 PM UTC

    We have identified, and are continuing to remediate, the cause of an incident where AIOps and Event Intelligence PagerDuty customers in the US Service Region may be experiencing issues with incident correlation. Impacted customers may not see intelligent change correlation, probable origin or...

  6. resolved May 12, 2026, 03:20 PM UTC

    We have identified and resolved an incident where AIOps and Event Intelligence PagerDuty customers in the US Service Region experienced issues with intelligent change correlation and probable origins between 14:42 UTC and 16:15 UTC. The incident is now resolved, and there is no ongoing impact to...

Read the full incident report →

Minor April 22, 2026

Issue Identified with Jeli

Detected by Pingoru
Apr 22, 2026, 12:55 AM UTC
Resolved
Apr 22, 2026, 01:20 AM UTC
Duration
24m
Affected: Jeli (Jeli)
Timeline · 2 updates
  1. investigating Apr 22, 2026, 12:55 AM UTC

    We are investigating an incident where Jeli customers in the US Service Region are experiencing issues with accessing Jeli opportunities. PagerDuty Event ingestion and incident notification delivery are not affected. We will provide further updates within 20 minutes.

  2. resolved Apr 22, 2026, 01:20 AM UTC

    We have resolved an incident where Jeli customers in the US service region experienced issues with acessing Jeli Opportunities. PagerDuty Event ingestion and incident notification delivery were not affected. The incident is now resolved, and there is no ongoing impact to customers. Please reach...

Read the full incident report →

Minor April 19, 2026

Event Processing - No customer impact identified

Detected by Pingoru
Apr 19, 2026, 09:51 AM UTC
Resolved
Apr 19, 2026, 10:54 AM UTC
Duration
1h 3m
Affected: Events API (US) (Events API (US))Events API (EU) (Events API (EU))
Timeline · 3 updates
  1. identified Apr 19, 2026, 09:51 AM UTC

    We are investigating an issue affecting event processing in PagerDuty. We will provide details and recommended actions within 15 minutes.

  2. investigating Apr 19, 2026, 10:32 AM UTC

    We have identified an incident where some PagerDuty customers in both the US and EU service regions experienced issues with event processing between 9:01 UTC and 9:50 UTC. We are monitoring improvement with event processing and there is no ongoing impact to customers. We will provide an update...

  3. resolved Apr 19, 2026, 10:54 AM UTC

    An incident where we initially believed a small number of PagerDuty customers in both the US and EU Service Regions may have experienced issues with event processing turned out to be a false alarm. We have determined there was no customer impact, Event ingestion and incident notification...

Read the full incident report →