Pricing
Status historyRSS updatesStatus API

Powered by Uptimus

    Cornerstone outage history

    101 recorded Cornerstone incidents since October 2025, with official updates, affected components, duration and resolution information.

    Back to current status

    Intermittent Latency & Issues Launching Training - US SL3 and US SL5

    Started October 21, 2026 at 7:06 PM UTC · 4h 22m

    IssuesMinor incident
    Affected components
    LMSLMSUptimeResponse TimeResponse TimeUptime
    1. October 21, 2026 at 7:06 PM UTCinvestigating

      Some customers on US SL3 may experience intermittent latency and issues launching training. We are actively investigating the issue as a top priority and working to restore normal functionality as quickly as possible. We will continue to provide updates as more information becomes available.

    2. October 21, 2026 at 8:08 PM UTCmonitoring

      Our Engineering teams have confirmed the issue has subsided. We have validated that the issue is no longer reproducible and we are monitoring for the next hour before considering the issue resolved.

    3. October 21, 2026 at 8:42 PM UTCinvestigating

      We've received reports that this issue has resurfaced and our Engineering teams are investigating further. We'll continue to share updates as new information becomes available.

    4. October 21, 2026 at 9:29 PM UTCmonitoring

      Engineering has applied a fix and we have validated the issue is no longer reproducible. We will place this back in a monitoring status for at least one hour before considering the issue resolved.

    5. October 21, 2026 at 11:28 PM UTCresolved

      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.

    FTP inaccessible across UK Production

    Started October 20, 2026 at 9:13 PM UTC · 5h 52m

    OutageMajor incident
    Affected components
    Edge Import / Edge Loads (Stuck/Erroring)UptimeEdge Import / Edge Loads (Stuck/Erroring)UptimeUptimeEdge Import / Edge Loads (Stuck/Erroring)
    1. October 20, 2026 at 9:13 PM UTCinvestigating

      Our Engineering teams are performing an Emergency Change and as a result FTP across UK Production environment is currently inaccessible. We are working to restore access and will update here as soon as complete.

    2. October 20, 2026 at 10:58 PM UTCinvestigating

      Engineering is continuing to work on the Emergency Control Change As part of this work we have needed to pause Data Feeds and they will resume once this work is completed. We will continue to keep this page updated at least every 2 hours or as we get new information. We apologize for any inconvenience.

    3. October 21, 2026 at 1:00 AM UTCinvestigating

      Our Engineering teams are continuing to work on restoring FTP access across the UK Production environment. The issue remains under investigation, and we will provide a further update as soon as more information becomes available.

    4. October 21, 2026 at 3:04 AM UTCresolved

      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.

    Minor Issue - DLW Feeds not processing US SL1 and USL5

    Started October 20, 2026 at 4:18 PM UTC · 1d 3h

    IssuesMinor incident
    Affected components
    Edge Import / Edge Loads (Stuck/Erroring)Edge Import / Edge Loads (Stuck/Erroring)
    1. October 20, 2026 at 4:18 PM UTCinvestigating

      Data Load Wizard feeds are experiencing issues processing on US SL1 and US SL5 Swimlanes. 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.

    2. October 20, 2026 at 5:57 PM UTCidentified

      Engineering has identified a cause and we are currently validating a fix. We will continue sharing updates as they become available.

    3. October 20, 2026 at 7:11 PM UTCmonitoring

      A fix has been implemented and we have validated it's been successful. We will update this issue to Resolved after a period of monitoring.

    4. October 21, 2026 at 8:07 PM UTCresolved

      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.

    Major Issue - System availability issues on EU (FRA) Production

    Started October 19, 2026 at 9:35 AM UTC · 3h 30m

    OutageMajor incident
    Affected components
    Uptime
    1. October 19, 2026 at 9:35 AM UTCinvestigating

      The swimlane is experiencing some latency issues. Clients with portals in this swimlane may experience delays or issues accessing certain pages in the application. 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.

    2. October 19, 2026 at 10:01 AM UTCmonitoring

      A fix for this issue was implemented, and the issue has been mitigated. We are monitoring the swimlane performance before concluding this incident as resolved.

    3. October 19, 2026 at 1:05 PM UTCresolved

      This issue has been fully resolved, and all corrective actions have been completed successfully. No further impact is expected.

    Learner Home Latency – EU SL1 (FRA)

    Started October 16, 2026 at 9:30 AM UTC · 0m

    Pending
    1. October 16, 2026 at 7:41 PM UTCresolved

      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.

    Latency on JP PRD SL Portal

    Started October 16, 2026 at 12:49 AM UTC · 16m

    IssuesMinor incident
    Affected components
    Response Time
    1. October 16, 2026 at 12:49 AM UTCinvestigating

      The swimlane is experiencing some latency issues. Clients with portals in this swimlane may experience delays or issues accessing certain pages in the application. 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.

    2. October 16, 2026 at 12:57 AM UTCmonitoring

      The issue has been resolved. We are monitoring to ensure all services are back to normal.

    3. October 16, 2026 at 1:05 AM UTCresolved

      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.

    Minor Issue - DLW Feeds not processing US SL1 and USL5

    Started October 15, 2026 at 8:52 PM UTC · 1h 0m

    IssuesMinor incident
    Affected components
    Edge Import / Edge Loads (Stuck/Erroring)Edge Import / Edge Loads (Stuck/Erroring)
    1. October 15, 2026 at 8:52 PM UTCinvestigating

      Data Load Wizard feeds are experiencing issues processing on US SL1 and US SL5 Swimlanes. 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.

    2. October 15, 2026 at 9:53 PM UTCresolved

      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.

    EU (FRA) SL1 and FR (CDG) - Career Site not working

    Started October 14, 2026 at 8:05 AM UTC · 3h 12m

    OutageMajor incident
    Affected components
    Career Site downCareer Site down
    1. October 14, 2026 at 8:05 AM UTCinvestigating

      Portals on FR (CDG) and EU (FRA) SL1 may experience issues accessing Career Sites. 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.

    2. October 14, 2026 at 8:15 AM UTCidentified

      Cornerstone engineers have found the cause for this issue and are currently working on a fix

    3. October 14, 2026 at 9:52 AM UTCmonitoring

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

    4. October 14, 2026 at 11:17 AM UTCresolved

      Following the fix deployment we have observed stable performance of careersites. Hence this incident is concluded resolved.

    Reporting 2.0 – FRA (EU) SL1 - Unable to Create or Edit Reports Due to Unresponsive Report Builder

    Started October 12, 2026 at 7:43 AM UTC · 1h 30m

    OutageMajor incident
    Affected components
    Reporting 2.0
    1. October 12, 2026 at 7:43 AM UTCinvestigating

      Users may experience an issue with Reporting 2.0 in the Production environment, where the report builder fails to load the available data fields, preventing users from creating new reports or modifying existing ones. When users attempt to create a new report or edit an existing report, the report builder interface loads but does not display the available fields required to configure the report. As a result, users are unable to add or modify table columns, apply filters, or complete report configuration.

    2. October 12, 2026 at 9:13 AM UTCresolved

      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!

    Resolved: Issue while editing User records on US SL4 swim lane

    Started October 8, 2026 at 10:30 AM UTC · 0m

    Pending
    1. October 8, 2026 at 12:40 PM UTCresolved

      Issues were reported while users tried to edit User records on the US SL4 swim lane. The incident occurred on 8 October at 3:30 AM Pacific Time and was resolved by 5:20 AM Pacific Time.

    2. October 22, 2026 at 9:31 PM UTCpostmortem

      **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: * Monitor the health and availability of the underlying application service components to support early detection and timely response to similar service disruptions.

    Latency on CDG SL Portals

    Started October 7, 2026 at 9:25 AM UTC · 4h 58m

    IssuesMinor incident
    Affected components
    Response TimeResponse Time
    1. October 7, 2026 at 9:25 AM UTCinvestigating

      The swimlane is experiencing some latency issues. Clients with portals in this swimlane may experience delays or issues accessing certain pages in the application. 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.

    2. October 7, 2026 at 9:55 AM UTCidentified

      This issue is mitigated for CDG SL4. We continue to work on a fix for CDG SL1.

    3. October 7, 2026 at 10:19 AM UTCmonitoring

      This issue was mitigated, and SL performance is back to normal. We will continue to monitor before concluding that this incident is resolved.

    4. October 7, 2026 at 2:23 PM UTCresolved

      The issue has been resolved. The CSOD Technology Team observed a performance degradation affecting the CDG swimlanes. Clients with portals on these swimlanes may have experienced slow performance or intermittent errors while accessing the application.

    5. October 22, 2026 at 9:13 PM UTCpostmortem

      **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: * Reviewing change management procedures involving application service recycling to minimize potential disruptions to active workloads. * Strengthening capacity validation procedures to ensure required application capacity aligns with configured capacity before and after change activities.

    Latency on Reporting 2.0 - UK SL2 swimlane

    Started October 6, 2026 at 1:13 PM UTC · 5h 35m

    OutageMajor incident
    Affected components
    Reporting 2.0
    1. October 6, 2026 at 1:13 PM UTCinvestigating

      The UK SL2 swim lane is experiencing latency issues around Reporting 2.0. Clients with portals in this swim lane may experience delays or issues accessing Analytics reports in the application. 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.

    2. October 6, 2026 at 1:47 PM UTCmonitoring

      We have implemented a fix, and the latency has been resolved. We are closely monitoring the environment to ensure performance remains stable and the issue does not recur.

    3. October 6, 2026 at 2:44 PM UTCinvestigating

      It appears the issue has resurfaced, and CSOD technical teams are working to resolve it with top priority. More information will be shared as it becomes available.

    4. October 6, 2026 at 4:30 PM UTCmonitoring

      Engineering has implemented an additional solution. Reporting functionality has returned to normal operations following the change. We will keep the status of this issue in Monitoring for a couple of hours to ensure there isn't a recurrence.

    5. October 6, 2026 at 6:48 PM UTCresolved

      After a period of monitoring with no recurrence of the issue, we consider this incident resolved.

    6. October 20, 2026 at 7:30 AM UTCpostmortem

      **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:** * Review database performance and resource utilization during periods of high concurrent workload * Review Reporting 2.0 throttling capacity changes to ensure sufficient capacity is maintained for expected demand

    EU FRA SL1 Swimlane – System Latency

    Started October 2, 2026 at 2:34 PM UTC · 8h 33m

    IssuesMinor incident
    Affected components
    Response Time
    1. October 2, 2026 at 2:34 PM UTCinvestigating

      Clients with portals hosted in this swimlane may experience slower response times when accessing certain areas of the application. We are currently investigating the issue.

    2. October 2, 2026 at 4:14 PM UTCinvestigating

      We are continuing to actively investigate the latency issue and are treating this as a top priority. Our teams remain engaged and are working to identify the cause and restore normal performance as quickly as possible. We will continue to provide regular updates as our investigation progresses.

    3. October 2, 2026 at 6:27 PM UTCmonitoring

      We have implemented a fix, and the latency has been resolved. We are closely monitoring the environment to ensure performance remains stable and the issue does not recur.

    4. October 2, 2026 at 11:07 PM UTCresolved

      The CSOD Technology Team observed a performance degradation affecting this swimlane. After a period of monitoring we are considering the issue Resolved. The problem began at 7:46 AM Pacific Time and was resolved at 10:47 AM Pacific Time. During this time, clients with portals on this swimlane may have experienced slow performance or intermittent errors while accessing the application.

    5. October 19, 2026 at 5:18 PM UTCpostmortem

      **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:** * The team has added additional capacity to the EU Production environment * Planned workload redistribution to improve resource utilization and balance the load across the environment  * Monitoring will continue to identify potential performance degradation and help maintain service stability

    EU (FRA) Swimlane – Learner Home Latency

    Started October 1, 2026 at 1:47 PM UTC · 4h 29m

    IssuesMinor incident
    Affected components
    Response Time
    1. October 1, 2026 at 1:47 PM UTCinvestigating

      The EU (FRA) swimlane is currently experiencing latency issues affecting Learner Home. Clients with portals hosted in this swimlane may experience delays when accessing Learner Home and certain pages within the application. This issue is our top priority, and our Engineering teams are actively working to identify the root cause and restore normal performance as soon as possible. We will continue to monitor the situation and provide additional updates as they become available. Please check back periodically for the latest information.

    2. October 1, 2026 at 3:40 PM UTCinvestigating

      We are continuing to investigate this issue. Thank you for your continued patience.

    3. October 1, 2026 at 4:38 PM UTCmonitoring

      The latency issue with the EU (FRA) swimlane has been resolved. The Learner Home and other pages within the application should now be accessible. We are currently monitoring the environments to ensure continued stability.

    4. October 1, 2026 at 6:16 PM UTCresolved

      After a period of monitoring and no reoccurence, this is resolved.

    5. October 19, 2026 at 5:16 PM UTCpostmortem

      **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:** * The team has added additional capacity to the EU Production environment * Planned workload redistribution to improve resource utilization and balance the load across the environment  * Monitoring will continue to identify potential performance degradation and help maintain service stability

    High Event queue count in US SL3

    Started September 30, 2026 at 4:07 PM UTC · 32m

    OutageMajor incident
    Affected components
    Response Time
    1. September 30, 2026 at 4:08 PM UTCinvestigating

      US SL3 swim lane is experiencing delays in processing background or queued tasks. During this time, background tasks, including email processing, may take longer than usual to complete. Resolving this issue is our top priority, and we are working to fix it as quickly as possible. Please check back periodically for updates, which will be posted as they become available.

    2. September 30, 2026 at 4:39 PM UTCresolved

      CSOD Technology Team observed delays in processing background or queued tasks on US SL3 swim lane including emails. The problem began on 09/30/2026 06:27 AM - PDT and was resolved on 09/30/2026 09:20 AM - PDT. During this time, background tasks may have taken longer than normal to complete.

    3. October 22, 2026 at 8:53 PM UTCpostmortem

      **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: * Enhanced retry handling to reduce batch sizes when processing conflicts occur, minimizing the likelihood of repeated database deadlocks. * Improved error handling to ensure database deadlocks are properly identified and managed, preventing repeated attempts to process the same failed operations.

    Development Plans – Functional Issues and Errors in Production (All Swimlanes)

    Started September 29, 2026 at 11:14 AM UTC · 56m

    OutageMajor incident
    Affected components
    Response TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse Time
    1. September 29, 2026 at 11:14 AM UTCinvestigating

      Clients may experience functional issues when using Development Plans in Production, including errors or delays when performing certain tasks. Our Engineering Team is actively working with the appropriate domain team to identify the underlying cause and resolve the issue as quickly as possible. This is being treated as a high priority. Please check back periodically for additional updates, which will be posted as they become available.

    2. September 29, 2026 at 12:09 PM UTCresolved

      Our Engineering Team has confirmed the issue to be resolved. Thank you for your patience and understanding!

    3. October 22, 2026 at 7:14 PM UTCpostmortem

      **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: * Implemented end-to-end testing to validate core API functionality and confirm that required service components initialize correctly.

    Content Studio Service Disruption in EU and FR EXT Production Swimlanes

    Started September 24, 2026 at 10:47 AM UTC · 25m

    OutageMajor incident
    Affected components
    Response TimeResponse Time
    1. September 24, 2026 at 10:47 AM UTCinvestigating

      The Content Studio feature is currently experiencing issues in the FRA EXT and CDG SL1 environments and may be unavailable during this service disruption. Our Engineering Team is treating this as a top priority and is actively working to restore the service as soon as possible. Please check back periodically for additional updates, which will be shared as they become available. Thank you for your patience and understanding.

    2. September 24, 2026 at 10:47 AM UTCinvestigating

      We are continuing to investigate this issue.

    3. September 24, 2026 at 11:11 AM UTCresolved

      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!

    Issue with Core User Management functionality in US SL4 accounts

    Started September 24, 2026 at 12:00 AM UTC · 13h 30m

    Pending
    1. September 24, 2026 at 1:54 PM UTCresolved

      Resolved: Admins were previously unable to edit user records in the Production environment across multiple US SL4 (AWS) portals. When attempting to open a user record for editing through Admin > Tools > Core Functions > Users, the request failed with the error message, "An error occurred while processing your request." Our Engineering Team has resolved the issue, and admins can now access and edit user records as expected. Incident Duration: 05:27 AM to 06:29 AM PST

    2. September 30, 2026 at 2:11 AM UTCpostmortem

      **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: * Continued monitoring of application health and service availability to support early detection of similar conditions. * Continued monitoring of capacity and resource utilization to identify conditions that could contribute to service degradation.

    504 timeout gateway error on Reporting 2.0 (US Swimlanes 1,2 and 5)

    Started September 22, 2026 at 12:20 PM UTC · 1h 21m

    OutageMajor incident
    Affected components
    Response TimeResponse TimeResponse Time
    1. September 22, 2026 at 12:20 PM UTCinvestigating

      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!

    2. September 22, 2026 at 1:41 PM UTCresolved

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

    3. September 30, 2026 at 3:47 PM UTCpostmortem

      **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: * Continued monitoring of Report Architect processing services and supporting dependencies to support earlier detection of similar conditions. * Initiated a review of the recovery and resiliency behavior of supporting services to improve service continuity during similar disruptions.

    Minor Issue - Queue Latency - UK SL1

    Started September 21, 2026 at 8:51 PM UTC · 16h 41m

    IssuesMinor incident
    Affected components
    Response TimeUptime
    1. September 21, 2026 at 8:51 PM UTCinvestigating

      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.

    2. September 21, 2026 at 10:37 PM UTCinvestigating

      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

    3. September 22, 2026 at 1:10 PM UTCinvestigating

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

    4. September 22, 2026 at 1:32 PM UTCresolved

      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!