OpenSesame Outage History

OpenSesame experienced a service disruption where internal employee self-service user and account creation became unavailable, affecting the Simon Authoring Suite. The issue was identified and resolved within 45 minutes through implementation of a fix.

OpenSesame's AI functionality for creating slide voiceovers and generating quizzes in the Simon Authoring Suite failed to complete successfully for 1.2 hours. The issue affected users' ability to use AI-powered content creation features within the authoring tool. The incident was resolved after investigation and monitoring.

The OpenSesame Simon Course Translation service experienced a partial outage that prevented processing of text translations for courses and caption translations for assets. The Simon Authoring Suite was affected during this incident. The issue was resolved after 46 minutes of investigation and remediation work.

OpenSesame's CourseCloud service experienced a major incident where users were unable to launch courses. The issue affected the OpenSesame CourseCloud component for 15 minutes before being identified and resolved with a fix implementation.

OpenSesame's CourseCloud service experienced a major incident where users were unable to launch courses. The issue affected the OpenSesame CourseCloud component for 17 minutes before being resolved.

OpenSesame experienced an issue where xAPI completion statements were not being sent for direct integrations, causing learners' course completions to not register in their Learning Management Systems. The OpenSesame Course Delivery Platform was affected for 4 hours while the engineering team investigated and implemented a fix. The issue was resolved with all missed completion statements successfully sent to the affected LMS platforms.

The OpenSesame Course Delivery Platform experienced a major incident where learners could not launch e-learning courses, encountering error messages or blank screens when attempting to start courses. The issue affected the course player functionality for approximately 1 hour. The engineering team implemented a fix and monitored the system until the incident was fully resolved.