48 Lexia incidents · Oktober 2020 — official updates, affected components, duration and resolution details.
We have discovered an issue with our program, Core5. We are working to identify the issue and resolve as soon as possible. We apologize for any inconvenience this might cause.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have discovered an issue with our LETRS program. We are working to identify the issue and resolve as soon as possible. We apologize for any inconvenience this might cause.
A patch has been applied resolving customer-impacting issues. Development teams continue ongoing review to ensure continued stability.
Development teams continue ongoing review to ensure continued stability.
This incident has been resolved.
Anticipated resolution with scheduled maintenance tonight, Friday 2/6.
This issue have been resolved.
Lexia Academy is currently unavailable, and we are investigating the cause. Lexia Community and the Help Center are not affected. We apologize for the inconvenience and thank you for your patience!
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently working on resolving errors appearing in the community. We apologize for any inconvenience, and thank you for your patience!
The issue has been resolved! Users should no longer encounter errors while working in Lexia Community.
There is required maintenance taking place on the phone system that may cause issues when trying to call. We recommend going to the Help Center to contact Support if you experience any issues: https://help.lexialearning.com/s/contact
The phone system maintenance has been completed. Calls should be processed as expected. Thank you for your patience!
We have discovered an issue with our programs, Core5 and myLexia. We are working to identify the issue and resolve as soon as possible. We apologize for any inconvenience this might cause.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an issue with PowerUp students' dashboards showing last week's usage/units gained. We apologize for the inconvenience and thank you for your patience! We will update you once we know more about the root cause.
This incident has been resolved.
LETRS and Lexia Aspire are experiencing an outage. We are actively investigating.
This incident has been resolved.
Users may experience interruptions or error screens when trying to access our products. We apologize for the inconvenience and thank you for your patience! We are currently investigating this issue and will update once we know more about the root cause.
This incident has been resolved.
We are actively investigating this issue and will provide updates soon. Current issue description: Upon clicking on PowerUp from the Clever iOS app, the user receives an error message. Workaround: The user should instead navigate to the Lexia PowerUp product app and click the "Login with Clever" button
We are continuing to investigate this issue.
This incident has been resolved.
We are currently experiencing an issue that may be preventing students from accessing our PowerUp program. We are working to identify the issue and resolve it as soon as possible. We apologize for any inconvenience this might cause.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
There is currently an issue with PowerUp displaying students’ usage data on the PowerUp student homepage. All usage is correct and up to date in myLexia. We are working to resolve the issue quickly. We apologize for any inconvenience this might cause.
This incident has been resolved.
Some Clever rostered users (staff and students) are not being processed overnight, which subsequently affects access to all Lexia products for those users. We are actively investigating this issue and will provide an update as soon as possible.
Clever syncs are running successfully now, but we are still monitoring to ensure everything is processed smoothly.
This incident has been resolved.
Students and staff may experience a disruption when accessing Core5, PowerUp, Lexia English, and the myLexia platform via Classlink Single Sign On. We are actively investigating the issue and will provide an update when a resolution and timeline is defined. Thank you for your patience while this issue is being resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are actively working on a fix for an issue where students are unable to log in successfully when using the Clever iOS App to access Core5, PowerUp, and Lexia English via the Clever dashboard. As a workaround, students can go to the Core5, PowerUp, or Lexia English App and, from the program login page, click the "Login with Clever" button to log in using their Clever credentials (badges do not work). We apologize for any inconvenience this might cause.
We are continuing to work on a fix for this issue.
The student login issue for our Core5 users using the Clever iOS app has now been resolved. Core5 users are now able to login to Core5 via the Clever dashboard or Clever badge. We are still working on a fix for PowerUp and Lexia English.
A fix has been implemented, and we are monitoring results.
This incident has been resolved!
We have discovered an issue with our programs, LETRS and Lexia Aspire. We are working to identify the issue and resolve it as soon as possible. We apologize for any inconvenience this might cause.
We are continuing to investigate this issue.
This incident has been resolved.
We are currently investigating an issue that is affecting students and staff that log in through Classlink SSO.
This incident has been resolved.
We have discovered an issue with logging into Lexia Academy. We are working to identify and resolve the issue as soon as possible. We apologize for any inconvenience this might cause.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.