PagerDuty experienced a minor incident on May 12, 2026, lasting 1h 18m. The incident has been resolved; the full update timeline is below.
Update timeline
- 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....
- 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....
- 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...
- 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...
- 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...
- 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...