404 Error returned in the Web UI for Integration management pages.
This summary is created by Generative AI and may differ from the actual content.
Overview
On August 13, 2026, between 21:26 UTC and 23:12 UTC, customers navigating to the 'Your Integrations' pages in the PagerDuty web application encountered a 404 'Page Not Found' error and were unable to access integration management pages. The issue impacted fewer than 5% of active accounts across the EU and US service regions, while existing integrations, event ingestion, notification delivery, and core incident management remained unaffected. No data loss occurred, and the rest of the PagerDuty platform remained fully operational.
Impact
The incident affected fewer than 5% of active accounts in the EU and US service regions, preventing access to integration management pages. No revenue, data, or operational impact occurred for core services like event ingestion, notification delivery, or incident management.
Trigger
The incident was triggered by the archiving of a feature flag that was no longer needed after the 'Your Integrations' page was successfully rolled out with 100% deployment across all service regions in early August. References to the flag in client-side routing logic were not detected by automated scanners, causing the browser to evaluate the route as inactive and display a 404 error.
Detection
The issue was detected through customer reports to the Support team, which initiated the Major Incident response process at 23:03 UTC. Operational monitoring systems did not flag the client-side 404 errors as service faults because backend infrastructure returned HTTP 200 success codes.
Resolution
Responders reproduced the rendering error, verified normal functionality of existing integrations, and traced the issue to the retired flag. At 23:12 UTC, the flag was unarchived, instantly restoring page availability across all environments. No additional capacity or resource adjustments were required.
Root Cause
The root cause was the retirement of a feature flag without removing all references to it in client-side routing logic. Automated scanners were not configured to parse client-side routing repositories, leading to undetected references. Archiving the flag caused the browser to treat the route as inactive, resulting in 404 errors. The backend infrastructure remained operational, returning HTTP 200 codes, which masked the issue from monitoring systems.