Cornerstone incident
Users Unable to Access Career Site (US Swimlanes)
Cornerstone experienced a notice incident on May 4, 2026 affecting Uptime and Uptime and 1 more component, lasting 1d. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified May 04, 2026, 02:10 PM UTC
Cornerstone career site is currently unavailable. Users attempting to access the career page are unable to load the site and are encountering an error message stating: “An error occurred while processing your request.” Our engineering team has identified the issue and is actively working to restore full service. We will keep you posted on significant updates to this concern.
- monitoring May 04, 2026, 03:03 PM UTC
Our Engineering team has deployed a fix to address this concern. We will continue to closely monitor the situation to ensure stability. Further updates will be shared through the Known Issue article and Statuspage. Thank you for your understanding and patience.
- resolved May 05, 2026, 02:31 PM UTC
After monitoring the Career Site operations for 24 hours with no further recurrences observed, we consider this issue resolved. Thank you for your patience and understanding!
- postmortem May 21, 2026, 04:01 AM UTC
**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.