PagerDuty Outage History

PagerDuty is up right now

PagerDuty had 33 outages in the last 2 years totaling 57h 42m of downtime — averaging 1.4 incidents per month.

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

Source: https://status.pagerduty.com

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 29, 2026

PagerDuty Advance Experiencing Delays and Timeouts

Detected by Pingoru
May 29, 2026, 12:23 PM UTC
Resolved
May 29, 2026, 01:49 PM UTC
Duration
1h 25m
Affected: PagerDuty Advance (PagerDuty Advance)
Timeline · 4 updates
  1. investigating May 29, 2026, 12:23 PM UTC

    We are investigating an incident where all of 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...

  2. investigating May 29, 2026, 12:44 PM UTC

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

  3. investigating May 29, 2026, 01:07 PM UTC

    We are actively monitoring improvement in an incident with PagerDuty Advance and we expect systems to continue to improve. Event ingestion and incident notification delivery are not affected. We will provide an update within the next 30 minutes.

  4. resolved May 29, 2026, 01:49 PM UTC

    We have resolved an incident where all PagerDuty customers in both the US and EU service regions experienced 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...

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 →

Minor March 26, 2026

Delayed Event Processing

Detected by Pingoru
Mar 26, 2026, 10:49 PM UTC
Resolved
Mar 26, 2026, 11:16 PM UTC
Duration
26m
Affected: Events API (US) (Events API (US))
Timeline · 4 updates
  1. identified Mar 26, 2026, 10:49 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Mar 26, 2026, 10:57 PM UTC

    We are investigating an incident where some PagerDuty customers in the US Service Region are experiencing issues with delayed event processing. Event ingestion and incident notification delivery are affected. We will provide further updates within 20 minutes.

  3. investigating Mar 26, 2026, 11:06 PM UTC

    We have taken corrective action and are seeing signs of improvement for an issue that caused delayed event processing. We have deployed a fix, and we expect systems to continue to improve. Event ingestion and incident notification delivery are affected for the subset of customers that were...

  4. resolved Mar 26, 2026, 11:16 PM UTC

    We have resolved an incident where some PagerDuty customers in the US Service Region experienced issues with delayed event processing. All delayed events and notifications have been successfully processed for the subset of customers that were impacted. The incident is now resolved, and there is...

Read the full incident report →

Minor March 24, 2026

Latency Issues in Web and Mobile Applications

Detected by Pingoru
Mar 24, 2026, 10:31 PM UTC
Resolved
Mar 24, 2026, 11:34 PM UTC
Duration
1h 2m
Affected: Mobile Application (US) (Mobile Application (US))Web Application (US) (Web Application (US))
Timeline · 4 updates
  1. identified Mar 24, 2026, 10:31 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Mar 24, 2026, 10:47 PM UTC

    We are investigating an incident where some PagerDuty customers in the US Service Region are experiencing latency issues in both web and mobile applications. Event ingestion and incident notification delivery are not affected. We will provide further updates within 20 minutes.

  3. investigating Mar 24, 2026, 11:08 PM UTC

    We are continuing to investigate an incident where where some PagerDuty customers in the US Service Region are experiencing latency issues in both web and mobile applications. Event ingestion and incident notification delivery are not affected. We will provide further updates within 20 minutes.</...

  4. resolved Mar 24, 2026, 11:34 PM UTC

    We have resolved an incident where some PagerDuty customers in the US Service Region were experiencing latency issues in both web and mobile applications. Event ingestion and incident notification delivery were not affected.

Read the full incident report →

Minor March 24, 2026

Scribe Agent Unable to Join Calls

Detected by Pingoru
Mar 24, 2026, 06:03 PM UTC
Resolved
Mar 24, 2026, 06:52 PM UTC
Duration
48m
Affected: PagerDuty Advance (PagerDuty Advance)
Timeline · 3 updates
  1. identified Mar 24, 2026, 06:03 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Mar 24, 2026, 06:07 PM UTC

    We are monitoring an incident where all PagerDuty customers in all Service Regions are experiencing issues with Scribe Agent unable to join any calls. Impacted customers may see an error that Scribe Agent could not join the call. Event ingestion and incident notification delivery are not affected....

  3. resolved Mar 24, 2026, 06:52 PM UTC

    An incident where all PagerDuty customers in all Service Regions were experiencing issues with Scribe Agent unable to join any calls has been resolved. Impacted customers may have seen an error that Scribe Agent could not join the call. Event ingestion and incident notification delivery were not...

Read the full incident report →

Minor March 24, 2026

Issue with Webhook Delivery to Microsoft Teams

Detected by Pingoru
Mar 24, 2026, 05:27 PM UTC
Resolved
Mar 24, 2026, 07:35 PM UTC
Duration
2h 7m
Affected: Microsoft Teams (US) (Microsoft Teams (US))Microsoft Teams (EU) (Microsoft Teams (EU))
Timeline · 5 updates
  1. identified Mar 24, 2026, 05:27 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Mar 24, 2026, 05:42 PM UTC

    We are investigating an incident where PagerDuty customers in the US and EU Service Regions are experiencing issues with incident update notifications in Microsoft Teams. EIncident notification delivery is only affected for users using Microsoft Teams users. Microsoft Team users can still receive...

  3. investigating Mar 24, 2026, 05:57 PM UTC

    We are continuing to monitor an incident where PagerDuty customers in all Service Regions are experiencing issues with incident update notifications in Microsoft Teams. Incident notification delivery is only affected for users using Microsoft Teams. Microsoft Team users can still receive mobile...

  4. investigating Mar 24, 2026, 06:54 PM UTC

    We are continuing to monitor an incident where PagerDuty customers in all Service Regions are experiencing issues with webhook delivery to the Microsoft Teams integration. Incident notification delivery is only affected for Microsoft Teams users. Microsoft Team users can still receive mobile and...

  5. resolved Mar 24, 2026, 07:35 PM UTC

    An incident where PagerDuty customers in all Service Regions were experiencing issues with webhook delivery to the Microsoft Teams integration has been resolved. Incident notification delivery was only affected for Microsoft Teams users. Microsoft Team users could still receive mobile and web...

Read the full incident report →

Minor March 21, 2026

Investigating Potential Issue with Phone Notifications

Detected by Pingoru
Mar 21, 2026, 06:25 PM UTC
Resolved
Mar 21, 2026, 06:59 PM UTC
Duration
34m
Timeline · 4 updates
  1. identified Mar 21, 2026, 06:25 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Mar 21, 2026, 06:38 PM UTC

    We are investigating an issue within PagerDuty impacting call/voice notifications in the US Service region. All core PagerDuty functionality, including API-based event ingestion, event orchestration, incident creation, email notifications and Push/SMS notifications, remain fully operational. We...

  3. investigating Mar 21, 2026, 06:52 PM UTC

    We are continuing to investigate an issue within PagerDuty impacting call/voice notifications in the US Service region; this issue impacts a small number of PagerDuty customers. All core PagerDuty functionality, including API-based event ingestion, event orchestration, incident creation, email...

  4. resolved Mar 21, 2026, 06:59 PM UTC

    We have resolved an issue within PagerDuty impacting call/voice notifications in the US Service region; this issue impacted a small number of PagerDuty customers. All core PagerDuty functionality, including API-based event ingestion, event orchestration, incident creation, email notifications and...

Read the full incident report →

Minor February 27, 2026

Issues with schedule change notifications

Detected by Pingoru
Feb 27, 2026, 09:19 AM UTC
Resolved
Feb 27, 2026, 10:36 AM UTC
Duration
1h 17m
Timeline · 4 updates
  1. identified Feb 27, 2026, 09:19 AM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Feb 27, 2026, 09:49 AM UTC

    We are investigating an incident where some PagerDuty customers across all service regions are experiencing issues receiving notifications about schedule changes. Impacted customers may not receive notifications when they are mentioned in a schedule change. We will provide further updates within...

  3. investigating Feb 27, 2026, 10:08 AM UTC

    We are continuing to investigate an incident where some PagerDuty customers across all service regions are experiencing issues receiving notifications about schedule changes. Impacted customers may not receive notifications when they are mentioned in a schedule change. We will provide further...

  4. resolved Feb 27, 2026, 10:36 AM UTC

    We have identified and resolved an incident where some PagerDuty customers across all service regions experienced issues receiving notifications about schedule changes between 08:38am UTC and 10:25am UTC. Our events and notification pipelines were not impacted. The incident is now resolved, and...

Read the full incident report →

Minor February 15, 2026

Delay in Email Event Processing

Detected by Pingoru
Feb 15, 2026, 10:39 AM UTC
Resolved
Feb 15, 2026, 12:18 PM UTC
Duration
1h 38m
Affected: Email (US) (Email (US))Incoming Email (US) (Incoming Email (US))
Timeline · 8 updates
  1. identified Feb 15, 2026, 10:39 AM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Feb 15, 2026, 10:40 AM UTC

    We are investigating an incident where a small number of PagerDuty customers in the US Service Region are experiencing issues with a delay in email event processing for email integrations on Event Orchestration and Services. Impacted customers may see a delay or absence of email events triggering...

  3. investigating Feb 15, 2026, 10:59 AM UTC

    We are continuing to investigate an incident where a small number of PagerDuty customers in The US Service Region are experiencing issues with lagging processing of email events on Event Orchestrations and Services. Impacted customers may see a delay or absence of email events triggering...

  4. investigating Feb 15, 2026, 11:19 AM UTC

    We are investigating an incident where a small number of PagerDuty customers in the US Service Region are experiencing issues with a delay in email event processing for email integrations on Event Orchestration and Services. Impacted customers may see a delay or absence of email events triggering...

  5. investigating Feb 15, 2026, 11:39 AM UTC

    We are investigating an incident where a small number of PagerDuty customers in the US Service Region are experiencing issues with a delay in email event processing for email integrations on Event Orchestration and Services. Impacted customers may see a delay or absence of email events triggering...

  6. investigating Feb 15, 2026, 11:58 AM UTC

    We are investigating an incident where a small number of PagerDuty customers in the US Service Region are experiencing issues with a delay in email event processing for email integrations on Event Orchestration and Services. Impacted customers may see a delay or absence of email events triggering...

  7. investigating Feb 15, 2026, 12:17 PM UTC

    We are monitoring improvement in an incident with email event processing on Event Orchestrations and Services for a small number of customers in The US Service Region. We have deployed a fix, and we expect systems to continue to improve.

  8. resolved Feb 15, 2026, 12:18 PM UTC

    We have resolved an incident where a small number of PagerDuty customers in The US service region experienced issues with a delay in email event processing. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to ...

Read the full incident report →

Minor February 13, 2026

Inability to create or edit teams and delete users

Detected by Pingoru
Feb 13, 2026, 02:37 PM UTC
Resolved
Feb 13, 2026, 03:08 PM UTC
Duration
31m
Affected: Users and Teams (US) (Users and Teams (US))Users and Teams (EU) (Users and Teams (EU))
Timeline · 3 updates
  1. identified Feb 13, 2026, 02:37 PM UTC

    We are investigating a potential issue within PagerDuty where users may be unable to delete users, or edit teams across both the EU and US Service Regions. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed. Incident creation...

  2. investigating Feb 13, 2026, 02:55 PM UTC

    We are investigating an incident where some PagerDuty customers in both service regions are experiencing issues with creating/editing teams or deleting users. Impacted customers may see be unable to create or edit teams, or delete users through the PagerDuty Web UI. Our events and notifications...

  3. resolved Feb 13, 2026, 03:08 PM UTC

    We have resolved an incident where some PagerDuty customers in both the US and EU service regions experienced issues creating/editing teams and deleting users. Our events and notification pipelines were not impacted. The incident is now resolved, and there is no ongoing impact to customers....

Read the full incident report →

Minor January 28, 2026

Incident Workflow Delays

Detected by Pingoru
Jan 28, 2026, 06:53 PM UTC
Resolved
Jan 28, 2026, 08:14 PM UTC
Duration
1h 20m
Affected: Incident Workflows (US) (Incident Workflows (US))
Timeline · 6 updates
  1. identified Jan 28, 2026, 06:53 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Jan 28, 2026, 07:09 PM UTC

    We are investigating an incident where all PagerDuty customers in the US Service Region are experiencing issues with delays in Incident Workflows. Impacted customers may have begun experiencing delays about 90 minutes ago. We are monitoring improvement, and we expect systems to continue to...

  3. investigating Jan 28, 2026, 07:26 PM UTC

    We are continuing to monitor improvement in an incident with delays in Incident Workflows. We expect systems to continue to improve. We will provide an update within the next 15 minutes.

  4. investigating Jan 28, 2026, 07:42 PM UTC

    We are continuing to monitor remediation of an incident with delays in Incident Workflows. Known customer impact has been resolved. We will provide an update within the next 15 minutes.

  5. investigating Jan 28, 2026, 08:00 PM UTC

    We are continuing to monitor remediation of an incident with delays in Incident Workflows. Known customer impact has been resolved. We will provide an update within the next 15 minutes.

  6. resolved Jan 28, 2026, 08:14 PM UTC

    We have resolved an incident where all PagerDuty customers in the US service region experienced issues with delays in Incident Workflows. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to [email protected] if you have any concerns.

Read the full incident report →

Minor January 16, 2026

500 Errors accessing the application - Edited

Detected by Pingoru
Jan 16, 2026, 03:50 PM UTC
Resolved
Jan 16, 2026, 04:14 PM UTC
Duration
23m
Affected: Web Application (EU) (Web Application (EU))
Timeline · 2 updates
  1. investigating Jan 16, 2026, 03:50 PM UTC

    We're currently investigating an error in the EU Service Region, where some customers may experience 500 errors accessing PagerDuty.

  2. resolved Jan 16, 2026, 04:14 PM UTC

    We have resolved an incident where a small number of PagerDuty customers in the EU service region may have experienced 500 errors when accessing the PagerDuty web application. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to [email protected] if...

Read the full incident report →

Minor January 14, 2026

Voice and SMS Notification Delivery Issues via Certain U.S. Carrier Networks

Detected by Pingoru
Jan 14, 2026, 08:03 PM UTC
Resolved
Jan 15, 2026, 10:26 AM UTC
Duration
14h 23m
Affected: SMS (US) (SMS (US))Voice (US) (Voice (US))
Timeline · 5 updates
  1. identified Jan 14, 2026, 08:03 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Jan 14, 2026, 08:11 PM UTC

    We are currently observing a higher rate of voice and SMS notification delivery failures affecting users on certain mobile carrier networks within the United States . This disruption appears to be isolated to carrier systems and does not impact our...

  3. investigating Jan 14, 2026, 08:47 PM UTC

    Ongoing Monitoring: SMS and Voice Notification Delays on U.S. Carrier Networks We are aware of delivery delays affecting some SMS and voice notifications for users on certain mobile carrier networks in the United States. This is a carrier-level infrastructure issue outside of our control,...

  4. investigating Jan 15, 2026, 06:10 AM UTC

    Ongoing Monitoring: SMS and Voice Notification Delays on U.S. Carrier Networks We are seeing significant improvements, with reduced delivery delays that have been affecting some SMS and voice notifications for users on certain mobile carrier networks in the United States. This is...

  5. resolved Jan 15, 2026, 10:26 AM UTC

    The issue with SMS and Voice Notification Delays on U.S. Carrier Networks has been resolved and there is no ongoing impact to customers. Please reach out to [email protected] if you have any concerns.

Read the full incident report →

Minor January 14, 2026

Email integration issue

Detected by Pingoru
Jan 14, 2026, 12:11 AM UTC
Resolved
Jan 14, 2026, 06:10 AM UTC
Duration
5h 59m
Affected: Incoming Email (US) (Incoming Email (US))Incoming Email (EU) (Incoming Email (EU))
Timeline · 12 updates

Read the full incident report →

Major January 9, 2026

Slack notification issue

Detected by Pingoru
Jan 09, 2026, 08:59 AM UTC
Resolved
Jan 09, 2026, 10:39 AM UTC
Duration
1h 39m
Affected: Slack (US) (Slack (US))
Timeline · 5 updates
  1. investigating Jan 09, 2026, 08:59 AM UTC

    We are investigating an incident where some PagerDuty customers in the US service region are experiencing a delay with notifications posting to Slack. We will provide further updates within 15 minutes.

  2. investigating Jan 09, 2026, 09:14 AM UTC

    We are continuing to investigate an incident where some PagerDuty customers in the US service region are experiencing a delay with notifications posting to Slack. We will provide further updates within 30 minutes.

  3. investigating Jan 09, 2026, 09:42 AM UTC

    We are continuing to investigate an incident where some PagerDuty customers in the US service region are experiencing a delay with notifications posting to Slack. We will provide further updates within 30 minutes.

  4. investigating Jan 09, 2026, 10:13 AM UTC

    We are continuing to investigate an incident where some PagerDuty customers in the US service region are experiencing a delay with notifications posting to Slack. We will provide further updates within 30 minutes.

  5. resolved Jan 09, 2026, 10:39 AM UTC

    We have resolved an incident where some PagerDuty customers in the US service region had been experiencing a delay with notifications posting to Slack. The incident is now resolved, and there is no ongoing impact to customers. Please reach out to <a href="mailto:support@pagerduty....

Read the full incident report →

Minor December 15, 2025

Errors in Mobile Application

Detected by Pingoru
Dec 15, 2025, 09:18 PM UTC
Resolved
Dec 15, 2025, 10:25 PM UTC
Duration
1h 7m
Affected: Mobile Application (US) (Mobile Application (US))Mobile Application (EU) (Mobile Application (EU))
Timeline · 5 updates
  1. identified Dec 15, 2025, 09:18 PM UTC

    We are investigating a potential issue within PagerDuty. If we confirm an impact, we will update within 15 minutes. If there is no impact this notification will be removed.

  2. investigating Dec 15, 2025, 09:37 PM UTC

    We are investigating an incident where some PagerDuty customers in the US and EU Service Regions are experiencing issues with the mobile application. Impacted customers may see error messages in the mobile application. Notifications are not affected. We will provide further updates within 20...

  3. investigating Dec 15, 2025, 09:56 PM UTC

    We are continuing to investigate an incident where some PagerDuty customers in the US and EU Service Regions are experiencing issues with the mobile application. Impacted customers may see error messages in the mobile application. Notifications are not affected. We will provide further updates...

  4. investigating Dec 15, 2025, 10:21 PM UTC

    We are monitoring an improvement in an incident where some PagerDuty customers in the US and EU Service Regions are experiencing issues with the mobile application. Impacted customers may see error messages in the mobile application. Notifications are not affected. We will provide further updates...

  5. resolved Dec 15, 2025, 10:25 PM UTC

    We have resolved an incident where some PagerDuty customers in the US and EU Service Regions experienced issues with the mobile application. Impacted customers may have seen error messages in the mobile application. Notifications were not affected. The incident is now resolved, and there is no...

Read the full incident report →

Minor December 15, 2025

Delays in Incident Workflow Actions that use JavaScript steps

Detected by Pingoru
Dec 15, 2025, 06:34 PM UTC
Resolved
Dec 15, 2025, 08:16 PM UTC
Duration
1h 42m
Affected: Incident Workflows (US) (Incident Workflows (US))
Timeline · 7 updates
  1. investigating Dec 15, 2025, 06:34 PM UTC

    We are investigating an incident where some PagerDuty customers in the US region are experiencing issues with delays to Incident Workflow Actions that use JavaScript steps. All other incident response functionality and notifications remain unaffected. We will provide further updates within 20...

  2. investigating Dec 15, 2025, 06:55 PM UTC

    We are continuing to investigate an incident where some PagerDuty customers in the US are experiencing issues with delays to Incident Workflow Actions that use JavaScript steps. All other incident response functionality and notifications remain unaffected. We will provide further updates within...

  3. investigating Dec 15, 2025, 07:14 PM UTC

    We are continuing to investigate an incident where some PagerDuty customers in the US are experiencing issues with delays to Incident Workflow Actions that use JavaScript steps. All other incident response functionality and notifications remain unaffected. We will provide further updates within...

  4. investigating Dec 15, 2025, 07:35 PM UTC

    We are continuing to investigate an incident where some PagerDuty customers in the US are experiencing issues with delays to Incident Workflow Actions that use JavaScript steps. All other incident response functionality and notifications remain unaffected. We will provide further updates within...

  5. investigating Dec 15, 2025, 07:54 PM UTC

    We are continuing to investigate an incident where some PagerDuty customers in the US are experiencing issues with delays to Incident Workflow Actions that use JavaScript steps. All other incident response functionality and notifications remain unaffected. We will provide further updates within...

  6. investigating Dec 15, 2025, 08:13 PM UTC

    We have applied a fix and are seeing recovery in an incident where some PagerDuty customers in the US are experiencing issues with delays to Incident Workflow Actions that use JavaScript steps. All other incident response functionality and notifications remain unaffected. We will provide further...

  7. resolved Dec 15, 2025, 08:16 PM UTC

    We have resolved an incident where some PagerDuty customers in the US service region experienced issues with delays to Incident Workflow Actions that use JavaScript steps. All other incident response functionality and notifications were unaffected. The incident is now resolved, and there is no...

Read the full incident report →