How we know: the official Go1 status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works
Go1 Component Status
The main Go1 systems on this page. All 3 are operational right now.
3operational
API
Operational
Go1
Operational
Third Party LMS Integrations
Operational
Component statuses may change independently during partial outages.
Recent Go1 Outages & Incidents
Incident history from the official Go1 status page, including resolution updates.
Uptime history4 days observed
Aug 8100.00% averageAug 11
Errors in Go1 Learn People TabResolved Jul 30, 2026 · 37 minResolved
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.
---
[2026-07-30T23:19:46.033+10:00] (identified) 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.
---
[2026-07-30T22:57:11.665+10:00] (identified) 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.
Go1 Content completion issuesResolved Jun 1, 2026 · 526h 0mResolved
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.
---
[2026-06-16T09:57:03.615+10:00] (monitoring) 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.
---
[2026-06-12T09:22:18.924+10:00] (monitoring) 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.
---
[2026-06-11T08:28:57.409+10:00] (monitoring) 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.
---
[2026-06-10T09:20:25.289+10:00] (monitoring) 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.
---
[2026-06-09T08:32:20.369+10:00] (monitoring) 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.
---
[2026-06-08T07:54:57.214+10:00] (monitoring) 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.
---
[2026-06-03T14:16:17.541+10:00] (monitoring) 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.
---
[2026-06-03T14:08:55.503+10:00] (monitoring) 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.
---
[2026-06-02T14:10:47.896+10:00] (identified) 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.
---
[2026-06-02T04:44:14.914+10:00] (identified) 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.
---
[2026-06-01T15:27:41.235+10:00] (identified) We are continuing to work on a fix. Apologies for any inconvenience caused.
---
[2026-06-01T13:39:08.538+10:00] (identified) We are continuing to work on a fix.
---
[2026-06-01T12:19:10.155+10:00] (identified) The issue has been identified, and team is working towards the fix.
---
[2026-06-01T10:25:46.578+10:00] (investigating) 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.
Go1 Content playback issueResolved May 29, 2026 · 6h 52mResolved
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.
---
[2026-05-29T19:43:38.143+10:00] (identified) The issue has identified and mitigation efforts are currently underway.
---
[2026-05-29T19:42:21.770+10:00] (identified) 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.
---
[2026-05-29T15:46:37.120+10:00] (investigating) We are currently investigating an issue where some content may intermittently fail to launch or play in the Go1 player.
Live Go1 Outage Reports
Problems reported by engineers using Go1. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.
Reports, last 24 hours0 total
24h agoNothing reportednow
No Go1 problems reported yet.
Something wrong with Go1 on your end?
Reports are anonymous, take about ten seconds, and help the next engineer who checks.
About Go1
Go1 exposes 3 monitored components on its status page at status.go1.com — Go1, API and Third Party LMS Integrations among them. Follow Go1 downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.
Over the past 30 days, PulsAPI has measured Go1 uptime at 100.00%. Response times, incident history, and SLA tracking for Go1 are available on the PulsAPI dashboard.
Go1 Status FAQ
Is Go1 down right now?
PulsAPI checks Go1 every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Go1 status feed and refreshes automatically, so you are not looking at a stale cached answer.
What should I do if Go1 is not working?
Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Go1 recovers.
How do I check Go1 uptime history?
PulsAPI tracks Go1 uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Go1.
How fast does PulsAPI detect Go1 outages?
PulsAPI polls the official Go1 status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.
Does PulsAPI track individual Go1 components?
Yes. PulsAPI monitors 3 individual Go1 components, so you can see which service or region is affected instead of a generic "service degraded" banner.
Can I get alerts when Go1 goes down?
Yes. Create a PulsAPI account and subscribe to Go1. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Go1 status changes.
How do I report an issue with Go1 to the community?
Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Go1 problems early. Official status pages often lag real incidents by 10 to 20 minutes.
Is there a free way to monitor Go1?
Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Go1 alongside up to 9 other services at pulsapi.com/signup.
Track Go1 with the rest of your stack
Monitor 2461+ cloud services from one dashboard and get alerts when Go1 status changes.