Cornerstone Outage History

Cornerstone's US SL4 region experienced a service disruption from 8:39 AM to 9:22 AM Pacific Time, causing users to encounter login failures and 404 errors when accessing the application. The performance degradation affected clients in this region with slow performance and intermittent errors during the outage period. The issue was identified, fixed, and resolved after monitoring confirmed no further recurrence.

The Cornerstone career site experienced a performance degradation that prevented users from accessing career pages, with users encountering error messages stating "An error occurred while processing your request." The issue affected clients with portals on the US swimlanes from 6:50am to 7:34am Pacific Time. The engineering team deployed a fix and monitored the system until the issue was fully resolved.

The Cornerstone career site became unavailable for 24.4 hours, preventing users from accessing career pages and displaying error messages when attempting to load the site. The engineering team identified the root cause and deployed a fix, followed by 24 hours of monitoring to ensure stability. The issue was fully resolved with no further recurrences observed.

A recurring issue with Cornerstone's Reporting 2.0 system affected US swimlanes clients, causing difficulties accessing reports and delays in portal actions. The incident lasted 37 minutes, occurring from approximately 6:20 AM to 6:53 AM PST on April 30, 2026. The Engineering Team resolved the functionality issues and is working on implementing a long-term fix to prevent future recurrences of this problem that was previously reported on April 13, 2026.

Cornerstone's US production environment experienced recurring issues with Reporting 2.0 functionality, preventing users from accessing reports and causing delays in performing certain tasks. The issue initially surfaced, was resolved, then resurfaced multiple times over the course of the incident, affecting clients with portals in the US swimlanes. Engineering teams implemented fixes and monitored the system for a week with no further recurrences before declaring the issue fully resolved.

Cornerstone's US swimlanes experienced functional issues that prevented users from accessing reports in Reporting 2.0, causing delays and disruptions for clients with portals in the affected swimlane. The engineering team identified the root cause and deployed a fix after 4.1 hours. The issue was resolved with no further recurrences after a monitoring period.

Cornerstone experienced performance degradation affecting US swimlanes (US SL1, US SL2, US SL3, US SL5) from 11:45 AM to 12:55 PM Pacific Time on March 30th. Customers experienced slow performance and intermittent errors when accessing the Manage Candidates page. The engineering team implemented a fix to resolve the issue and monitored the system for stability before marking the incident as resolved.

Cornerstone experienced an issue causing Edge Import loads and feeds to fail during processing on US swimlanes, affecting response times. Emergency maintenance was performed over 3.4 hours, during which new Edge Import and Bulk API jobs were prevented from entering the queue and users encountered 503 errors when accessing Edge Import. The maintenance was completed successfully, restoring full operational status with all new and impacted scheduled jobs resuming normal processing.

Cornerstone's Galaxy clients across UK and EU regions experienced latency issues and 504 gateway timeout errors when accessing certain application pages. The performance degradation affected clients with portals in these regional swimlanes, causing slow performance and intermittent errors. The issue was identified and resolved within approximately 17 minutes of the initial problem occurrence.

Cornerstone experienced intermittent latency spikes and errors affecting customers on a US swimlane for 85 hours. Customers may have experienced slow performance and intermittent errors while accessing the application during this period. The engineering team identified the root cause, implemented mitigation measures, deployed a permanent fix during non-business hours, and resolved the issue after monitoring confirmed stability.