Cornerstone logo

Cornerstone

Learning Management
Description
Cornerstone is an enterprise learning and talent experience platform that helps organizations develop and retain talent. It provides LMS, skills management, content, and workforce development for corporate learning and HR.
Recent Incidents (Last 24 Hours)
Last refresh: 2026-07-03 07:22 UTC (1h ago)

Minor Issue - Latency - US Swimlanes

Resolved

**Incident Summary:** Beginning in mid-April 2026, users in the US Production environment \(SL1, SL2, SL3, and SL5\) experienced intermittent 502 and 504 Gateway Timeout errors while accessing the platform. The issue primarily occurred during periods of elevated traffic and affected multiple customers, resulting in occasional request failures and degraded platform responsiveness. **Root Cause:*...

Incident
Location:
Started: 2026-06-17 21:46 UTC (15d ago)
Updated: 2026-07-02 18:20 UTC (14h ago)
Resolved: 2026-06-18 00:00 UTC (15d ago)
2026-06-18 00:00 UTC (15d ago) : This incident has been resolved.
2026-06-17 22:21 UTC (15d ago) : Our engineering teams have identified the cause and implemented a fix. We've validated that the issue is no longer present. We will monitor for 1 hour before marking this incident resolved.
2026-06-17 21:46 UTC (15d ago) : The swimlane is experiencing some latency issues. Clients with portals across US Swimlanes 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.

Intermittent Errors and Timeouts Observed on US Swimlanes

Resolved

**Incident Summary:** Beginning on June 1, 2026, some customers in the US Production environment, including SL1, SL2, SL3, and SL5, experienced periods of intermittent latency. The issue primarily affected platform responsiveness and request processing, resulting in slower response times across certain application flows. **Root Cause:** The issue was caused by insufficient service capacity duri...

Incident
Location:
Started: 2026-06-03 16:44 UTC (29d ago)
Updated: 2026-07-02 16:56 UTC (15h ago)
Resolved: 2026-06-11 17:36 UTC (21d ago)
2026-06-11 17:36 UTC (21d ago) : After a few days of monitoring and no recurrences we are considering this issue Resolved. A Root Cause Analysis will be shared within 7-10 business days.
2026-06-08 19:19 UTC (24d ago) : As a result of our continued investigation with AWS, we have implemented a network update to further address the intermittent errors and timeouts. Initial results following the change are positive, and we are continuing to actively monitor the environment to confirm sustained stability. If any new occurrences are identified, we will investigate further and provide additional updates as appropri...
2026-06-08 17:38 UTC (24d ago) : A fix has been implemented and we are monitoring the results.

RESURFACED: Intermittent Timeouts Observed on US Production Environment

Resolved

**Incident Summary:** Beginning on June 1, 2026, some customers in the US Production environment, including SL1, SL2, SL3, and SL5, experienced periods of intermittent latency. The issue primarily affected platform responsiveness and request processing, resulting in slower response times across certain application flows. **Root Cause:** The issue was caused by insufficient service capacity duri...

Incident
Location:
Started: 2026-06-02 14:35 UTC (Jun 02, 2026)
Updated: 2026-07-02 16:55 UTC (15h ago)
Resolved: 2026-06-03 05:20 UTC (Jun 03, 2026)
2026-06-23 08:13 UTC (10d ago) : **Incident Summary:** On June 2nd, 2026, clients in the US Production environment \(SL1, SL2, SL3, and SL5\) experienced brief latency. The issue primarily impacted platform responsiveness, request processing, and caused timeout errors. **Impact:** Users experienced intermittent latency and delayed responses while accessing services. The degradation affected multiple application flows, leading ...
2026-06-03 05:20 UTC (Jun 03, 2026) : The scheduled Emergency maintenance has been completed, and the intermittent timeout issues should be resolved now.
2026-06-02 17:51 UTC (Jun 02, 2026) : We are planning Emergency Maintenance today at 9:00 PM PT to address this issue. During the maintenance window, the system may be unavailable for up to one hour. Intermittent timeouts may continue until the maintenance is completed. The maintenance is being scheduled outside of peak business hours to reduce overall customer impact. We will continue to provide additional updates as more informat...

Intermittent timeouts observed on US Production Environment

Resolved

**Incident Summary:** Beginning on June 1, 2026, some customers in the US Production environment, including SL1, SL2, SL3, and SL5, experienced periods of intermittent latency. The issue primarily affected platform responsiveness and request processing, resulting in slower response times across certain application flows. **Root Cause:** The issue was caused by insufficient service capacity duri...

Incident
Location:
Started: 2026-06-01 14:52 UTC (Jun 01, 2026)
Updated: 2026-07-02 16:54 UTC (15h ago)
Resolved: 2026-06-01 23:15 UTC (Jun 01, 2026)
2026-06-23 04:19 UTC (10d ago) : **Incident Summary:** On June 1st, 2026, clients in the US Production environment \(SL1, SL2, SL3, and SL5\) experienced intermittent latency for a brief duration. The issue primarily impacted platform responsiveness and request processing. **Impact:** Users experienced intermittent latency and delayed responses while accessing services. The degradation affected multiple application flows, lead...
2026-06-01 23:15 UTC (Jun 01, 2026) : The CSOD Technology Team observed a performance degradation affecting this swimlane. The problem began at 7:24 AM Pacific Time and was resolved at 11:25 AM Pacific Time. During this time, clients with portals on this swimlane may have experienced slow performance or intermittent errors while accessing the application.
2026-06-01 20:53 UTC (Jun 01, 2026) : Our engineering teams have confirmed that the issue has been fixed. We are currently monitoring for at least 1 hour before marking the issue resolved.