Go1 Outage History
14 incidents recorded over the last 365 days, 13 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Go1 Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| Sep 15, 2026 | Go1 portal login and Authentication issuesAuthentication 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… | 7h 24m | Resolved |
| Jul 30, 2026 | Errors in Go1 Learn People TabThe 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. | 37 min | Resolved |
| Jun 1, 2026 | Go1 Content completion issuesThis 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… | 526h 0m | Resolved |
| May 29, 2026 | Go1 Content playback issueWe’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… | 6h 52m | Resolved |
| May 26, 2026 | Scheduled MaintenanceThis incident has been resolved. Apologies for any inconvenience caused. | 39 min | Resolved |
| May 25, 2026 | Scheduled System MaintenanceScheduled maintenance has been completed. Services have been restored and we are continuing to monitor performance. Thank you for your patience. | 2h 0m | Scheduled |
| May 11, 2026 | Go1 portal login ( SSO error )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… | 41 min | Resolved |
| May 8, 2026 | Go1 portal login and Aunthentication issuesWe 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. | 1h 45m | Resolved |
| Apr 14, 2026 | Go1 service disruptionsThe services are back up and running. Thank you for your patience while we worked to restore services. | 1h 12m | Resolved |
| Apr 13, 2026 | Go1 Portal access and a partner access token issueOur 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. | 17 min | Resolved |
| Apr 8, 2026 | Go1 Authentication Server experienced a brief connection outageThe 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… | 46 min | Resolved |
| Mar 16, 2026 | Enrollment Service is down -> Enrollments not reflecting in reports and assignments are failingThe issue with our enrollment service has been resolved. Assignments and enrollments are now working as expected—apologies for any inconvenience caused. | 16h 55m | Resolved |
| Nov 18, 2025 | Go1 Portal Access IssueCloudflare 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. | 1h 57m | Resolved |
| Nov 17, 2025 | Password Reset Notification Issue – Go1 LearnersWe are glad to inform that the issue has been resolved. Apologies for any inconvenience caused. | 5h 3m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Go1 incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Go1 Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Go1 acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Go1 outage in this window ran 21d 22h, against a mean recovery of 1d 16h. If you depend on Go1 in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.