Is Cornerstone down?

A production incident occurred in the US PROD environments, causing intermittent issues with Reporting 2.0 services across multiple swimlanes. The CSX application was impacted, experiencing degraded performance and access challenges to the reports. Our engineering are actively investigating this issue. We will keep you posted on any significant updates. Thank you for your patience and understanding!

Our Engineering Team has confirmed the issue to be resolved. We will share a Root Cause Analysis in 7-10 business days. Thank you!

This swimlane is experiencing some delays in processing background or queued tasks. During this time, background tasks may take longer than normal to complete. This is our top priority and we are working to resolve the problem as soon as possible. Please check back periodically for additional updates, which will be posted as they become available.

The standard queue has been cleared but there remain some Learning Assignments which are still processing slower than expected. This remains under investigation and we will share more as soon as possible

This issue is still under active investigation by our Engineering Team. We will continue to share significant updates as we make progress.

Our Engineering Team has confirmed that the issue has been resolved. All background tasks in the queue have been completed, and processing is now operating as expected. Thank you for your patience and understanding!

Engineering team is analyzing the root cause of the Imports and Feeds incident.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

The issue has been identified and engineering is working on restoring the service.

A fix has been implemented, and the queues are no longer stuck. However, it will take some time to clear the backlog. We are continuing to monitor the queue.

This incident has been resolved.

A production incident occurred in the EU Production environment hosted in Frankfurt (FRA PRD), resulting in the Careersite service becoming completely unavailable. The issue has been identified, and the Engineering team is actively working on a resolution. Given the high severity of the incident, restoring service remains our top priority, and the team is working diligently to restore functionality as quickly as possible.

A fix has been deployed, and we are seeing no errors. We will monitor for one hour before placing this in Resolved status.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

No new reports of Career Site inaccessibility noted during last 24 hours. Hence we close this status page. Given recent occurrences engineering team is actively working on permanent solution to prevent future inconvenience.

**Root Cause Analysis** ‌ **Incident Summary:** Between Sep. 3rd and Sep. 8th, 2026, there were three Production incidents that affected Career Site functionality. This issue was intermittent across the FRA SL1 Production environment. These incidents occurred * Sep. 3rd from 4:37 am - 5:02 am PT * Sep. 7th from 2:13 pm - 2:25 pm PT * Sep. 8th from 6:20 am - 8:14 am PT **Impact:** Users experienced intermittent failures while accessing Career Site functionality. This resulted in a degraded user experience and partial service disruption during the incident window. **Root Cause:** The issue was caused by a sudden increase in traffic that temporarily exceeded the available service capacity. During the resulting scale-up activity, newly provisioned application capacity required additional time to become fully operational and could not immediately accommodate the increased demand. The limited capacity buffer combined with the application startup time resulted in intermittent service failures until sufficient capacity was available to handle the traffic. **Resolution:** * The service capacity and scaling configuration were adjusted to maintain an appropriate capacity buffer and better accommodate sudden increases in traffic. The affected service was also redeployed to restore stability * As a permanent improvement, the service has been moved to infrastructure with enhanced scaling capabilities to respond more rapidly to sudden increases in traffic. Since Sep. 12th, the new infrastructure has been fully handling service traffic **Preventive Measures:** * The service has been transitioned to infrastructure with improved scaling capabilities to better accommodate unexpected traffic increases * Capacity and application health will continue to be monitored during traffic fluctuations to ensure sufficient resources are available to maintain service stability