60 recorded Clever incidents since September 2024, with official updates, affected components, duration and resolution information.
Some of our Admins are currently experiencing an issue where, when clicking on the link to download badges, the downloads are erroring out.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Clever is in the process of updating our website. You may notice some minor changes or possible errors on our home page during this update, but it will not impact our customers' ability to login or use our products.
Our website update is still in progress.
This incident is resolved. We have completed the update to our main website.
Between 5:08 and 5:59 pm PST, some users may have been unable to log in to the Clever Portal or launch apps. Service has recovered, and we’re monitoring it. If you see any additional issues, please reach out to our support team at support.clever.com.
Between 7:12 and 8:53 AM PT today, a task titled "1 Application waiting on you" was shown in error to district administrators who logged in to the Clever dashboard during that window. The task referenced another district's pending application invite and was intended for that district only. It has been removed. The task linked only to your own Applications page; no data was shared, changed, or accessed as a result, and no action is needed. If it still appears, refresh your dashboard and you should see it corrected. We apologize for the confusion.
Clever is aware of a service disruption affecting Salesforce, a third-party platform we rely on for parts of our support case management. As a result, you may experience delays in support case updates, email notifications tied to cases, or slower response times when submitting new support requests through affected channels. This issue originates with Salesforce and is outside of our infrastructure. Our team is actively monitoring the situation and will restore normal support workflows as soon as Salesforce resolves the disruption on their end. Core Clever services (sync, rostering, login) are not affected by this incident. We'll post updates here as we learn more. Thank you for your patience.
Salesforce has posted on their status page, https://status.salesforce.com/, that they have identified the issue and are working on resolving it. We don't have an estimated time frame as to when it will be resolved for Clever- but we are monitoring their status page for udpates. We'll post updates here as we learn more. Thank you for your patience.
Salesforce has deployed a fix for the earlier service disruption. All previously affected channels are now functioning normally, and support case handling, notifications, and response times have returned to expected levels. We'll continue monitoring as Salesforce rolls out additional updates to prevent recurrence, and will post again if anything changes. Thank you for your patience throughout this incident.
Salesforce has resolved this incident. All previously affected channels are now functioning normally, and support case handling, notifications, and response times have returned to expected levels.
Clever is currently investigating an issue where sync times on connected app pages are displaying inaccurately in the dashboard. As soon as we have more information, we will provide an update.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are aware of an issue currently affecting some Aeries API syncs and are actively investigating on our end. We will post more information as soon as possible. We apologize for any inconvenience this may be causing.
Aeries API syncs that were previously showing a sync error are now syncing to Clever. We will continue to monitor the situation. If you have questions, please submit a ticket to Clever's Support Team at support.clever.com Thank you
Aeries API syncs that were previously showing a sync error are now syncing to Clever. This issue has now been resolved and we appreciate your patience.
We’re aware of an issue currently affecting some Aeries API syncs and are actively investigating on our end. We will post more information as soon as possible. We apologize for any inconvenience this may be causing.
The sync issue with some Aeries API syncs has been resolved. We thank you for your patience.
We have identified an issue that is preventing some students from being able to access their Teacher Pages on the Clever Portal. Students and teachers are still able to access applications from their district Portal pages. We’re investigating the issue and will provide status updates.
This incident has been resolved.
We have identified an error causing Canvas IDP logins to fail. We are working on a resolution and will provide an update at that time. We apologize for any inconvenience this may be causing.
This incident has been resolved.
We have identified an error causing Canvas IDP logins to fail (Invalid or Unknown Client Error). We are working on a resolution and will provide an update at that time. We apologize for any inconvenience this may be causing.
This incident has been resolved.
We have identified an error causing custom login instructions and hints to disappear from the Clever login page. We are working on a resolution and will provide an update once these labels are restored. Action Required: If your users see a generic "Account" login page instead of your typical provider (Google, Microsoft Entra, AD, etc.), please update the SAML Authentication setting in your dashboard to identify your provider. For further assistance, please contact support.clever.com.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
Users may have experienced login issues to the Clever Portal today, April 15th, around 1:40pm ET/ 10:40am PT. This issue was resolved and everything is back to normal. If you see any additional issues, please contact Clever Support through our Help Center: support.clever.com.
Clever is currently experiencing intermittent login failures with an unknown cause. Our Engineering team is currently investigating the issue and we will update this page as soon as possible. We apologize for any inconvenience this may be causing.
The intermittent login failures have stopped and our team is still investigating the root cause of the issue. If you are still experiencing login issues, please contact our support team at support.clever.com. Thank you!
The incident regarding intermittent login failures has been resolved. -Thank you
There is a sync issue for some districts on the Skyward Selenium sync that is preventing syncs from being completed. At this time we are investigating the issue and will provide regular status updates. We apologize for the inconvenience this may cause.
Our Engineering team was able to identify and resolve the issue regarding Skyward Selenium syncs failing for some districts. Those impacted districts should see those previously failed syncs run. For any further questions regarding your impacted sync, please contact our Support Team at support.clever.com Thank you and we apologize again for any inconvenience this may have caused.
Clever is currently investigating an issue where clever.com/login is inaccessible. As soon as we have more information, we will provide an update.
Amazon AWS, a service that works with Clever, is experiencing a issue that is preventing users from being able to log in to Clever. We are monitoring the issue and will provide status updates as they become available.
Amazon AWS has resolved this issue, and everything is back to normal.
Clever is currently investigating an issue where the device camera is not opening when users are attempting to log in to Clever with a Badge on Windows devices. As soon as we have more information, we will provide an update.
This issue has been resolved. Users should now be able to use Badges to log in on Windows devices. For all other concerns, please reach out to our support team at support.clever.com
Some users on the new Clever iOS app are experiencing issues. For districts experiencing an issue where users had to enter their district information and login again after returning directly to the Clever app from a resource, this has been resolved as of 3:30pm PDT 1/15. If your district is still experiencing this, reach out to Clever Support at support.clever.com. For districts experiencing a login loop issue requiring users login multiple times, Clever has fixed the issue in the latest Clever iOS app, v6.0.8, and estimate it to be available as an update on Apple by early next week. When this update is available, you can follow these instructions to update the app: https://support.clever.com/s/articles/360024746971?language=en_US For all other issues, please contact Clever Support through our Help Center: support.clever.com.
Some users on the new Clever iOS app are experiencing issues. For districts experiencing an issue where users had to enter their district information and login again after returning directly to the Clever app from a resource, this has been resolved as of 3:30pm PDT 1/15. If your district is still experiencing this, reach out to Clever Support at support.clever.com. For districts experiencing a login loop issue requiring users login multiple times, Clever has fixed the issue in the latest Clever iOS app, v6.0.8, and this update is available to download in the Apple App Store. Districts can follow these instructions to update the app: https://support.clever.com/s/articles/360024746971?language=en_US For all other issues, please contact Clever Support through our Help Center: support.clever.com.
This incident has been resolved. For districts experiencing an issue where users had to enter their district information and login again after returning directly to the Clever app from a resource, this has been resolved as of 3:30pm PDT 1/15. If your district is still experiencing this, reach out to Clever Support at support.clever.com. For districts experiencing a login loop issue requiring users login multiple times, Clever has fixed the issue in the latest Clever iOS app, v6.0.8, and this update is available to download in the Apple App Store. Districts can follow these instructions to update the app: https://support.clever.com/s/articles/360024746971?language=en_US For all other issues, please contact Clever Support through our Help Center: support.clever.com.
Clever is seeing some SAML login failures and is investigating the root cause, including whether there is any relation to ADFS as the IdP and outdated certificates. Please contact support at support.clever.com if you are experiencing widespread login issues across your district so our Engineering team can investigate further. We will provide updates as our team continues to make progress on this issue.
Clever is continuing to see some districts with SAML SSO display login failures with "Login with ADFS". We are still investigating the root cause. Please contact support at support.clever.com if your district is configured to use ADFS with SAML logins and sees this error message, "No success code received from your SAML server", in your Access Logs. We will provide updates as our team continues to make progress on this issue.
This incident has been resolved. For troubleshooting expired SAML certificates at your district, please see our Help Center article: https://support.clever.com/hc/s/articles/000001736?language=en_US For any further issues, reach out to Clever Support at https://support.clever.com/
Clever is currently investigating an issue that is causing some districts to see an error message when users are trying to log into Clever. As soon as we have more information, we will update this status page. We apologize for the inconvenience. Thank you
Our Engineering Department has implemented a fix and it still closely monitoring the situation. For questions or concerns, please contact Clever Support at support.clever.com. Thank you,
The login issue for some districts has been resolved. We apologize for any inconvenience this may have caused.
