PagerDuty Outage History

PagerDuty experienced delayed event processing that affected the Events API in the US region for 28 minutes. The issue impacted event ingestion and incident notification delivery for a subset of customers. The service was restored after deploying a fix and taking corrective action.

PagerDuty experienced latency issues affecting their web and mobile applications for customers in the US Service Region over a 1-hour period. The incident was classified as minor, with event ingestion and incident notification delivery remaining unaffected. The company continued investigating the latency problems while providing regular updates to customers.

PagerDuty experienced an incident where the Scribe Agent was unable to join calls across all service regions, affecting all customers using PagerDuty Advance. Users encountered errors when the Scribe Agent attempted to join calls, though event ingestion and incident notifications continued to function normally. The issue was resolved after 49 minutes.

PagerDuty experienced a webhook delivery issue affecting Microsoft Teams integrations across all service regions for 2.2 hours. The incident prevented Teams users from receiving incident notifications through the integration, though mobile and other notification methods remained functional. The issue was classified as minor and has been resolved with continued monitoring.

PagerDuty experienced an issue affecting phone/voice notifications for a small number of customers in the US Service region for 32 minutes. All other core functionality including API event ingestion, event orchestration, incident creation, and email notifications remained operational. The issue was investigated and resolved as a minor service disruption.

PagerDuty investigated a potential service issue affecting their Slack integration in the US region. The investigation lasted 24 minutes and was classified as a minor incident. The issue was resolved without confirmed impact to users.

PagerDuty experienced issues with schedule change notifications across all service regions, where some customers did not receive notifications when mentioned in schedule changes. The incident was classified as minor and lasted approximately 1.3 hours before being resolved.