Skilljar driftsforstyrrelser

1. 17. august 2026 kl. 13.46 UTCinvestigating

   Vi er klar over et problem forårsager øget anvendelse fejl for en delmængde af kunder, og vores ingeniør team er aktivt undersøge. Vi arbejder flittigt på at afdække den grundlæggende årsag og genoprette tjenester. Vi opdaterer statussiden, så snart vi har identificeret problemet. Tak for Deres tålmodighed og forståelse, når vi behandler denne sag.

2. 17. august 2026 kl. 14.15 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 17. august 2026 kl. 18.09 UTCresolved

   Spørgsmålet er løst. Vi sætter pris på din forståelse og takker dig for din tålmodighed.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 9. juni 2026 kl. 17.38 UTCinvestigating

   We're aware of the ongoing issue with the Admin Dashboard, and our engineering team is actively investigating. We are working diligently to uncover the root cause and restore services. We will update the status page as soon as we have identified the issue. Thank you for your patience and understanding as we address this matter.

2. 9. juni 2026 kl. 17.40 UTCmonitoring

   A fix has been implemented for the identified issue impacting the Admin Dashboard, our team has entered the monitoring phase. We are actively observing the system to ensure stability. Regular updates on the monitoring progress will be provided on the status page. Thank you for your continued patience.

3. 9. juni 2026 kl. 18.51 UTCresolved

   The identified issue with Admin Dashboard has been resolved, and services are now operating smoothly. We appreciate your understanding and thank you for your patience.

1. 6. april 2026 kl. 19.34 UTCinvestigating

   We have identified elevated 504 timeout errors impacting the learner experience on the course platform. Learners may encounter errors or degraded performance when loading courses, progressing through content, or accessing learning paths. Our engineering team has identified the issue and is actively working on a fix. We will continue to post updates as remediation progresses.

2. 6. april 2026 kl. 19.55 UTCmonitoring

   A fix has been deployed to address the elevated 504 timeout errors on the learner-facing course platform. We are now monitoring to confirm the issue is fully resolved. Learners should see improved performance when accessing courses and loading content.

3. 6. april 2026 kl. 21.00 UTCresolved

   The identified issue with the course platform has been resolved, and services are now operating smoothly. We appreciate your understanding and thank you for your patience.

1. 2. april 2026 kl. 21.08 UTCinvestigating

   We are currently investigating reports of degraded performance on analytics pages within the Skilljar admin dashboard. Some users may experience slower than expected load times or timeouts when accessing reporting and analytics views. Our engineering team is actively looking into the root cause. Core platform functionality, including course delivery, learner access, and content management, remains unaffected.

2. 3. april 2026 kl. 15.48 UTCinvestigating

   Our engineering team continues to investigate the degraded performance affecting analytics pages in the Skilljar admin dashboard. We have identified several areas of interest and are actively working to isolate the root cause. Users may still experience slower than expected load times when accessing reporting and analytics views. All other platform functionality remains unaffected. We will continue to provide updates as our investigation progresses. Thank you for your continued patience.

3. 3. april 2026 kl. 22.12 UTCidentified

   Our engineering team has identified the root cause of the degraded performance affecting analytics pages in the Skilljar admin dashboard. A fix has been developed and is being deployed now. Users may continue to experience slower than expected load times on analytics views while the fix rolls out. All other platform functionality remains unaffected. We will provide another update once the fix is in place and we have confirmed performance has stabilized. Thank you for your patience.

4. 3. april 2026 kl. 22.33 UTCmonitoring

   A fix has been deployed to address the degraded performance affecting analytics pages in the Skilljar admin dashboard. Page load times should now be improving. Our engineering team is actively monitoring to confirm the fix is holding and performance has fully stabilized. If you continue to experience any issues, please reach out to our support team.

5. 3. april 2026 kl. 23.00 UTCresolved

   The performance issues affecting analytics pages in the Skilljar admin dashboard have been fully resolved. Page load times are back to normal and the platform is operating as expected. We appreciate your patience while our team worked through this issue.

1. 31. marts 2026 kl. 17.48 UTCidentified

   We've successfully identified an issue impacting Course Platform. Our engineering team is actively working on a resolution, and we'll keep you informed with regular updates on the status page. Thank you for your understanding as we work towards a fix.

2. 31. marts 2026 kl. 18.01 UTCmonitoring

   A fix has been implemented for the identified issue impacting the Course Platform, our team has entered the monitoring phase. We are actively observing the system to ensure stability. Regular updates on the monitoring progress will be provided on the status page. Thank you for your continued patience.

3. 31. marts 2026 kl. 19.03 UTCresolved

   The identified issue with the Course Platform has been resolved, and services are now operating smoothly. We appreciate your understanding and thank you for your patience.

1. 26. marts 2026 kl. 20.38 UTCresolved

   Between approximately 4:30 PM and 8:30 PM PT on March 25, 2026, some customers experienced display and formatting issues on their homepage and catalog pages. Affected pages may have failed to load correctly or displayed content in an unexpected layout. This issue was caused by an internal infrastructure update that temporarily impacted how cached page content was served. No customer action caused this issue.

1. 17. marts 2026 kl. 14.15 UTCinvestigating

   We're aware of the ongoing issue with student domains, and our engineering team is actively investigating. We are working diligently to uncover the root cause and restore services. We will update the status page as soon as we have identified the issue. Thank you for your patience and understanding as we address this matter.

2. 17. marts 2026 kl. 14.34 UTCmonitoring

   A fix has been implemented for the identified issue impacting student domains, our team has entered the monitoring phase. We are actively observing the system to ensure stability. Regular updates on the monitoring progress will be provided on the status page. Thank you for your continued patience.

3. 17. marts 2026 kl. 15.57 UTCresolved

   The identified issue with student domains has been resolved, and services continue operating smoothly. We appreciate your understanding and thank you for your patience.

1. 28. februar 2026 kl. 00.42 UTCidentified

   We're aware of an ongoing issue where Course and Path actions are not executing as expected. Our engineering team has identified the root cause and is working to restore full functionality. We will update the status page as progress is made. Thank you for your patience and understanding.

2. 28. februar 2026 kl. 01.50 UTCmonitoring

   A fix has been implemented for the identified issue impacting Course and Path actions, and our team has entered the monitoring phase. We are actively observing the system to ensure actions are processing as expected. Please note that some actions may take additional time to fully catch up. We will continue to provide updates on the status page. Thank you for your continued patience.

3. 28. februar 2026 kl. 14.48 UTCmonitoring

   The backlog of actions are continuing to be processed as expected. Please note that some actions may take additional time to fully catch up. We will continue to provide updates on the status page. Thank you for your continued patience.

4. 28. februar 2026 kl. 16.47 UTCresolved

   This incident has been resolved, all processing is back to normal.

1. 18. februar 2026 kl. 17.34 UTCinvestigating

   We are currently investigating reports of users receiving 403 errors when attempting to log in to the Course Platform. Our engineering team has been engaged and is actively working to identify the root cause and restore normal access. We will provide updates as more information becomes available. If you are affected, please try again shortly. We apologize for the inconvenience.

2. 18. februar 2026 kl. 17.54 UTCidentified

   We have identified the root cause of the 403 errors affecting login to Skilljar. A fix is currently being implemented and we expect service to be restored shortly. We will provide an update once the fix has been deployed and confirmed. We appreciate your patience and apologize for the disruption.

3. 18. februar 2026 kl. 18.07 UTCmonitoring

   A fix for the 403 errors affecting login to Skilljar has been deployed. We are currently monitoring the system to confirm the issue is fully resolved. Users should now be able to log in normally. If you continue to experience issues, please contact our support team. We will provide a final update once we have confirmed stability.

4. 18. februar 2026 kl. 18.34 UTCresolved

   The issue causing 403 errors during login to Skilljar has been fully resolved. All systems are operating normally. We have confirmed stability through our monitoring and no further impact is expected. We apologize for the disruption and thank you for your patience. If you experience any further issues, please don't hesitate to reach out to our support team.

1. 3. februar 2026 kl. 17.35 UTCinvestigating

   We're investigating an issue affecting customers using Salesforce (SFDC) SAML Single Sign-On, where users are unable to log in. Our teams are actively working on mitigation and will provide updates as progress is made.

2. 4. februar 2026 kl. 00.39 UTCresolved

   This incident has been resolved by the upstream service. Salesforce has rolled back a change they had made that affected Salesforce (SFDC) SAML Single Sign-On. For more information see Salesforce incident https://status.salesforce.com/incidents/20003660.

1. 13. januar 2026 kl. 00.31 UTCinvestigating

   We are investigating an ongoing issue that is causing delays in analytics processing and the display of new student records. Our engineering team is working diligently to resolve this backlog and restore full service. Note: All learner data and registrations are being captured securely; this is a display delay only. We will update the status page as soon as we have identified the root cause. Thank you for your patience.

2. 13. januar 2026 kl. 05.34 UTCmonitoring

   A fix has been implemented and we are now monitoring the recovery. Analytics data and new student records are beginning to populate in dashboards as the processing backlog clears. We expect all data to be fully up-to-date in the next few hours. Thank you for your patience while we restored service.

3. 13. januar 2026 kl. 14.52 UTCresolved

   The issue causing delays in analytics processing and student record visibility has been resolved. We apologize for the delay and appreciate your patience.

1. 9. december 2025 kl. 14.36 UTCidentified

   We've successfully identified the issue impacting certain Catalog Pages on Student Domains that use the In-Progress Content Block. A fix is being deployed, and we'll keep you informed with regular updates on the status page. Thank you for your understanding as we work towards a fix.

2. 9. december 2025 kl. 14.45 UTCmonitoring

   A fix has been implemented for the identified issue impacting the In-Progress Content Block on certain Catalog Pages, our team has entered the monitoring phase. We are actively observing the system to ensure stability. Regular updates on the monitoring progress will be provided on the status page. Thank you for your continued patience.

3. 9. december 2025 kl. 16.53 UTCresolved

   The identified issue with impacting certain Catalog Pages on Student Domains that use the In-Progress Content Block has been resolved, and services are now operating smoothly. We appreciate your understanding and thank you for your patience.

1. 20. november 2025 kl. 11.20 UTCinvestigating

   We are investigating increased Salesforce Connection failures. We will update soon as we have more details.

2. 20. november 2025 kl. 13.08 UTCmonitoring

   We’ve restored Salesforce functionality and sincerely apologize for the disruption this caused. To resume normal operations, please re-authenticate your Salesforce connection in the Skilljar Dashboard: https://dashboard.skilljar.com/salesforce/ Our team is actively monitoring the situation to ensure everything remains stable. Thank you for your patience and understanding.

3. 20. november 2025 kl. 15.32 UTCinvestigating

   We’re currently investigating an issue that is preventing customers from re-authenticating their Salesforce connection in the Skilljar Dashboard. Some users are seeing an "invalid_client_id" error during the process. Our engineering team is actively working to identify the cause and implement a fix as quickly as possible. We sincerely apologize for the inconvenience and appreciate your patience while we work to resolve this.

4. 20. november 2025 kl. 21.41 UTCinvestigating

   We are continuing to investigate the Salesforce connection issue identified earlier today. Further updates will be provided as soon as more information is available.

5. 21. november 2025 kl. 12.05 UTCidentified

   Our team has identified the issue disrupting the Salesforce connection and is actively working to restore access as quickly as possible. We want to reassure you that no data has been lost, and Skilljar continues to operate normally. This issue only affects the Salesforce integration. Thank you for your patience while we work to resolve it. We will provide updates as more information becomes available.

6. 22. november 2025 kl. 03.08 UTCidentified

   Thank you for your patience while we work to resolve this issue affecting Salesforce integrations. We will provide updates as more information becomes available.

7. 22. november 2025 kl. 19.42 UTCidentified

   The Salesforce and Gainsight incident remains ongoing. Our teams are actively working to resolve the issue and restore functionality as quickly and safely as possible. For the latest updates and FAQs, please visit the main status page: https://status.gainsight.com/incidents/gvng0kly8vwf

8. 2. december 2025 kl. 17.46 UTCidentified

   The Salesforce and Gainsight incident remains ongoing. Rest assured our teams are working around the clock to resolve the issue and restore functionality as quickly and safely as possible. In the meantime, we are preparing a workaround and steps to re-enable services. For the latest updates and FAQs, please visit the main status page: https://status.gainsight.com/incidents/gvng0kly8vwf

9. 11. december 2025 kl. 17.02 UTCidentified

   We continue to work closely with Salesforce to restore the Skilljar-Salesforce integration. At this time, the application remains offline and we do not recommend attempting to reconnect the integration. Our teams are actively engaged and will provide another update as soon as we have a confirmed path to re-enable the integration. Thank you for your patience while we work to bring this functionality back online.

10. 11. december 2025 kl. 20.43 UTCidentified

    Skilljar customers can now connect their instances with Salesforce by following the process outlined here: https://communities.gainsight.com/ce-skilljar-by-gainsight-18/skilljar-salesforce-reconnection-guide-29937

11. 11. december 2025 kl. 21.16 UTCmonitoring

    The Skilljar-Salesforce integration has now been re-enabled and customers can proceed with re-authenticating their connection. To restore full functionality, please follow the step-by-step reconnection guide available here: https://communities.gainsight.com/ce-skilljar-by-gainsight-18/skilljar-salesforce-reconnection-guide-29937 Our teams will continue monitoring to ensure stability. Thank you for your patience as we worked to restore the integration.

12. 13. december 2025 kl. 01.01 UTCresolved

    The Skilljar-Salesforce integration has been restored and has remained stable during monitoring. Customers can continue to re-authenticate the Skilljar-Salesforce app by following the reconnection steps here: https://communities.gainsight.com/ce-skilljar-by-gainsight-18/skilljar-salesforce-reconnection-guide-29937 For additional background on the broader Salesforce advisory and Gainsight’s response, please see: - Overview of the incident and restoration of connections: https://www.gainsight.com/blog/salesforce-re-enables-gainsight-connections/ - Mandiant investigation summary: https://www.gainsight.com/blog/mandiant-investigation-summary/ - CrowdStrike investigation summary: https://www.gainsight.com/blog/crowdstrike-investigation-summary/ We are closing this incident and will continue to monitor the integration as part of our standard reliability practices. Thank you for your patience and partnership throughout this event.

1. 6. november 2025 kl. 23.46 UTCinvestigating

   We're aware of the ongoing issue causing increased application errors, and our engineering team is actively investigating. We are working diligently to uncover the root cause and restore services. We will update the status page as soon as we have identified the issue. Thank you for your patience and understanding as we address this matter.

2. 6. november 2025 kl. 23.52 UTCidentified

   We've successfully identified the issue causing increased application errors. Our engineering team is actively working on a resolution, and we'll keep you informed with regular updates on the status page. Thank you for your understanding as we work towards a fix.

3. 6. november 2025 kl. 23.59 UTCmonitoring

   A fix has been implemented for the identified issue causing increased application errors, our team has entered the monitoring phase. We are actively observing the system to ensure stability. Regular updates on the monitoring progress will be provided on the status page. Thank you for your continued patience.

4. 7. november 2025 kl. 00.34 UTCresolved

   The identified issue has been resolved, and services are now operating smoothly. We appreciate your understanding and thank you for your patience.

1. 20. oktober 2025 kl. 12.32 UTCresolved

   Skilljar's course platform and dashboard were affected by the AWS outage that occurred early this morning. The issue has been resolved, and we are ensuring that no lasting effects are felt. Thank you for your patience during this regional issue.

1. 23. september 2025 kl. 17.06 UTCidentified

   We've successfully identified the issue impacting delayed analytics and reporting. Our engineering team is actively working on a resolution, and we'll keep you informed with regular updates on the status page. Thank you for your understanding as we work towards a fix.

2. 23. september 2025 kl. 18.05 UTCidentified

   We have resolved the underlying issue and are working through a backlog of analytics and reporting data. Data should be up to date within a few hours. We will update the status page when the backlog has been processed. Thank you for your understanding.

3. 24. september 2025 kl. 04.57 UTCresolved

   The delay in analytics and reporting has been resolved, and all backlog data has been fully processed. Thank you for your patience and understanding while we worked through this issue.

1. 6. august 2025 kl. 14.20 UTCinvestigating

   We're aware of the ongoing issue causing increased errors on loading the course platform, and our engineering team is actively investigating. We are working diligently to uncover the root cause and restore services. We will update the status page as soon as we have identified the issue. Thank you for your patience and understanding as we address this matter.

2. 6. august 2025 kl. 15.14 UTCinvestigating

   We are continuing to investigate and have identified networking issues with incoming requests. We will update the status page as soon as we have completely identified the issue. Thank you for your patience and understanding as we address this matter.

3. 6. august 2025 kl. 15.34 UTCidentified

   We have identified the issue with request networking through one of our security providers. We are working to address the issue now. Thank you again for your patience as we work towards resolution.

4. 6. august 2025 kl. 17.14 UTCresolved

   We have resolved the networking issue with our security provider, and all course platform sites are now available.

1. 15. juli 2025 kl. 16.58 UTCidentified

   We've successfully identified an issue impacting analytics data being populated. There is no data loss. We are seeing analytics being delayed on the Skilljar Admin Dashboard and delays to data propagation on the data connector. Our engineering team is actively working on a resolution, and we'll keep you informed with regular updates on the status page. Thank you for your understanding as we work towards a fix.

2. 15. juli 2025 kl. 18.47 UTCidentified

   The issue impacting analytics data delays on the Skilljar Admin Dashboard and data connector is still being actively addressed by our engineering team. We are making steady progress and are committed to resolving the issue as quickly as possible. Regular updates will continue to be provided here. We appreciate your patience and understanding.

3. 15. juli 2025 kl. 21.55 UTCmonitoring

   We have implemented a fix for the analytics data delays on the Skilljar Admin Dashboard and data connector, and our team is now in the monitoring phase. We are closely observing the system to ensure stability while we work through processing the backlog of data. Analytics is still experiencing delays, and we thank you for your continued patience during this time.

4. 16. juli 2025 kl. 18.06 UTCmonitoring

   The analytics data on the Skilljar Admin Dashboard and data connector is currently approximately 36 hours behind. Our team is actively working to process the backlog, and we anticipate that data will be fully up-to-date within the next 24 hours. Thank you for your patience as we work towards resolving this issue.

5. 17. juli 2025 kl. 17.43 UTCmonitoring

   We are still experiencing delays in analytics data on the Skilljar Admin Dashboard and data connector. Our team is actively working to address the issue and expedite the resolution process. We appreciate your continued patience and will keep you updated on our progress.

6. 18. juli 2025 kl. 22.46 UTCresolved

   The identified issue causing delays in analytics data on the Skilljar Admin Dashboard and data connector has been resolved, and services are now operating normally. We appreciate your understanding and thank you for your patience.

1. 20. maj 2025 kl. 18.33 UTCidentified

   We've identified an issue impacting the API. Our engineering team is actively working on a resolution, and we'll keep you informed with regular updates on the status page. Thank you for your understanding as we work towards a fix.

2. 20. maj 2025 kl. 18.56 UTCmonitoring

   A fix has been implemented for the identified issue impacting the API, our team has entered the monitoring phase. We are actively observing the system to ensure stability. Regular updates on the monitoring progress will be provided on the status page. Thank you for your continued patience.

3. 20. maj 2025 kl. 19.06 UTCresolved

   The identified issue with the API has been resolved, and services are now operating smoothly. We appreciate your understanding and thank you for your patience.

1. 22. april 2025 kl. 17.36 UTCinvestigating

   We're aware of the ongoing issue with delays in analytics and reporting, and our engineering team is actively investigating. We are working diligently to uncover the root cause and restore services. We will update the status page as soon as we have identified the issue. Thank you for your patience and understanding as we address this matter.

2. 22. april 2025 kl. 21.05 UTCinvestigating

   We are continuing to investigate the delay in analytics and reporting.

3. 23. april 2025 kl. 16.49 UTCinvestigating

   We are still continuing our investigation into delayed analytics and reporting.

4. 23. april 2025 kl. 17.12 UTCidentified

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

5. 23. april 2025 kl. 20.36 UTCmonitoring

   A fix has been implemented and we are currently monitoring the results. While Analytics and Reporting remain delayed, we expect data to be fully caught up within 2 days. We are also actively exploring ways to reduce this timeline and will provide updates as progress is made.

6. 24. april 2025 kl. 22.17 UTCmonitoring

   A fix has been implemented and we are continuing to monitor the results. Analytics and Reporting remain delayed; however, based on current progress, we now estimate that data will be fully caught up within the next 12 hours.

7. 25. april 2025 kl. 16.52 UTCresolved

   The issue impacting Analytics and Reporting delays has been fully resolved. Data is now fully caught up, and all systems are operating normally. Thank you for your patience while we worked to address this.