Go1 Outage History

Started Sep 15, 2026, 04:10 PM UTC· resolved Sep 15, 2026, 11:35 PM UTC

1. investigating Sep 15, 2026, 04:10 PM UTC

   We are experiencing intermittent issues with logging in to the Go1 system. We are currently investigating the problems on our platform.

2. investigating Sep 15, 2026, 04:11 PM UTC

   We are continuing to investigate this issue.

3. monitoring Sep 15, 2026, 07:07 PM UTC

   Login and authentication services are stable while still being monitored for any reported errors.

4. resolved Sep 15, 2026, 11:35 PM UTC

   Authentication services have remained stable, and users are able to log in normally. We identified that a high-volume scheduled integration process caused a sudden increase in login-related background updates. This placed unexpected load on supporting services and resulted in intermittent login failures for some customers. We are implementing improvements to process these non-critical updates separately from the login flow. This will help ensure that background processing issues do not prevent users from accessing Go1. We apologise for the disruption and appreciate your patience while we investigated and resolved this incident.

Read the full incident report →

Started Jul 30, 2026, 12:57 PM UTC· resolved Jul 30, 2026, 01:34 PM UTC

1. identified Jul 30, 2026, 12:57 PM UTC

   We’ve determined that some users may encounter a generic error in Go1 Learn when creating a user or viewing User Details from the People tab. User management workflows may be affected. We’re working to restore normal functionality.

2. identified Jul 30, 2026, 01:19 PM UTC

   We have identified the cause of an issue affecting user management in the Go1 Learn People tab. Some administrators may encounter a generic error when creating a user or viewing user details. A fix is being deployed. We will provide a further update once deployment is complete and the service has been validated.

3. resolved Jul 30, 2026, 01:34 PM UTC

   The profile page issue affecting some customer portals is now resolved. We have confirmed that profile access and user creation are working again on affected portals, and we are no longer seeing the earlier error there.

Read the full incident report →

Started Jun 01, 2026, 12:25 AM UTC· resolved Jun 22, 2026, 10:26 PM UTC

1. investigating Jun 01, 2026, 12:25 AM UTC

   We recently completed scheduled maintenance on 26 May 2026. Following this, some users are experiencing issues accessing, launching, and completing certain courses — our team is actively investigating.

2. identified Jun 01, 2026, 02:19 AM UTC

   The issue has been identified, and team is working towards the fix.

3. identified Jun 01, 2026, 03:39 AM UTC

   We are continuing to work on a fix.

4. identified Jun 01, 2026, 05:27 AM UTC

   We are continuing to work on a fix. Apologies for any inconvenience caused.

5. identified Jun 01, 2026, 06:44 PM UTC

   We are continuing to work through a resolution to the ongoing inconsistencies for completions. Our team will provide an update as soon as possible. Thank you for your ongoing patience.

6. identified Jun 02, 2026, 04:10 AM UTC

   Update - We have identified the root causes of the issues following our scheduled maintenance on 26 May, and our team is actively working through fixes across each affected area. Content launching - We have resolved the majority of content launch failures and are continuing to address remaining cases. If you are still unable to launch content, please contact support. Completions - Some completions are not reflecting correctly on the platform. We have identified multiple contributing causes and are working through fixes for each. If you notice completions that are not reflecting as expected, please contact support with the affected user and enrolment details so we can prioritise. We will continue to update this page as each area is resolved.

7. monitoring Jun 03, 2026, 04:08 AM UTC

   Enrolment & Playback Issues – Updates -3 June Content Not Launching 404 errors – Monitoring after fix applied. 400 errors – 🟢 Monitoring after fix applied. 500 errors – 🟡 Fix in progress. Approximately 56 enrolments across 6 portals impacted daily. Content Not Marked as Complete Courses (complete in Staff, not platform) – 🟢 Data corrected via reindex (11 May – 2 June). Courses (in progress in Staff and platform) – 🟡 Manual fixes underway via automated skill. Interactives progression – 🟢 Fix script applied to impacted enrolments. Awards – 🟡 Collecting impacted enrolments for manual fix. Resolution expected within 3 days. Thank you for your continued patience.

8. monitoring Jun 03, 2026, 04:16 AM UTC

   Update — Fixes are progressing well across each affected area. Here is the latest status. Content launching The majority of launch issues have been resolved. A small number of cases are still being addressed and we expect these to be cleared shortly. If you experience content failing to launch from 3 June onwards, please contact support. Completions We have corrected the display of completion data for enrolments dating back to 11 May. Our team is continuing to work through a small number of remaining cases that require individual attention. If you notice completions that are still not reflecting as expected, please contact support with the affected user and course details. We will continue to update this page as remaining items are resolved.

9. monitoring Jun 07, 2026, 09:54 PM UTC

   Enrolment & Completion Incidents — Active Investigation Following recent infrastructure migration, we are actively investigating and resolving several issues affecting content playback, enrolments, and completions. Content Not Launching 404 / 400 errors — Fix applied; monitoring in progress. 500 errors — Fix script currently running; resolution in progress. Content Not Completing Courses (showing complete in admin, not on platform) — Re-indexing enrolments daily from May 21st onward; ongoing. Courses (showing in-progress in admin) — Impacted enrolments being collected for manual remediation; expected within 7 days. Interactives progression — Fix script currently running; resolution in progress. Awards — Impacted enrolments being collected for manual remediation; expected within 7 days once upstream issues are resolved. We are actively working to resolve all impacted cases. Further updates will be posted as fixes are confirmed. We apologise for the disruption.

10. monitoring Jun 08, 2026, 10:32 PM UTC

    UPDATE: Several completion-related issues remain resolved, including previously reported problems with completions not being recorded and enrolments remaining in progress. Playback errors, course enrolments not completing, and multi-course completion issue are all on track for closure on June 10, 2026, with no new playback error instances identified on June 9, 2026. The awards completion issue may also be ready for closure on June 10, 2026, while batch recalculation work for awards credit calculations is still underway. We have also been continuing our audit of partner webhook requests for potentially missed completion events since June 5, 2026, and this review will continue on June 10, 2026.

11. monitoring Jun 09, 2026, 11:20 PM UTC

    UPDATE: Several completion-related issues remain resolved, including previously reported problems with completions not being recorded and enrolments remaining in progress. Playback errors continue to show only a small trickle of instances and remain under monitoring. Course enrolments not completing are being addressed on demand, while the multi-course completion issue is awaiting customer acknowledgement of the recommended content fix and remains on track for closure. The awards completion issue remains under investigation following the discovery of an unrelated issue, while work to resolve synchronization issues between myGo1 and Go1 Learn is already underway. Duplicate records affecting awards credit calculations have been cleaned up, with no further instances identified today. We have also continued our audit of partner webhook requests for potentially missed completion events since June 5, 2026. This review remains ongoing, and completion webhooks continue to be triggered as affected records are identified through the audit process.

12. monitoring Jun 10, 2026, 10:28 PM UTC

    UPDATE: There are no major active concerns at this time, with most efforts now focused on post-incident review and validation activities. Playback errors continue to be monitored, with only a small number of new instances observed. A deeper forensic analysis has commenced using a fresh database snapshot to identify any underlying causes. Course enrolment issues continue to be addressed on demand as required. Several previously identified issues have now been resolved, including awards completion processing, awards credit calculation discrepancies, the multi-course completion issue, and synchronization of awards completion data between myGo1 and Go1 Learn. No further recalculations or duplicate records were identified today, and a bug fix for the completion date sync is currently under review. Our audit of partner webhook requests for enrolment completions remains ongoing. No additional corrections were required today, and monitoring will continue as part of the broader review process. Thank you for your ongoing patience.

13. monitoring Jun 11, 2026, 11:22 PM UTC

    UPDATE No major active concerns have been identified since the previous update. Current efforts remain focused on validation, monitoring, and post-incident review activities. Recently resolved items remain stable, and validation of implemented fixes is ongoing. Review of the completion date synchronization fix and completion sync is progressing as planned. Monitoring and verification activities will remain in place as part of the broader review process. Thank you for your continued patience and support.

14. monitoring Jun 15, 2026, 11:57 PM UTC

    UPDATE No significant new issues have been identified since the last update. Teams continue to focus on validation activities, ongoing monitoring, and post-incident review efforts. Previously resolved items remain stable, with verification of implemented fixes continuing as expected. Assessment of the completion date synchronization fix and related completion sync processes is progressing according to plan. Monitoring and validation measures will remain active as part of the overall review and assurance process. Thank you for your continued patience and support.

15. resolved Jun 22, 2026, 10:26 PM UTC

    This incident has been fully resolved, and all affected services are operating normally. Our team identified the underlying issue, implemented the necessary remediation, and has verified that platform performance and functionality have returned to expected levels. We will continue to monitor the environment to ensure ongoing stability. We apologize for the disruption and appreciate your patience while we worked to restore service.

Read the full incident report →

Started May 29, 2026, 05:46 AM UTC· resolved May 29, 2026, 12:39 PM UTC

1. investigating May 29, 2026, 05:46 AM UTC

   We are currently investigating an issue where some content may intermittently fail to launch or play in the Go1 player.

2. identified May 29, 2026, 09:42 AM UTC

   We’ve identified an issue affecting some client-created interactive and SCORM-style content where content may fail during the player launch process. In affected cases, the player shell can load but the interactive launch step may return an error, preventing the content from opening successfully. We’re actively investigating affected learning objects and applying remediation while we work on the broader fix.

3. identified May 29, 2026, 09:43 AM UTC

   The issue has identified and mitigation efforts are currently underway.

4. resolved May 29, 2026, 12:39 PM UTC

   We’ve applied remediation for the issue affecting some client-created interactive and SCORM-style content in the Go1 player, and affected content should now be launching normally. We’ll continue to monitor closely to ensure playback remains stable.

Read the full incident report →

Started May 26, 2026, 01:52 AM UTC· resolved May 26, 2026, 02:32 AM UTC

1. investigating May 26, 2026, 01:52 AM UTC

   We are currently having issues around portal access, and the team is now investigating.

2. resolved May 26, 2026, 02:32 AM UTC

   This incident has been resolved. Apologies for any inconvenience caused.

Read the full incident report →

Started May 11, 2026, 12:51 PM UTC· resolved May 11, 2026, 01:32 PM UTC

1. identified May 11, 2026, 12:51 PM UTC

   We found issues with login due to SSO errors. We are currently investigating the problems in our platform.

2. identified May 11, 2026, 01:00 PM UTC

   We are continuing to work on a fix for this issue.

3. resolved May 11, 2026, 01:32 PM UTC

   The intermittent single sign-on login failures caused by a scaling issue in our authentication service between 22:06 and 22:37 AEST are resolved. The service automatically recovered at 22:37 AEST, and all sign-on attempts have been succeeding since. We are tuning the autoscaler to help prevent recurrence.

Read the full incident report →

Started May 08, 2026, 03:39 AM UTC· resolved May 08, 2026, 05:24 AM UTC

1. investigating May 08, 2026, 03:39 AM UTC

   We found issues with login and loading the Go1 system. We are currently investigating the problems in our platform.

2. identified May 08, 2026, 03:41 AM UTC

   The issue has been identified. A fix is currently being worked on and will be implemented.

3. monitoring May 08, 2026, 03:55 AM UTC

   A fix has been implemented and we're currently monitoring the results. We should start seeing the services back to normal as expected.

4. monitoring May 08, 2026, 05:12 AM UTC

   We are continuing to monitor for any further issues.

5. resolved May 08, 2026, 05:24 AM UTC

   We are glad to inform that the issue has been resolved now. We found the cause of this temporary disruption and have fixed the root of the issue. Apologies for any inconvenience caused.

Read the full incident report →

Started Apr 14, 2026, 01:01 AM UTC· resolved Apr 14, 2026, 02:13 AM UTC

1. monitoring Apr 14, 2026, 01:01 AM UTC

   Our team is currently experiencing service disruptions and are investigating. We will continue to monitor the situation and provide updates as soon as the service is fully restored

2. resolved Apr 14, 2026, 02:13 AM UTC

   The services are back up and running. Thank you for your patience while we worked to restore services.

Read the full incident report →

Started Apr 13, 2026, 02:26 AM UTC· resolved Apr 13, 2026, 02:43 AM UTC

1. investigating Apr 13, 2026, 02:26 AM UTC

   We are currently investigating an issue with the login and generate the access tokens

2. resolved Apr 13, 2026, 02:43 AM UTC

   Our team has fixed the connection issue. Users should now be able to log in successfully, and access token generation is functioning as expected. Thank you for your patience while we worked to restore access.

Read the full incident report →

Started Apr 08, 2026, 06:40 AM UTC· resolved Apr 08, 2026, 07:26 AM UTC

1. investigating Apr 08, 2026, 06:40 AM UTC

   We are currently investigating an issue with the database connection outage that occurred around 3:30 AEST.

2. identified Apr 08, 2026, 06:53 AM UTC

   Our team has determined that there is a connection issue with the database. The Go1 login service may be affected.

3. investigating Apr 08, 2026, 07:14 AM UTC

   Our team have fixed the connection issue. Users should be able to log in now after refreshing the page. We are monitoring the traffic, and it has started to decrease.

4. investigating Apr 08, 2026, 07:14 AM UTC

   Our team have fixed the connection issue. Users should be able to log in now after refreshing the page. We are monitoring the traffic, and it has started to decrease.

5. monitoring Apr 08, 2026, 07:16 AM UTC

   Our team have fixed the connection issue. Users should be able to log in now after refreshing the page. We are monitoring the traffic, and it has started to decrease.

6. resolved Apr 08, 2026, 07:26 AM UTC

   The database connection outage affecting multiple authentication and authorization services related to identity management has been resolved. We appreciate your patience and sincerely apologize for any inconvenience caused.

Read the full incident report →

Started Mar 16, 2026, 01:03 AM UTC· resolved Mar 16, 2026, 05:58 PM UTC

1. investigating Mar 16, 2026, 01:03 AM UTC

   We are currently investigating this issue.

2. identified Mar 16, 2026, 01:25 AM UTC

   We’ve identified the issue and the team is actively working on a solution. We’ll provide an update as soon as the fix is in place. Thank you for your patience.

3. monitoring Mar 16, 2026, 02:15 AM UTC

   A fix has been implemented, and we are monitoring the system to ensure full restoration. We will share further updates as soon as the service is confirmed stable. Thank you for your continued patience.

4. monitoring Mar 16, 2026, 04:34 AM UTC

   The enrollment services are currently operating at a slower pace than usual. We are continuing to monitor for any further issues.

5. monitoring Mar 16, 2026, 06:18 AM UTC

   We are continuing to monitor for any further issues.

6. resolved Mar 16, 2026, 05:58 PM UTC

   The issue with our enrollment service has been resolved. Assignments and enrollments are now working as expected—apologies for any inconvenience caused.

Read the full incident report →

Started Nov 18, 2025, 12:52 PM UTC· resolved Nov 18, 2025, 02:49 PM UTC

1. monitoring Nov 18, 2025, 12:52 PM UTC

   Our team is currently experiencing service disruptions due to an issue within the Cloudflare Global Network. We will continue to monitor the situation and provide updates as soon as the service is fully restored

2. monitoring Nov 18, 2025, 12:56 PM UTC

   We are continuing to monitor for any further issues.

3. monitoring Nov 18, 2025, 01:34 PM UTC

   The issue is still ongoing. Our team is continuously monitoring updates from Cloudflare's side, while they continue working on the fixes.

4. resolved Nov 18, 2025, 02:49 PM UTC

   Cloudflare has implemented a fix and we are seeing services recover. We will continue to monitor for updates and adjust the incident if we identify any outages or degraded services.

Read the full incident report →

Started Nov 17, 2025, 05:52 PM UTC· resolved Nov 17, 2025, 10:55 PM UTC

1. investigating Nov 17, 2025, 05:52 PM UTC

   We have identified sporadic issues with password notification delivery failing for direct users of Go1 attempting to reset their password manually. Our team is actively reviewing scope of impact and performance impact. Learners impacted may be unable to successfully reset their passwords at this time. If you need immediate support while we continue to investigate this issue, please reach out to Support.

2. resolved Nov 17, 2025, 10:55 PM UTC

   We are glad to inform that the issue has been resolved. Apologies for any inconvenience caused.

Read the full incident report →

Started Oct 15, 2025, 03:37 AM UTC· resolved Oct 15, 2025, 03:48 AM UTC

1. identified Oct 15, 2025, 03:37 AM UTC

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

2. resolved Oct 15, 2025, 03:48 AM UTC

   We are glad to inform that the issue has been resolved now, and the notifications should be functioning as expected. Apologies for any inconvenience caused.

Read the full incident report →

Started Oct 13, 2025, 12:53 AM UTC· resolved Oct 13, 2025, 04:04 AM UTC

1. investigating Oct 13, 2025, 12:53 AM UTC

   Our team is currently investigating an issue impacting notifications delivery for some portals. Some customers may experience delays in sending welcome emails to new users Other functionality remains operational. We will provide an update as soon as information is available.

2. monitoring Oct 13, 2025, 01:03 AM UTC

   A fix has been implemented and we're currently monitoring the results.

3. resolved Oct 13, 2025, 04:04 AM UTC

   We are glad to inform that the issue has been resolved. Apologies for any inconvenience caused.

Read the full incident report →

Started Oct 09, 2025, 09:15 PM UTC· resolved Oct 10, 2025, 02:58 AM UTC

1. investigating Oct 09, 2025, 09:15 PM UTC

   Our team is currently investigating an issue impacting notifications delivery for some portals. Other functionality remains operational. We will provide an update as soon as information is available.

2. investigating Oct 09, 2025, 10:13 PM UTC

   We continue to investigate this issue.

3. investigating Oct 09, 2025, 11:43 PM UTC

   We are continuing to investigate this issue.

4. monitoring Oct 10, 2025, 01:37 AM UTC

   A fix has been implemented and we're currently monitoring the results. We should start seeing the notification services back to normal as expected. Apologies for any inconvenience caused.

5. resolved Oct 10, 2025, 02:58 AM UTC

   We are glad to inform that the issue has been resolved now. Apologies for any inconvenience caused.

Read the full incident report →

Started Sep 22, 2025, 08:36 AM UTC· resolved Sep 22, 2025, 10:07 AM UTC

1. investigating Sep 22, 2025, 08:36 AM UTC

   Our team has identified an error causing delays with course creation and sharing, and we are actively investigating the issue.

2. investigating Sep 22, 2025, 08:36 AM UTC

   We are continuing to investigate this issue.

3. investigating Sep 22, 2025, 08:45 AM UTC

   We are continuing to investigate this issue.

4. monitoring Sep 22, 2025, 09:34 AM UTC

   We’ve redirected services to our primary database, and systems are beginning to stabilize. Our team is continuing to closely monitor performance.

5. resolved Sep 22, 2025, 10:07 AM UTC

   The issue impacting course creation and sharing has now been fully resolved. We apologize for any inconvenience this may have caused and appreciate your patience during the resolution process.

Read the full incident report →

Started Sep 18, 2025, 06:31 AM UTC· resolved Sep 18, 2025, 07:20 AM UTC

1. investigating Sep 18, 2025, 06:31 AM UTC

   Our team has identified an error impacting multiple accounts and is actively investigating 18 Sep 16:29PM AEST

2. monitoring Sep 18, 2025, 06:45 AM UTC

   Service to the Go1 Portal has been restored. All users should now have access, and we are continuing to closely monitor system performance. ( 18 Sep 16:35 PM AEST )

3. resolved Sep 18, 2025, 07:20 AM UTC

   A surge in traffic caused a denial of service on our gateways. We have fixed the cause, and our gateways are now operating normally. We will continue to monitor to ensure traffic levels remain stable.

Read the full incident report →

Started Sep 10, 2025, 01:29 AM UTC· resolved Sep 10, 2025, 05:43 AM UTC

1. identified Sep 10, 2025, 01:29 AM UTC

   Our team has identified the problem and is actively working on a fix.

2. identified Sep 10, 2025, 02:20 AM UTC

   Fix in progress - We are applying a fix across our catalog now and full service should be restored in 120 minutes. Further updates in 60 minutes

3. identified Sep 10, 2025, 03:29 AM UTC

   Fix in progress - We are continuing to apply fix, and we are already seeing content properly becoming available. The complete process might take a little longer time than expected. We will keep you updated.

4. resolved Sep 10, 2025, 05:43 AM UTC

   The fix has been implemented successfully, and the issue is resolved. We apologize for any inconvenience this may have caused and appreciate your patience during the resolution process.

Read the full incident report →

Started Aug 27, 2025, 05:07 AM UTC· resolved Aug 27, 2025, 09:23 AM UTC

1. investigating Aug 27, 2025, 05:07 AM UTC

   We are currently investigating an issue where some admins may experience delays or errors when loading or searching within the User Management page. Our engineering team is actively working to identify the cause and restore full functionality as soon as possible.

2. monitoring Aug 27, 2025, 06:20 AM UTC

   Some admins may experience delays or errors when using User Management, including user search in the UI and via the public API, due to high system load. A temporary timeout has been applied to improve performance, and we are monitoring the situation.

3. resolved Aug 27, 2025, 09:23 AM UTC

   Our team identified the root cause of the temporary disruption and implemented a fix. We apologize for any inconvenience this may have caused and appreciate your patience during the resolution process.

Read the full incident report →

Started Jul 29, 2025, 06:33 AM UTC· resolved Jul 29, 2025, 06:37 AM UTC

1. investigating Jul 29, 2025, 06:33 AM UTC

   We’re currently experiencing a service disruption preventing learners from accessing the Go1 Learn Portal. Our Go1 Engineering team is actively working to identify the root cause and implement a solution.

2. identified Jul 29, 2025, 06:37 AM UTC

   Our team has identified the problem and is actively working on a fix.

3. resolved Jul 29, 2025, 06:37 AM UTC

   We’re pleased to let you know that the issue has now been resolved. We apologize for any inconvenience this may have caused and appreciate your patience.

Read the full incident report →

Started Jul 24, 2025, 09:54 AM UTC· resolved Jul 24, 2025, 11:50 AM UTC

1. investigating Jul 24, 2025, 09:54 AM UTC

   We're currently experiencing a service disruption preventing some customers from changing user details, changing roles or activating and deactivating users. Our Go1 Engineering team is actively working to identify the root cause and implement a solution.

2. investigating Jul 24, 2025, 10:27 AM UTC

   We are continuing to investigate this issue.

3. identified Jul 24, 2025, 11:02 AM UTC

   Our team has identified the problem and is actively working on a fix.

4. resolved Jul 24, 2025, 11:50 AM UTC

   We’re pleased to let you know that the issue has now been resolved. The root cause was identified as a malfunction in the caching system, which has since been replaced. We apologize for any inconvenience this may have caused and appreciate your patience.

Read the full incident report →

Started Feb 04, 2025, 02:39 AM UTC· resolved Feb 04, 2025, 03:21 AM UTC

1. investigating Feb 04, 2025, 02:39 AM UTC

   We're experiencing issues around content not being able to load in Go1 player and are currently looking into the issue.

2. monitoring Feb 04, 2025, 02:54 AM UTC

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

3. resolved Feb 04, 2025, 03:21 AM UTC

   We are glad to inform that the issue has been resolved now. We found the cause of this temporary disruption and have fixed the root of the issue. Apologies for any inconvenience caused.

Read the full incident report →

Started Feb 03, 2025, 03:32 PM UTC· resolved Feb 04, 2025, 03:32 PM UTC

1. resolved Feb 05, 2025, 03:32 PM UTC

   On 5 February at 1:23 AM UTC, Go1's engineering team identified an issue via internal monitoring that prevented some learners from starting new content. The team immediately investigated to determine the root cause and resolve the issue. During the 37-minute period, learners attempting to start new content were stuck at the beginning of the process and may have seen an “Oops! An error occurred, please refresh and try again,” message.

2. postmortem Feb 05, 2025, 03:32 PM UTC

   **Incident Summary**` `**Start:** 5 February 2025 1:23 AM UTC` `**End:** 5 February 2025 2:00 AM UTC` ` **Impact:** Learners were temporarily unable to start new content on Go1` `On 5 February at 1:23 AM UTC, Go1's engineering team identified an issue via internal monitoring that prevented some learners from starting new content. The team immediately investigated to determine the root cause and resolve the issue.` ` During the 37-minute period, learners attempting to start new content were stuck at the beginning of the process and may have seen an _“Oops! An error occurred, please refresh and try again,”_ message.` ` **Root Cause**` `The incident stemmed from a configuration issue that impacted the ability for users to access content. Automated monitoring settings prevented early detection and updates to address it are underway. **Remedial Actions**` `The engineering team updated the configuration to resolve the issue, restoring the service at 2:00 AM UTC. Monitoring confirmed that all systems were functioning as expected.` ` **Preventative Actions**` `The team is enhancing health checks to improve detection of similar issues and prevent recurrence. A full incident retrospective will identify any additional improvements.` ` To stay informed about any future outages or bugs, we highly recommend subscribing to our [Go1 Status Page](https://status.go1.com/). By subscribing, you can choose to be updated via email, text, or Slack, allowing you to share real-time information with your team and learners.` ` Please reach out to your support team with any questions. Thank you for your patience.

Read the full incident report →

Started Jan 27, 2025, 07:03 PM UTC· resolved Jan 27, 2025, 08:57 PM UTC

1. investigating Jan 27, 2025, 07:03 PM UTC

   We are currently investigating this issue. The content for our courses is not loading. Preview features in Content Hub and Explore pages are also affected.

2. monitoring Jan 27, 2025, 07:44 PM UTC

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

3. resolved Jan 27, 2025, 08:57 PM UTC

   This incident has been resolved.

4. postmortem Jan 27, 2025, 10:36 PM UTC

   **Incident Summary** **Start:** 27 January 2025 PT 9:40 a.m. PST | 28 January 2025 4:40 a.m. AEDT **End:** 27 January 2025 PT 11:22 a.m. PST | 28 January 2025 6:22 a.m. AEDT **Impact:** Users temporarily saw a "_We couldn't load the content," or an, "Oops! An error occurred, please refresh and try again,"_ error message when attempting to access any content related feature.On 27 January at 9:40 a.m. PT \(28 January 4:40 a.m. AEDT\) an issue was identified by Go1's engineering team via internal monitoring. During the time the issue was active, ~20 users saw a _"We couldn't load the content," or an, "Oops! An error occurred, please refresh and try again,"_ error message when attempting to access any content related feature, i.e., previewing content, content sync, playlists, AI search, etc. ‌ **Root Cause** The engineering team identified the root cause as being an internal system process that was causing unexpected results. ‌ **Remedial Actions** The issue was resolved at 11:22 a.m. PST \(6:22 a.m. AEDT\) by disabling the internal system process that was causing the issue. The team monitored the results to ensure services were properly restored and the system was functioning as expected.**Preventative Actions** Comprehensive preventative measures will be identified upon completion of the incident retrospective.

Read the full incident report →