PagerDuty incident

Event Processing - No customer impact identified

Minor Resolved View vendor source →
Started
Apr 19, 2026, 09:51 AM UTC
Resolved
Apr 19, 2026, 10:54 AM UTC
Duration
1h 3m
Detected by Pingoru
Apr 19, 2026, 09:51 AM UTC

Affected components

Events API (US) (Events API (US))Events API (EU) (Events API (EU))

Update timeline

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

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