This summary is created by Generative AI and may differ from the actual content.
Overview
On August 7, 2025, between 14:07 and 16:28 UTC, PagerDuty experienced a service degradation where customers in US and EU service regions were unable to access service integration configuration pages, which returned "Page Not Found" errors. This was caused by a deployed change introducing a broad redirect rule that unintentionally impacted the URL patterns for these pages. Core incident response functionality remained unaffected. The issue was detected via a customer report and resolved by reverting the problematic code change. Some users experienced brief residual issues due to browser caching of previous redirect responses.Impact
Customers in US and EU service regions were unable to access service integration configuration pages, encountering "Page Not Found" errors, for approximately 2 hours and 21 minutes. Core PagerDuty functionality, including incident response capabilities, remained fully operational.Trigger
A change deployed on August 7, 2025, at 14:07 UTC, introduced a broad redirect rule to a service.Detection
At approximately 16:01 UTC, a customer reported encountering errors when trying to access a service integration page. The support team reproduced the issue and notified engineers.Resolution
Within nine minutes of notification, engineers identified the problematic code change as the root cause and immediately began reverting it. By 16:28 UTC, the revert was completed, restoring access to integration configuration pages across both US and EU service regions. Some users experienced brief residual issues due to browser caching of the previous redirect responses.Root Cause
A recently deployed code change introduced a broad redirect rule that unintentionally impacted the URL patterns for service integration configuration pages, causing them to return "Page Not Found" errors.
