Cornerstone Status Page

May 28, 2026 · resolved May 28

A severe production incident occurred in the US PROD environment, causing intermittent issues with Reporting 2.0 services across multiple swimlanes. The CSX application was impacted, experiencing degraded performance and potential data inconsistencies. Our engineering teams identified the issue and deployed a fix. We closely monitored the situation to ensure stability. After a period of monitoring with no further recurrences, the issue has been resolved.

May 21, 2026 · resolved May 21

After a period of monitoring with no further recurrence observed, the issue is now considered resolved. The CSOD Technology Team identified a performance degradation impacting US SL4 customers. The issue began at 8:39 AM Pacific Time and was resolved at 9:22 AM Pacific Time. During this period, clients with portals in this region may have experienced slow performance or intermittent errors while accessing/working on the application.

May 7, 2026 · resolved May 7

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

May 5, 2026 · resolved May 5

**Incident Summary:** Between May 4th and May 5th, 2026, the Career Site Service functionality in the US Production environment experienced intermittent errors across multiple swimlanes \(SL1, SL2, SL3, and SL5\). The issue impacted user access to Career Site functionalities and was classified as a Severity 2 incident. **Impact:** Users experienced intermittent failures while accessing the Career Site, resulting in degraded user experience and partial service disruption during the incident window. **Root Cause Analysis \(RCA\):** The incident was caused by a sudden traffic surge that exceeded the available service capacity during auto-scaling events. Due to the service sensitivity to cold starts, newly created instances were unable to stabilize before receiving high traffic, leading to repeated overload conditions and delayed scaling response. **Resolution:** The issue was mitigated by identifying scaling and capacity limitations as the root cause. Minimum instance thresholds were increased to prevent under-provisioning, and the affected component was redeployed to restore service stability. **Preventive Measures:** * Minimum instance thresholds were increased to maintain adequate baseline capacity. * Auto-scaling responsiveness was improved to better handle sudden traffic spikes and reduce the impact of cold-start scenarios. * Additional scaling optimizations were implemented to improve service stability during high traffic events.

May 4, 2026 · resolved May 5

**Incident Summary:** Between May 4th and May 5th, 2026, the Career Site Service functionality in the US Production environment experienced intermittent errors across multiple swimlanes \(SL1, SL2, SL3, and SL5\). The issue impacted user access to Career Site functionalities and was classified as a Severity 2 incident. **Impact:** Users experienced intermittent failures while accessing the Career Site, resulting in degraded user experience and partial service disruption during the incident window. **Root Cause Analysis \(RCA\):** The incident was caused by a sudden traffic surge that exceeded the available service capacity during auto-scaling events. Due to the service sensitivity to cold starts, newly created instances were unable to stabilize before receiving high traffic, leading to repeated overload conditions and delayed scaling response. **Resolution:** The issue was mitigated by identifying scaling and capacity limitations as the root cause. Minimum instance thresholds were increased to prevent under-provisioning, and the affected component was redeployed to restore service stability. **Preventive Measures:** * Minimum instance thresholds were increased to maintain adequate baseline capacity. * Auto-scaling responsiveness was improved to better handle sudden traffic spikes and reduce the impact of cold-start scenarios. * Additional scaling optimizations were implemented to improve service stability during high traffic events.