- Detected by Pingoru
- Oct 12, 2026, 07:43 AM UTC
- Resolved
- Oct 12, 2026, 09:13 AM UTC
- Duration
- 1h 29m
Affected: Reporting 2.0
Timeline · 2 updates
-
investigating Oct 12, 2026, 07:43 AM UTC
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.
-
resolved Oct 12, 2026, 09:13 AM 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!
Read the full incident report →
- Detected by Pingoru
- Oct 08, 2026, 10:30 AM UTC
- Resolved
- Oct 08, 2026, 10:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 08, 2026, 12:40 PM UTC
Issues were reported while users tried to edit User records on the US SL4 swim lane. The incident occurred at 3:30 AM Pacific Time and was resolved by 5:20 AM Pacific Time.
Read the full incident report →
- Detected by Pingoru
- Oct 07, 2026, 09:25 AM UTC
- Resolved
- Oct 07, 2026, 02:23 PM UTC
- Duration
- 4h 58m
Affected: Response TimeResponse Time
Timeline · 4 updates
-
investigating Oct 07, 2026, 09:25 AM UTC
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.
-
identified Oct 07, 2026, 09:55 AM UTC
This issue is mitigated for CDG SL4. We continue to work on a fix for CDG SL1.
-
monitoring Oct 07, 2026, 10:19 AM UTC
This issue was mitigated, and SL performance is back to normal. We will continue to monitor before concluding that this incident is resolved.
-
resolved Oct 07, 2026, 02:23 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Oct 06, 2026, 01:13 PM UTC
- Resolved
- Oct 06, 2026, 06:48 PM UTC
- Duration
- 5h 35m
Affected: Reporting 2.0
Timeline · 5 updates
-
investigating Oct 06, 2026, 01:13 PM UTC
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.
-
monitoring Oct 06, 2026, 01:47 PM UTC
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.
-
investigating Oct 06, 2026, 02:44 PM UTC
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.
-
monitoring Oct 06, 2026, 04:30 PM UTC
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 reoccurrence.
-
resolved Oct 06, 2026, 06:48 PM UTC
After a period of monitoring with no recurrence of the issue, we consider this incident resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2026, 02:34 PM UTC
- Resolved
- Oct 02, 2026, 11:07 PM UTC
- Duration
- 8h 33m
Affected: Response Time
Timeline · 4 updates
-
investigating Oct 02, 2026, 02:34 PM UTC
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.
-
investigating Oct 02, 2026, 04:14 PM UTC
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.
-
monitoring Oct 02, 2026, 06:27 PM UTC
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.
-
resolved Oct 02, 2026, 11:07 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Oct 01, 2026, 01:47 PM UTC
- Resolved
- Oct 01, 2026, 06:16 PM UTC
- Duration
- 4h 29m
Affected: Response Time
Timeline · 4 updates
-
investigating Oct 01, 2026, 01:47 PM UTC
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.
-
investigating Oct 01, 2026, 03:40 PM UTC
We are continuing to investigate this issue. Thank you for your continued patience.
-
monitoring Oct 01, 2026, 04:38 PM UTC
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.
-
resolved Oct 01, 2026, 06:16 PM UTC
After a period of monitoring and no reoccurence, this is resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 30, 2026, 04:07 PM UTC
- Resolved
- Sep 30, 2026, 04:39 PM UTC
- Duration
- 31m
Affected: Response Time
Timeline · 2 updates
-
investigating Sep 30, 2026, 04:08 PM UTC
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.
-
resolved Sep 30, 2026, 04:39 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Sep 29, 2026, 11:14 AM UTC
- Resolved
- Sep 29, 2026, 12:09 PM UTC
- Duration
- 55m
Affected: Response TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse Time
Timeline · 2 updates
-
investigating Sep 29, 2026, 11:14 AM UTC
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.
-
resolved Sep 29, 2026, 12:09 PM UTC
Our Engineering Team has confirmed the issue to be resolved. Thank you for your patience and understanding!
Read the full incident report →
Notice September 24, 2026 - Detected by Pingoru
- Sep 24, 2026, 01:30 PM UTC
- Resolved
- Sep 24, 2026, 01:30 PM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Sep 24, 2026, 10:47 AM UTC
- Resolved
- Sep 24, 2026, 11:11 AM UTC
- Duration
- 24m
Affected: Response TimeResponse Time
Timeline · 3 updates
-
investigating Sep 24, 2026, 10:47 AM UTC
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.
-
investigating Sep 24, 2026, 10:47 AM UTC
We are continuing to investigate this issue.
-
resolved Sep 24, 2026, 11:11 AM 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!
Read the full incident report →
- Detected by Pingoru
- Sep 22, 2026, 12:20 PM UTC
- Resolved
- Sep 22, 2026, 01:41 PM UTC
- Duration
- 1h 20m
Affected: Response TimeResponse TimeResponse Time
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Sep 21, 2026, 08:51 PM UTC
- Resolved
- Sep 22, 2026, 01:32 PM UTC
- Duration
- 16h 41m
Affected: UptimeResponse Time
Timeline · 4 updates
-
investigating Sep 21, 2026, 08:51 PM UTC
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.
-
investigating Sep 21, 2026, 10:37 PM UTC
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
-
investigating Sep 22, 2026, 01:10 PM UTC
This issue is still under active investigation by our Engineering Team. We will continue to share significant updates as we make progress.
-
resolved Sep 22, 2026, 01:32 PM UTC
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!
Read the full incident report →
- Detected by Pingoru
- Sep 18, 2026, 11:37 AM UTC
- Resolved
- Sep 18, 2026, 12:34 PM UTC
- Duration
- 57m
Affected: Response TimeResponse TimeResponse TimeResponse Time
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Sep 14, 2026, 02:09 PM UTC
- Resolved
- Sep 14, 2026, 06:06 PM UTC
- Duration
- 3h 56m
Affected: Response Time
Timeline · 3 updates
-
identified Sep 14, 2026, 02:09 PM UTC
The issue has been identified and engineering is working on restoring the service.
-
monitoring Sep 14, 2026, 03:58 PM UTC
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.
-
resolved Sep 14, 2026, 06:06 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 08, 2026, 02:03 PM UTC
- Resolved
- Sep 09, 2026, 05:35 PM UTC
- Duration
- 1d 3h
Affected: Response Time
Timeline · 6 updates
Read the full incident report →
- Detected by Pingoru
- Sep 04, 2026, 07:53 PM UTC
- Resolved
- Sep 05, 2026, 03:44 AM UTC
- Duration
- 7h 50m
Affected: Response TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse TimeResponse Time
Timeline · 7 updates
-
investigating Sep 04, 2026, 07:53 PM UTC
This swimlane is experiencing some functional issues accessing the xAPI Statement viewer and may have issues with xAPI statement processing. Clients with portals in this swimlane may experience delays or issues executing some tasks. 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.
-
investigating Sep 04, 2026, 09:48 PM UTC
We are continuing to investigate this issue and will share an update at least every 2 hours or until we have more.
-
identified Sep 04, 2026, 11:02 PM UTC
Cornerstone Engineering has identified the issue and is currently working on a fix. We will update once the issue is Resolved.
-
identified Sep 05, 2026, 01:06 AM UTC
We are still working on a fix and will confirm once it has been successfully deployed. This remains a top priority for our teams and we will continue sharing updates as they become available or at least every 2 hours.
-
monitoring Sep 05, 2026, 01:50 AM UTC
A fix has been deployed and we are seeing no errors. We will monitor for 1 hour before placing this in a Resolved status.
-
resolved Sep 05, 2026, 03:44 AM UTC
After a period of monitoring with no repeat occurrences we are marking this incident Resolved. A formal Root Cause Analysis will be available 7-10 business days from Resolution.
-
postmortem Sep 23, 2026, 07:07 AM UTC
**Root Cause Analysis** **Issue:** On September 4th, 2026, the xAPI service started returning errors during authentication of incoming requests. **Impact:** The issue prevented affected users from successfully loading or interacting with xAPI statement data, disrupting normal viewing functionality. **Root Cause:** The Public API Gateway infrastructure was updated to address a gap related to authentication for some endpoints \(not xAPI\). This change had an unintended impact on the xAPI service and caused a system regression. **Corrective Action:** On September 4th, 2026, the Public API Gateway infrastructure was rolled back to an earlier version which did not have this regression. **Preventive Action:** * On September 4th, 2026, changes were reverted entirely and a different mitigation was performed to ensure that behavior expected by xAPI is maintained. * Additional automation is being added to the Public API Gateway which asserts that the expected behavior of xAPI is not regressed.
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 11:52 AM UTC
- Resolved
- Sep 03, 2026, 04:12 PM UTC
- Duration
- 4h 19m
Affected: Response Time
Timeline · 5 updates
Read the full incident report →
- Detected by Pingoru
- Sep 03, 2026, 05:00 AM UTC
- Resolved
- Sep 03, 2026, 05:00 AM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Sep 02, 2026, 04:16 PM UTC
- Resolved
- Sep 03, 2026, 12:56 PM UTC
- Duration
- 20h 40m
Affected: Response TimeResponse TimeResponse TimeResponse TimeResponse Time
Timeline · 4 updates
Read the full incident report →
Critical September 1, 2026 - Detected by Pingoru
- Sep 01, 2026, 02:02 PM UTC
- Resolved
- Sep 01, 2026, 02:43 PM UTC
- Duration
- 41m
Affected: Uptime
Timeline · 4 updates
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2026, 09:00 AM UTC
- Resolved
- Aug 27, 2026, 09:00 AM UTC
- Duration
- —
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Aug 26, 2026, 03:33 AM UTC
- Resolved
- Aug 26, 2026, 03:33 AM UTC
- Duration
- —
Affected: UptimeUptimeUptimeUptime
Timeline · 2 updates
Read the full incident report →
- Detected by Pingoru
- Aug 24, 2026, 12:49 PM UTC
- Resolved
- Aug 24, 2026, 02:05 PM UTC
- Duration
- 1h 15m
Affected: Response Time
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 01:53 PM UTC
- Resolved
- Aug 20, 2026, 02:57 PM UTC
- Duration
- 1h 3m
Affected: Response TimeResponse TimeResponse TimeResponse Time
Timeline · 3 updates
Read the full incident report →
- Detected by Pingoru
- Aug 20, 2026, 12:06 PM UTC
- Resolved
- Aug 20, 2026, 12:51 PM UTC
- Duration
- 45m
Affected: Response TimeResponse TimeResponse TimeResponse Time
Timeline · 4 updates
Read the full incident report →