PagerDuty Outage History

PagerDuty is up right now

There were 11 PagerDuty outages since February 13, 2026 totaling 12h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.pagerduty.com

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

Intermittent REST API Errors and Response Delays

Detected by Pingoru
Feb 17, 2026, 07:30 PM UTC
Resolved
Feb 17, 2026, 10:31 PM UTC
Duration
3h
Affected: REST API (US) (REST API (US))
Timeline · 11 updates
  1. identified Feb 17, 2026, 07:30 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 Feb 17, 2026, 07:44 PM UTC

    We are investigating an incident where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide further updates within 20 minutes....

  3. investigating Feb 17, 2026, 08:03 PM UTC

    We are investigating an incident where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide further updates within 20 minutes....

  4. investigating Feb 17, 2026, 08:21 PM UTC

    We are continuing to investigate an incident where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide further updates within...

  5. investigating Feb 17, 2026, 08:32 PM UTC

    We have identified and are working on remediation steps for an issue where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide...

  6. investigating Feb 17, 2026, 08:50 PM UTC

    We are continuing to work on remediation steps for an issue where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide further...

  7. investigating Feb 17, 2026, 09:09 PM UTC

    We are continuing to work on remediation steps for an issue where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide further...

  8. investigating Feb 17, 2026, 09:30 PM UTC

    We are continuing to work on remediation steps for an issue where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide further...

  9. investigating Feb 17, 2026, 09:50 PM UTC

    We are continuing to work on remediation steps for an issue where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide further...

  10. investigating Feb 17, 2026, 10:11 PM UTC

    We are continuing to work on remediation steps for an issue where a very small subset of PagerDuty customers in the US Service Region might experience issues with REST API requests. Impacted customers may experience latency issues and API requests failing with 500 errors. We will provide further...

  11. resolved Feb 17, 2026, 10:31 PM UTC

    We have resolved an incident where a very small subset of PagerDuty customers in the US Service Region may have experienced errors and latency issues with REST API 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 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 →

Looking to track PagerDuty downtime and outages?

Pingoru polls PagerDuty's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when PagerDuty reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track PagerDuty alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring PagerDuty for free

5 free monitors · No credit card required