Cornerstone incident

UK SL2 - Error 500 on reporting 2.0

Notice Resolved View vendor source →

Cornerstone experienced a notice incident on May 7, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
May 07, 2026, 11:01 AM UTC
Resolved
May 07, 2026, 04:30 AM UTC
Duration
Detected by Pingoru
May 07, 2026, 11:01 AM UTC

Update timeline

  1. resolved May 07, 2026, 11:01 AM UTC

    Client with portals on UK SL2 may have experienced error 500 when accessing Reporting 2.0. This issue started on May 6th, 2026, 09:13 PM PDT and was resolved on May 6th 2026, 10:00 PM PDT.

  2. postmortem May 12, 2026, 06:19 PM UTC

    **Issue Summary:** On May 6, 2026, users in the UK Production environment, including UK SL1, SL2, and SL3, experienced intermittent errors within Reporting 2.0. The issue occurred for a brief duration and resulted in occasional request failures and delays. **Root Cause:** The issue was caused by transient service instability within the Reporting 2.0 application flow. This instability temporarily impacted request processing for a subset of requests, resulting in intermittent HTTP 500 error responses. **Corrective Action:** The impacted application service was restarted to restore normal request processing. After the recovery action was completed, service stability was restored and Reporting 2.0 functionality returned to normal. **Preventive Measures:** To reduce the risk of recurrence, Cornerstone is taking the following action: * Reinforcing application stability checks to support faster detection and recovery in the event of similar transient service interruptions.