Cornerstone Outage History

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.

The Cornerstone US SL1 production environment experienced a service disruption with SSL errors making the service unavailable for 7.3 hours starting at 9:30 AM PST. The issue was identified and resolved by 12:50 PM PST, with services restored to normal operations. After continued monitoring, the incident was fully resolved by 5:59 PM PST.

Cornerstone experienced increased latency in the EU Production environment affecting Galaxy customers using LXP and LMS services, causing slower page load times and intermittent errors. The performance degradation lasted approximately 6 hours, with the core issue occurring between 4:28 AM and 5:19 AM Pacific Time. The engineering team identified and resolved the root cause, restoring normal response times and service operations.

Cornerstone experienced increased latency in the UK Stage Environment for 8.9 hours, causing slower page load times and eventual errors for users. The engineering team identified and resolved the underlying issue, restoring normal response times. Communication continued through an existing Known Issue channel since only the Stage environment was affected, with Production environments remaining stable throughout the incident.