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 Go1On 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. 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.