Cornerstone Outage History

**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.

**Incident Summary:** Starting April 13th, 2026, intermittent errors were observed in reporting functionality across US Production swimlanes \(SL1, SL2, SL3, and SL5\). **Root Cause Analysis \(RCA\):** The issue was caused by the auto-scaling mechanism. Newly provisioned nodes were not fully ready to handle reporting requests, leading to processing delays and request timeouts. **Corrective Action:** Auto-scaling \(scale-out\) has been temporarily paused. The system is currently operating on a fixed, increased server capacity without scale-in or scale-out to ensure stability. **Preventive Actions:** * Capacity has been proactively increased to handle expected load without relying on auto-scaling. * Additional nodes are being utilized with auto-scaling disabled to maintain consistent performance. * Engineering teams deployed enhancements with the May 8th patch to improve node readiness and ensure seamless scaling in the future.

**Incident Summary:** Starting April 13th, 2026, intermittent errors were observed in reporting functionality across US Production swimlanes \(SL1, SL2, SL3, and SL5\). **Root Cause Analysis \(RCA\):** The issue was caused by the auto-scaling mechanism. Newly provisioned nodes were not fully ready to handle reporting requests, leading to processing delays and request timeouts. **Corrective Action:** Auto-scaling \(scale-out\) has been temporarily paused. The system is currently operating on a fixed, increased server capacity without scale-in or scale-out to ensure stability. **Preventive Actions:** * Capacity has been proactively increased to handle expected load without relying on auto-scaling. * Additional nodes are being utilized with auto-scaling disabled to maintain consistent performance. * Engineering teams are working on enhancements to improve node readiness and ensure seamless scaling in the future.

**Issue Summary:** On March 22, 2026, Edge import–related errors were observed across the US Production swimlanes \(US SL1, US SL2, US SL3, US SL5\). **Root Cause:** The issue was caused by instability within the underlying cluster infrastructure, which disrupted queue services and prevented message processing, resulting in Edge import failures across the affected swimlanes. **Corrective Action:** On March 23, 2026, emergency maintenance was performed to stabilize and reset the impacted cluster components. Once stabilized, queue processing resumed and pending Edge imports were successfully completed. **Preventive Measures:** To minimize the risk of recurrence, the cluster infrastructure was thoroughly analyzed and validated as stable following remediation.