Platform: Global – Privileged Remote Access Page Unavailable (404)

Update timeline

1. identified Jun 24, 2025, 01:55 PM UTC

   We are currently investigating an issue affecting the Privileged Remote Access sessions and configuration page, which is currently returning a 404 Page Not Found error. This issue appears to be the result of a recent deployment. Our engineering team has identified the root cause and is in the process of rolling back the release to restore functionality. We will provide an update as soon as mitigation is confirmed. Thank you for your patience and understanding.

2. monitoring Jun 24, 2025, 02:04 PM UTC

   The rollback has been completed, and the Privileged Remote Access configuration page is now accessible. Impact Start Time: June 24, 2025 – 08:11 AM Central Impact End Time: June 24, 2025 – 08:49 AM Central We appreciate your patience while we worked to resolve the issue. If you continue to experience any problems, please contact our support team at https://support.delinea.com.

3. resolved Jun 24, 2025, 02:12 PM UTC

   This incident has been resolved.

4. postmortem Jul 14, 2025, 05:02 PM UTC

   **Incident Overview** On June 24, 2025, between 8:11 AM and 8:49 AM Central \(GMT-05:00\), users globally were unable to access the Privileged Remote Access \(PRA\) page. Attempts to load the page resulted in a 404 error, and users were unable to perform any PRA-related actions during this window. **Root Cause** The issue was caused by a bug introduced in the latest production release. The bug led to failures in fetching dynamically imported modules and JavaScript files, resulting in incomplete page loads and 404 errors for the PRA interface. This issue was not detected in the lower testing silos because those environments did not share the same dependency build as Production. As a result, automated tests in those environments passed successfully despite the underlying issue. To mitigate the impact, the release was rolled back to the previous stable version, which restored normal functionality. **Preventive Actions** * Align dependency builds in lower testing silos to match those in Production environments. * Enhance automated testing to cover scenarios involving dynamic module loading and dependency mismatches.