checked Oct 24, 2026 6:07 AM UTC · Cornerstone's official status page
Cornerstone is up and running.
All components operational
Statusfield watches Cornerstone alongside the rest of your stack and tells you when its status changes. Email, Slack, Microsoft Teams, PagerDuty, and webhooks.
30-day free trial — no card needed. First-time customers; continued monitoring requires a paid subscription.
20 reports published by Cornerstone in the last 30 days
When Cornerstone breaks, it is typically resolved in 3h 20m — median across 11 resolved incidents over 30 days.
resolvedOct 21 · 23:28 UTC
The CSOD Technology Team observed an issue with users launching training. The problem was intermittent between 11 AM Pacific Time and was resolved at 2 PM Pacific Time. During this time, users may have experienced issues accessing and launching training from their transcripts. Please contact Global Product Support if this issue is persisting.
Reported by Cornerstone on their status page.
resolvedOct 21 · 03:04 UTC
Our Engineering team has confirmed that FTP access across the UK Production environment has been restored. We have also performed checks on our side, and no further issues have been observed so far.
Reported by Cornerstone on their status page.
resolvedOct 21 · 20:07 UTC
After a full day of monitoring we are considering this issue resolved. A formal Root Cause Analysis will be published within 7-10 business days including preventive measures.
Reported by Cornerstone on their status page.
resolvedOct 19 · 13:05 UTC
This issue has been fully resolved, and all corrective actions have been completed successfully. No further impact is expected.
Reported by Cornerstone on their status page.
resolvedOct 16 · 09:30 UTC
Some customers on EU SL1 (FRA) may have experienced increased latency beginning at approximately 5:30 AM PT. The degradation primarily impacted the Learner Home service, resulting in slower response times when accessing and navigating the platform. The issue subsided at approximately 7:30 AM PT, and service performance has since returned to normal. We will provide a Root Cause Analysis (RCA) within 7 to 10 business days.
Reported by Cornerstone on their status page.
resolvedOct 16 · 01:05 UTC
The CSOD Technology Team observed a performance degradation affecting this swimlane. The problem began at 17:26 and was resolved at 18:03, 15 Oct PDT. During this time, clients with portals on this swimlane may have experienced slow performance or intermittent errors while accessing the application.
Reported by Cornerstone on their status page.
resolvedOct 15 · 21:53 UTC
The CSOD Technology Team observed issues with Data Load Wizard processing on US SL1 and US SL5. The problem began at 12:47 PM Pacific Time and was resolved at 1:10 PM Pacific Time. During this time, Feeds for Data Load Wizard may have been stuck or not processing. A fix has been deployed and after internal validation we have confirmed the issue is resolved.
Reported by Cornerstone on their status page.
resolvedOct 14 · 11:17 UTC
Following the fix deployment we have observed stable performance of careersites. Hence this incident is concluded resolved.
Reported by Cornerstone on their status page.
resolvedOct 12 · 09:13 UTC
The Engineering Team has confirmed that Reporting 2.0 is now functioning as expected. This is successfully resolved. Thank you for your patience and understanding!
Reported by Cornerstone on their status page.
postmortemOct 22 · 21:31 UTC
Issue Summary:
On October 8, 2026, customers in the US SL4 Production environment experienced issues accessing user records. Affected users were temporarily unable to access user records, resulting in a disruption to the associated functionality.
Root Cause:
The issue was caused by an unhealthy component within the underlying application service, which disrupted the processing of user record requests. As a result, the affected service was unable to process requests as expected, causing the User Record functionality to become temporarily unavailable.
Corrective Action:
Cornerstone recycled the affected application nodes to restore service health and functionality. Following these actions, the service recovered, and users were able to access user records successfully.
Preventive Measures:
To reduce the risk of a similar issue, Cornerstone continues to take the following action:
Reported by Cornerstone on their status page.
postmortemOct 22 · 21:13 UTC
Issue Summary:
On October 7, 2026, users in the CDG SL1 and CDG SL4 Production environments experienced increased latency when accessing Learner Home. Affected users experienced delays in loading and navigating Learner Home, resulting in temporary performance degradation.
Root Cause:
The issue was caused by an application service disruption during a scheduled change activity that involved recycling the underlying application service. Additionally, a discrepancy between the required application capacity and the capacity configured during the change prevented certain application nodes from starting as expected in CDG SL1. This delayed service recovery and prolonged the latency experienced by affected users.
Corrective Action:
Cornerstone increased application capacity to support service recovery and investigated the impact of the ongoing change activity. Following completion of the change activity and restoration of the required application nodes, service performance improved, and Learner Home latency returned to normal.
Preventive Measures:
To reduce the risk of a similar issue, Cornerstone is taking the following actions:
Reported by Cornerstone on their status page.
postmortemOct 20 · 07:30 UTC
Root Cause Analysis
Incident Summary:
On October 6th, 2026, High CPU utilization was observed in the UK SL2 Production environment, resulting in significant performance degradation in Reporting 2.0 and Dashboards.
Impact:
Users experienced delays in loading and refreshing dashboards, slower report generation, and intermittent failures when exporting reports to Excel. Performance degradation was observed during the incident until mitigation measures were applied.
Root Cause:
The incident was caused by high database resource utilization due to multiple resource-intensive analytics and reporting operations running concurrently. This placed significant pressure on available memory and processing capacity, affecting overall database performance. Additionally, Reporting 2.0 throttling capacity had been reduced the previous night, limiting the system's ability to handle concurrent reporting requests. The combined impact contributed to high CPU utilization and prolonged response times.
Resolution:
The DBA team applied corrective measures to address the database performance spikes. Reporting 2.0 throttling capacity was restored to its previous level. Following these actions, dashboard refresh times improved to expected levels.
Preventive Measures:
Reported by Cornerstone on their status page.
postmortemOct 19 · 17:18 UTC
Root Cause Analysis
Incident Summary:
On Oct. 1st and again on Oct. 2nd, 2026, users across the FRA SL1 Production environment experienced issues accessing Learner Home.
Impact:
Affected users experienced difficulties loading Learner Home and increased response times, resulting in a degraded learning experience.
Root Cause:
The incident was caused by elevated resource utilization in the FRA SL1 Production environment. This affected the performance of backend application components, resulting in increased response times and intermittent errors.
Resolution:
The team implemented corrective configuration changes and took steps to improve resource utilization. Following these actions, Learner Home functionality recovered and the immediate incident was resolved.
Preventive Measures:
Reported by Cornerstone on their status page.
postmortemOct 19 · 17:16 UTC
Root Cause Analysis
Incident Summary:
On Oct. 1st and again on Oct. 2nd, 2026, users across the FRA SL1 Production environment experienced issues accessing Learner Home.
Impact:
Affected users experienced difficulties loading Learner Home and increased response times, resulting in a degraded learning experience.
Root Cause:
The incident was caused by elevated resource utilization in the FRA SL1 Production environment. This affected the performance of backend application components, resulting in increased response times and intermittent errors.
Resolution:
The team implemented corrective configuration changes and took steps to improve resource utilization. Following these actions, Learner Home functionality recovered and the immediate incident was resolved.
Preventive Measures:
Reported by Cornerstone on their status page.
postmortemOct 22 · 20:53 UTC
Issue Summary:
On September 30, 2026, the US SL3 Production environment experienced delays in processing queued operations, resulting in an unusually high volume of events. Affected operations were unable to process at the expected rate, causing events to accumulate in the queue and delaying completion of activities.
Root Cause:
The issue was caused by database deadlocks occurring during concurrent data merge operations. When these conflicts occurred, the application attempted to retry the affected operations without sufficiently reducing the batch size of learning objects being processed. This resulted in repeated database conflicts, preventing queued events from being processed efficiently and causing an accumulation of events.
Corrective Action:
Cornerstone implemented a fix to improve the application's retry logic and database deadlock handling. The update addressed repeated processing conflicts by adjusting how failed operations are retried, allowing data merge operations to be processed more efficiently.
Preventive Measures:
To reduce the risk of a similar issue, Cornerstone has taken the following actions:
Reported by Cornerstone on their status page.
postmortemOct 22 · 19:14 UTC
Issue Summary:
On September 29, 2026, users across all Production regions experienced errors when accessing the Development Plan functionality within Guide. Affected users were temporarily unable to access or use the Development Plan functionality during the incident window.
Root Cause:
The issue was caused by an application initialization failure following a recent framework update. As a result, certain components required by the Development Plan service did not initialize correctly, leading to application errors and disruption of the affected functionality.
Corrective Action:
Cornerstone updated the affected software dependencies to address the initialization failure and restore normal operation of the Development Plan service. Following these changes, the required service components initialized successfully, allowing the affected functionality to resume normal operation.
Preventive Measures:
To reduce the risk of a similar issue, Cornerstone has taken the following action:
Reported by Cornerstone on their status page.
postmortemSep 30 · 02:11 UTC
Issue Summary:
On September 24, 2026, users in the US SL4 Production environment experienced an issue accessing the User Record page. Affected users were temporarily unable to access the page, resulting in disruption to employee-related functionality during the incident window.
Root Cause:
The issue was caused by an unexpected application processing condition that affected the availability of the service supporting User Record functionality. As a result, requests associated with the User Record page failed intermittently, causing the functionality to become temporarily unavailable.
Corrective Action:
Cornerstone recycled the affected application service and restored it to a healthy state, which resolved the issue and restored access to the User Record page. Following recovery, the affected functionality was validated and confirmed to be operating normally.
Preventive Measures:
To reduce the risk of a similar issue, Cornerstone is taking the following actions:
Reported by Cornerstone on their status page.
resolvedSep 24 · 11:11 UTC
Our Engineering Team has confirmed that the issue has been resolved, and the Content Studio feature has been restored. Thank you for your patience and understanding!
Reported by Cornerstone on their status page.
postmortemSep 30 · 15:47 UTC
Issue Summary:
On September 22, 2026, users in the US Production environment experienced issues generating and accessing reports through Report Architect. Affected users were temporarily unable to generate or view certain reports during the incident window.
Root Cause:
The issue was caused by a temporary disruption affecting a supporting backend service dependency used by Report Architect processing services. During the incident, the dependency intermittently failed to provide the service information required by certain report processing workloads. This disrupted the report processing flow and resulted in timeout errors when users attempted to generate or access reports.
Corrective Action:
Cornerstone restored the affected backend service dependency, allowing report processing workloads to resume normal operation. Following recovery, report generation and access were validated, and Report Architect functionality was confirmed to be operating normally.
Preventive Measures:
To reduce the risk of a similar issue, Cornerstone is taking the following actions:
Reported by Cornerstone on their status page.
postmortemOct 9 · 08:46 UTC
Incident Summary
On September 18th users in the UK , MetPol Production and Pilot environments experienced issues accessing the Imports and Feeds functionality.
Impact
Affected users were unable to access and manage Imports and Feeds during the incident window, resulting in disruption to the affected functionality.
Root Cause Analysis (RCA)
The incident occurred during a planned maintenance activity.
As part of the maintenance activity, changes were performed on an active host supporting the Imports and Feeds functionality. The activity required a restart of supporting services; however, the restart did not complete as expected for the dependent application workload.
As a result, a supporting service did not recover as expected, which caused the dependent Imports and Feeds functionality to become temporarily unavailable.
Resolution
The affected supporting services were restored to a healthy state and the required recovery activities were completed.
Following recovery, the dependent services were validated and the Imports and Feeds functionality was tested to confirm that access and normal operation had been restored.
Preventive Measures
Reported by Cornerstone on their status page.
