Historial de interrupciones de Clever

1. 22 de octubre de 2026 a las 14:40 UTCinvestigating

   Algunos de nuestros administradores están experimentando un problema en el que, al hacer clic en el enlace para descargar las insignias, las descargas se están equivocando.

2. 22 de octubre de 2026 a las 15:11 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 22 de octubre de 2026 a las 15:51 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

4. 22 de octubre de 2026 a las 16:14 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 21 de octubre de 2026 a las 17:35 UTCidentified

   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.

2. 21 de octubre de 2026 a las 17:53 UTCmonitoring

   Our website update is still in progress.

3. 22 de octubre de 2026 a las 2:14 UTCresolved

   This incident is resolved. We have completed the update to our main website.

1. 8 de octubre de 2026 a las 1:47 UTCresolved

   Entre las 5:08 y las 5:59 pm PST, algunos usuarios pueden haber sido incapaces de iniciar sesión en el Portal Clever o aplicaciones de lanzamiento. El servicio se ha recuperado, y lo estamos monitoreando. Si ve algún problema adicional, por favor contacte con nuestro equipo de soporte en support.clever.com.

Traducido automáticamente desde la actualización oficial del incidente.

1. 18 de septiembre de 2026 a las 16:43 UTCresolved

   Entre las 7:12 y las 8:53 AM PT de hoy, una tarea titulada "1 Aplicación esperándote" se mostró en error a los administradores de distrito que entraron en el tablero de mando de Clever durante esa ventana. La tarea hizo referencia a la solicitud pendiente de otro distrito y fue destinada para ese distrito solamente. Se ha eliminado. La tarea vinculada sólo a su propia página de Aplicaciones; no se compartieron, cambiaron o accedieron como resultado, y no se necesita ninguna acción. Si todavía aparece, refresca tu tablero y deberías verlo corregido. Nos disculpamos por la confusión.

Traducido automáticamente desde la actualización oficial del incidente.

1. 16 de septiembre de 2026 a las 11:24 UTCinvestigating

   Clever es consciente de una interrupción del servicio que afecta a Salesforce, una plataforma de terceros en la que confiamos para partes de nuestra gestión de casos de apoyo. Como resultado, puede experimentar retrasos en las actualizaciones de casos de apoyo, notificaciones de correo electrónico vinculadas a casos, o tiempos de respuesta más lentos al enviar nuevas solicitudes de soporte a través de canales afectados. Este número se origina con Salesforce y está fuera de nuestra infraestructura. Nuestro equipo está monitoreando activamente la situación y restaurará los flujos de trabajo de apoyo normales tan pronto como Salesforce resuelva la perturbación de su fin. Los servicios de Core Clever (sync, rostering, login) no se ven afectados por este incidente. Publicaremos actualizaciones aquí mientras aprendemos más. Gracias por su paciencia.

2. 16 de septiembre de 2026 a las 12:20 UTCidentified

   Salesforce ha publicado en su página de estado, https://status.salesforce.com/, que han identificado la cuestión y están trabajando para resolverla. No tenemos un plazo estimado en cuanto a cuándo será resuelto para Clever- pero estamos monitoreando su página de estado para los udpates. Publicaremos actualizaciones aquí mientras aprendemos más. Gracias por su paciencia.

3. 16 de septiembre de 2026 a las 17:46 UTCmonitoring

   Salesforce ha implementado una solución para la interrupción del servicio anterior. Todos los canales previamente afectados funcionan normalmente, y los tiempos de tramitación de casos de apoyo, notificaciones y respuesta han regresado a los niveles previstos. Seguiremos monitoreando a medida que Salesforce presente actualizaciones adicionales para evitar la recurrencia, y publicaremos de nuevo si algo cambia. Gracias por su paciencia durante todo este incidente.

4. 16 de septiembre de 2026 a las 23:43 UTCresolved

   Salesforce ha resuelto este incidente. Todos los canales previamente afectados funcionan normalmente, y los tiempos de tramitación de casos de apoyo, notificaciones y respuesta han regresado a los niveles previstos.

Traducido automáticamente desde la actualización oficial del incidente.

1. 27 de agosto de 2026 a las 14:18 UTCinvestigating

   Clever está actualmente investigando un problema donde los tiempos de sincronización en las páginas de aplicaciones conectadas se muestran inexactamente en el panel. Tan pronto como tengamos más información, proporcionaremos una actualización.

2. 27 de agosto de 2026 a las 14:47 UTCidentified

   Se ha determinado la cuestión y se está aplicando una solución.

3. 27 de agosto de 2026 a las 14:47 UTCidentified

   Seguimos trabajando en una solución para esta cuestión.

4. 27 de agosto de 2026 a las 15:36 UTCmonitoring

   Se ha aplicado una solución y estamos monitoreando los resultados.

5. 27 de agosto de 2026 a las 15:46 UTCresolved

   Este incidente ha sido resuelto.

Traducido automáticamente desde la actualización oficial del incidente.

1. 14 de agosto de 2026 a las 17:09 UTCinvestigating

   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.

2. 14 de agosto de 2026 a las 21:15 UTCmonitoring

   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

3. 18 de agosto de 2026 a las 13:59 UTCresolved

   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.

1. 13 de agosto de 2026 a las 16:23 UTCinvestigating

   Somos conscientes de un problema que afecta actualmente a algunos sincronizados de Aeries API y estamos investigando activamente sobre nuestro fin. Publicaremos más información lo antes posible. Nos disculpamos por cualquier inconveniente que esto pueda causar.

2. 13 de agosto de 2026 a las 21:38 UTCresolved

   The sync issue with some Aeries API syncs has been resolved. We thank you for your patience.

Traducido automáticamente desde la actualización oficial del incidente.

1. 5 de agosto de 2026 a las 18:50 UTCinvestigating

   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.

2. 5 de agosto de 2026 a las 20:48 UTCresolved

   This incident has been resolved.

1. 22 de junio de 2026 a las 19:55 UTCidentified

   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.

2. 22 de junio de 2026 a las 22:20 UTCresolved

   This incident has been resolved.

1. 1 de mayo de 2026 a las 17:48 UTCidentified

   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.

2. 1 de mayo de 2026 a las 19:09 UTCresolved

   This incident has been resolved.

1. 29 de abril de 2026 a las 12:21 UTCidentified

   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.

2. 29 de abril de 2026 a las 18:50 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 30 de abril de 2026 a las 15:35 UTCresolved

   This incident has been resolved.

1. 15 de abril de 2026 a las 18:18 UTCresolved

   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.

1. 26 de marzo de 2026 a las 15:30 UTCinvestigating

   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.

2. 26 de marzo de 2026 a las 19:04 UTCmonitoring

   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!

3. 27 de marzo de 2026 a las 16:21 UTCresolved

   The incident regarding intermittent login failures has been resolved. -Thank you

1. 18 de marzo de 2026 a las 14:51 UTCinvestigating

   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.

2. 18 de marzo de 2026 a las 17:00 UTCresolved

   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.

1. 10 de febrero de 2026 a las 20:47 UTCinvestigating

   Clever is currently investigating an issue where clever.com/login is inaccessible. As soon as we have more information, we will provide an update.

2. 10 de febrero de 2026 a las 21:25 UTCidentified

   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.

3. 10 de febrero de 2026 a las 22:58 UTCresolved

   Amazon AWS has resolved this issue, and everything is back to normal.

1. 10 de febrero de 2026 a las 17:23 UTCinvestigating

   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.

2. 10 de febrero de 2026 a las 20:15 UTCresolved

   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

1. 16 de enero de 2026 a las 22:19 UTCidentified

   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.

2. 17 de enero de 2026 a las 4:12 UTCmonitoring

   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.

3. 20 de enero de 2026 a las 19:33 UTCresolved

   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.

1. 14 de enero de 2026 a las 16:25 UTCinvestigating

   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.

2. 15 de enero de 2026 a las 16:09 UTCinvestigating

   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.

3. 16 de enero de 2026 a las 0:40 UTCresolved

   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/

1. 7 de enero de 2026 a las 15:59 UTCinvestigating

   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

2. 7 de enero de 2026 a las 19:13 UTCmonitoring

   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,

3. 8 de enero de 2026 a las 14:21 UTCresolved

   The login issue for some districts has been resolved. We apologize for any inconvenience this may have caused.