Störungsverlauf von Go1

1. 15. September 2026 um 16:10 UTCinvestigating

   Wir haben intermittierende Probleme mit der Anmeldung zum Go1-System. Wir untersuchen derzeit die Probleme auf unserer Plattform.

2. 15. September 2026 um 16:11 UTCinvestigating

   Wir werden dieses Problem weiter untersuchen.

3. 15. September 2026 um 19:07 UTCmonitoring

   Anmelde- und Authentifizierungsdienste sind stabil, während sie weiterhin auf gemeldete Fehler überwacht werden.

4. 15. September 2026 um 23:35 UTCresolved

   Authentifizierungsdienste sind stabil geblieben und Benutzer können sich normal anmelden. Wir haben festgestellt, dass ein hochvolumiger geplanter Integrationsprozess einen plötzlichen Anstieg der Login-bezogenen Hintergrundupdates verursacht. Dies belastete die unterstützenden Dienste unerwartet und führte bei einigen Kunden zu intermittierenden Anmeldefehlern. Wir implementieren Verbesserungen, um diese nicht kritischen Updates getrennt vom Login-Flow zu verarbeiten. Dadurch wird sichergestellt, dass Hintergrundverarbeitungsprobleme die Benutzer nicht daran hindern, auf Go1 zuzugreifen. Wir entschuldigen uns für die Störung und schätzen Ihre Geduld, während wir diesen Vorfall untersucht und gelöst haben.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 30. Juli 2026 um 12:57 UTCidentified

   Wir haben festgestellt, dass bei einigen Benutzern ein allgemeiner Fehler in Go1 Learn auftritt, wenn Sie einen Benutzer erstellen oder Benutzerdetails auf der Registerkarte Personen anzeigen. Benutzermanagement-Workflows können betroffen sein. Wir arbeiten daran, die normale Funktionalität wiederherzustellen.

2. 30. Juli 2026 um 13:19 UTCidentified

   Wir haben die Ursache eines Problems identifiziert, das die Benutzerverwaltung im Go1 Learn People-Tab beeinflusst. Einige Administratoren können beim Erstellen eines Benutzers oder beim Anzeigen von Benutzerdetails auf einen generischen Fehler stoßen. Ein Fix wird bereitgestellt. Wir werden ein weiteres Update bereitstellen, sobald die Bereitstellung abgeschlossen ist und der Dienst validiert wurde.

3. 30. Juli 2026 um 13:34 UTCresolved

   Das Problem mit der Profilseite, das einige Kundenportale betrifft, ist nun behoben. Wir haben bestätigt, dass Profilzugriff und Benutzererstellung auf den betroffenen Portalen wieder funktionieren, und wir sehen den früheren Fehler dort nicht mehr.

Automatisch aus der offiziellen Störungsmeldung übersetzt.

1. 1. Juni 2026 um 00:25 UTCinvestigating

   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. 1. Juni 2026 um 02:19 UTCidentified

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

3. 1. Juni 2026 um 03:39 UTCidentified

   We are continuing to work on a fix.

4. 1. Juni 2026 um 05:27 UTCidentified

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

5. 1. Juni 2026 um 18:44 UTCidentified

   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. 2. Juni 2026 um 04:10 UTCidentified

   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. 3. Juni 2026 um 04:08 UTCmonitoring

   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. 3. Juni 2026 um 04:16 UTCmonitoring

   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. 7. Juni 2026 um 21:54 UTCmonitoring

   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. 8. Juni 2026 um 22:32 UTCmonitoring

    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. 9. Juni 2026 um 23:20 UTCmonitoring

    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. 10. Juni 2026 um 22:28 UTCmonitoring

    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. 11. Juni 2026 um 23:22 UTCmonitoring

    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. 15. Juni 2026 um 23:57 UTCmonitoring

    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. 22. Juni 2026 um 22:26 UTCresolved

    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.

1. 29. Mai 2026 um 05:46 UTCinvestigating

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

2. 29. Mai 2026 um 09:42 UTCidentified

   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. 29. Mai 2026 um 09:43 UTCidentified

   The issue has identified and mitigation efforts are currently underway.

4. 29. Mai 2026 um 12:39 UTCresolved

   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.

1. 26. Mai 2026 um 01:52 UTCinvestigating

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

2. 26. Mai 2026 um 02:32 UTCresolved

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

1. 11. Mai 2026 um 12:51 UTCidentified

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

2. 11. Mai 2026 um 13:00 UTCidentified

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

3. 11. Mai 2026 um 13:32 UTCresolved

   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.

1. 8. Mai 2026 um 03:39 UTCinvestigating

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

2. 8. Mai 2026 um 03:41 UTCidentified

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

3. 8. Mai 2026 um 03:55 UTCmonitoring

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

4. 8. Mai 2026 um 05:12 UTCmonitoring

   We are continuing to monitor for any further issues.

5. 8. Mai 2026 um 05:24 UTCresolved

   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.

1. 14. April 2026 um 01:01 UTCmonitoring

   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. 14. April 2026 um 02:13 UTCresolved

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

1. 13. April 2026 um 02:26 UTCinvestigating

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

2. 13. April 2026 um 02:43 UTCresolved

   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.

1. 8. April 2026 um 06:40 UTCinvestigating

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

2. 8. April 2026 um 06:53 UTCidentified

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

3. 8. April 2026 um 07:14 UTCinvestigating

   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. 8. April 2026 um 07:16 UTCmonitoring

   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. 8. April 2026 um 07:26 UTCresolved

   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.

1. 16. März 2026 um 01:03 UTCinvestigating

   We are currently investigating this issue.

2. 16. März 2026 um 01:25 UTCidentified

   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. 16. März 2026 um 02:15 UTCmonitoring

   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. 16. März 2026 um 04:34 UTCmonitoring

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

5. 16. März 2026 um 06:18 UTCmonitoring

   We are continuing to monitor for any further issues.

6. 16. März 2026 um 17:58 UTCresolved

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

1. 18. November 2025 um 12:52 UTCmonitoring

   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. 18. November 2025 um 12:56 UTCmonitoring

   We are continuing to monitor for any further issues.

3. 18. November 2025 um 13:34 UTCmonitoring

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

4. 18. November 2025 um 14:49 UTCresolved

   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.

1. 17. November 2025 um 17:52 UTCinvestigating

   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. 17. November 2025 um 22:55 UTCresolved

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

1. 15. Oktober 2025 um 03:37 UTCidentified

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

2. 15. Oktober 2025 um 03:48 UTCresolved

   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.

1. 13. Oktober 2025 um 00:53 UTCinvestigating

   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. 13. Oktober 2025 um 01:03 UTCmonitoring

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

3. 13. Oktober 2025 um 04:04 UTCresolved

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

1. 9. Oktober 2025 um 21:15 UTCinvestigating

   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. 9. Oktober 2025 um 22:13 UTCinvestigating

   We continue to investigate this issue.

3. 9. Oktober 2025 um 23:43 UTCinvestigating

   We are continuing to investigate this issue.

4. 10. Oktober 2025 um 01:37 UTCmonitoring

   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. 10. Oktober 2025 um 02:58 UTCresolved

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

1. 22. September 2025 um 08:36 UTCinvestigating

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

2. 22. September 2025 um 08:45 UTCinvestigating

   We are continuing to investigate this issue.

3. 22. September 2025 um 09:34 UTCmonitoring

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

4. 22. September 2025 um 10:07 UTCresolved

   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.

1. 18. September 2025 um 06:31 UTCinvestigating

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

2. 18. September 2025 um 06:45 UTCmonitoring

   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. 18. September 2025 um 07:20 UTCresolved

   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.

1. 10. September 2025 um 01:29 UTCidentified

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

2. 10. September 2025 um 02:20 UTCidentified

   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. 10. September 2025 um 03:29 UTCidentified

   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. 10. September 2025 um 05:43 UTCresolved

   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.

1. 27. August 2025 um 05:07 UTCinvestigating

   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. 27. August 2025 um 06:20 UTCmonitoring

   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. 27. August 2025 um 09:23 UTCresolved

   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.