Historial de interrupciones de Vitalsource

1. August 26, 2026 at 4:16 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a Bookshelf Online.

2. August 26, 2026 at 4:24 PM UTCmonitoring

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

3. August 26, 2026 at 4:25 PM UTCmonitoring

   Continuamos monitoreando cualquier otro problema.

4. August 26, 2026 at 4:30 PM UTCresolved

   Este incidente ha sido resuelto.

5. August 26, 2026 at 5:31 PM UTCpostmortem

   El martes 25 de agosto, entre aproximadamente 1:50 y 2:00 PM ET, y de nuevo brevemente alrededor de las 2:45 PM ET, algunos usuarios encontraron errores, cargas lentas de página o dificultad para abrir libros en Bookshelf Online. Una perturbación similar ocurrió el miércoles 26 de agosto, entre aproximadamente 12:06 PM y 12:17 PM ET. Algunos usuarios también experimentaron problemas de registro intermitente durante estas ventanas. La causa fue una dependencia interna de servicios que se hizo inestable y dejó de aceptar nuevas solicitudes. Otras partes de la plataforma, incluida la entrega de material de curso a través de integraciones de LMS y comercio electrónico, no se vieron afectadas. Hemos identificado el desencadenante probable para la recurrencia del miércoles, están validando una solución, y han endurecido este componente contra la recurrencia. Estamos monitoreando de cerca a través del resto del período de inicio del término.

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

1. August 25, 2026 at 6:05 PM UTCinvestigating

   Actualmente estamos investigando un problema que afecta a Bookshelf Online.

2. August 25, 2026 at 6:27 PM UTCmonitoring

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

3. August 25, 2026 at 6:40 PM UTCresolved

   Este incidente ha sido resuelto.

4. August 26, 2026 at 5:32 PM UTCpostmortem

   El martes 25 de agosto, entre aproximadamente 1:50 y 2:00 PM ET, y de nuevo brevemente alrededor de las 2:45 PM ET, algunos usuarios encontraron errores, cargas lentas de página o dificultad para abrir libros en Bookshelf Online. Una perturbación similar ocurrió el miércoles 26 de agosto, entre aproximadamente 12:06 PM y 12:17 PM ET. Algunos usuarios también experimentaron problemas de registro intermitente durante estas ventanas. La causa fue una dependencia interna de servicios que se hizo inestable y dejó de aceptar nuevas solicitudes. Otras partes de la plataforma, incluida la entrega de material de curso a través de integraciones de LMS y comercio electrónico, no se vieron afectadas. Hemos identificado el desencadenante probable para la recurrencia del miércoles, están validando una solución, y han endurecido este componente contra la recurrencia. Estamos monitoreando de cerca a través del resto del período de inicio del término.

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

1. August 20, 2026 at 2:26 PM UTCinvestigating

   Actualmente estamos investigando esta cuestión.

2. August 20, 2026 at 2:50 PM UTCmonitoring

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

3. August 20, 2026 at 2:57 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. August 5, 2026 at 2:14 PM UTCresolved

   A networking issue caused an outage of Bookshelf Online from approximately 9:05 to 9:15 AM ET. Service has been fully restored.

1. August 4, 2026 at 10:29 PM UTCidentified

   Section history tracking will be temporarily unavailable for ~24 hours. Collect remains fully functional.

2. August 5, 2026 at 4:38 PM UTCresolved

   All systems operational.

1. July 20, 2026 at 8:16 PM UTCinvestigating

   Actualmente estamos experimentando una degradación del servicio. Estamos investigando.

2. July 20, 2026 at 8:28 PM UTCinvestigating

   Seguimos investigando esta cuestión.

3. July 20, 2026 at 9:12 PM UTCmonitoring

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

4. July 20, 2026 at 11:31 PM UTCresolved

   Este incidente ha sido resuelto.

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

1. July 7, 2026 at 10:41 PM UTCinvestigating

   TextbookX está experimentando problemas intermitentes. El equipo está investigando.

2. July 7, 2026 at 11:15 PM UTCidentified

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

3. July 7, 2026 at 11:20 PM UTCresolved

   El incidente se ha resuelto.

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

1. June 26, 2026 at 9:12 AM UTCinvestigating

   Actualmente estamos experimentando una degradación del servicio. Estamos investigando.

2. June 26, 2026 at 9:59 AM UTCmonitoring

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

3. June 26, 2026 at 10:11 AM UTCresolved

   Este incidente ha sido resuelto.

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

1. June 22, 2026 at 6:50 PM UTCidentified

   The issue has been identified and a fix is being implemented.

2. June 22, 2026 at 7:09 PM UTCmonitoring

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

3. June 22, 2026 at 7:24 PM UTCresolved

   This incident has been resolved.

1. May 4, 2026 at 4:02 PM UTCmonitoring

   Instructure has confirmed a security Incident on their systems. Although VitalSource has not been impacted, we are monitoring our integrations with them closely and assisting Instructure where feasible. For more information, go to: https://status.instructure.com.

2. May 6, 2026 at 2:04 PM UTCresolved

   This incident has been resolved.

1. March 28, 2026 at 12:55 AM UTCinvestigating

   We are currently investigating this issue.

2. March 28, 2026 at 1:12 AM UTCmonitoring

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

3. March 28, 2026 at 1:19 AM UTCresolved

   This incident has been resolved.

1. March 10, 2026 at 12:49 PM UTCidentified

   We are aware of an issue affecting the MBS/Verba integration that may impact course material shopping for students at MBS-connected institutions. Additionally, students with recent enrollment changes (new enrollments or newly added sections) may experience access delays. Students with existing enrollments are unaffected. This issue originates with MBS and is currently under investigation by their team. VitalSource systems are fully operational. We are in direct contact with MBS and are actively monitoring. We will provide updates as the situation develops.

2. March 12, 2026 at 12:42 PM UTCresolved

   This incident has been resolved.

1. January 27, 2026 at 2:22 AM UTCinvestigating

   We are investigating an issue affecting checkout on our store platform.

2. January 27, 2026 at 2:29 AM UTCinvestigating

   We are continuing to investigate this issue.

3. January 27, 2026 at 2:53 AM UTCidentified

   The issue has been identified and a fix is being implemented.

4. January 27, 2026 at 2:55 AM UTCmonitoring

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

5. January 27, 2026 at 3:14 AM UTCresolved

   This incident has been resolved. A failure in one of our underlying services caused this disruption, but we have successfully restored service.

1. December 5, 2025 at 9:09 AM UTCinvestigating

   We are investigating an issue impacting multiple applications across our systems. The issue appears to be with one of our providers Cloudflare: https://www.cloudflarestatus.com/incidents/lfrm31y6sw9q

2. December 5, 2025 at 9:13 AM UTCidentified

   We have confirmed that this is an issue with one of our service providers.

3. December 5, 2025 at 9:15 AM UTCmonitoring

   We're seeing our services come back online. Cloudflare has confirmed that they have put a fix in place. We are monitoring as our service is restored.

4. December 5, 2025 at 9:21 AM UTCresolved

   This incident has been resolved.

1. November 18, 2025 at 2:53 PM UTCmonitoring

   We are currently experiencing intermittent availability issues across VitalSource services due to an ongoing incident with our upstream provider, Cloudflare. While Cloudflare updates indicate a fix has been implemented, we are continuing to observe impact on our platforms. We are actively monitoring the situation and Cloudflare's official status updates here: https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

2. November 18, 2025 at 6:33 PM UTCresolved

   Cloudflare has reported that its services are currently operating normally. They are no longer observing elevated errors or latency across the Cloudflare network.

1. November 4, 2025 at 9:57 PM UTCinvestigating

   We are investigating an issue impacting multiple applications.

2. November 4, 2025 at 10:21 PM UTCinvestigating

   We are continuing to investigate this issue.

3. November 4, 2025 at 10:52 PM UTCmonitoring

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

4. November 4, 2025 at 10:57 PM UTCresolved

   This incident has been resolved.

1. September 23, 2025 at 10:15 PM UTCinvestigating

   We are currently investigating this issue.

2. September 23, 2025 at 10:50 PM UTCmonitoring

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

3. September 23, 2025 at 11:39 PM UTCresolved

   This incident has been resolved.

1. September 4, 2025 at 11:45 AM UTCinvestigating

   We are investigating an issue impacting Bookshelf Online.

2. September 4, 2025 at 12:09 PM UTCmonitoring

   Bookshelf is back online, and we are monitoring its impact.

3. September 4, 2025 at 1:12 PM UTCresolved

   This incident has been resolved.

4. September 4, 2025 at 8:10 PM UTCpostmortem

   Bookshelf Online experienced a complete service outage this morning due to processing issues with our Manage API. The incident was triggered when our system encountered difficulties handling a large batch of asset updates. While our platform has successfully processed similar volumes in the past, this particular batch appears to have contained edge cases or problematic assets that degraded our API's processing capability. This degradation cascaded through our system, ultimately rendering Bookshelf completely unavailable to users. Our engineering team quickly identified the contributing factors and implemented emergency mitigation measures, including temporarily blocking the problematic API endpoint. We have conducted an investigation and implemented permanent safeguards, including proper rate limiting for our asset update API and enhanced data validation processes. Our team is also reviewing whether any data reprocessing is needed to ensure complete data integrity. Service is fully operational, and we're implementing measures to prevent similar incidents in the future.

1. August 25, 2025 at 2:45 PM UTCinvestigating

   We are currently investigating this issue.

2. August 25, 2025 at 4:00 PM UTCidentified

   We have made some changes that have improved our performance and are monitoring closely for any other issues.

3. August 25, 2025 at 5:59 PM UTCidentified

   We are continuing to work on this issue. The Manage Platform UI is offline for maintenance.

4. August 25, 2025 at 6:44 PM UTCidentified

   We have been experiencing an intermittent service degradation affecting VitalSource systems. A subset of users and API integrations may encounter slow performance or error messages, while others remain unaffected. Our engineering teams are actively investigating and working on remediation. We will provide the next update as soon as more information is available.

5. August 25, 2025 at 7:09 PM UTCmonitoring

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

6. August 25, 2025 at 9:05 PM UTCidentified

   We are continuing to work on a fix for this issue.

7. August 25, 2025 at 9:09 PM UTCresolved

   This incident has been resolved.

8. August 25, 2025 at 10:33 PM UTCpostmortem

   Today, we experienced intermittent service interruption across VitalSource systems. During this incident, users and API integrations encountered slow performance, error messages, and intermittent access issues. The cause was due to significant request queuing in our core API infrastructure. This request queuing caused latency to some of our critical API endpoints, and this latency was then felt across several of our end-user-facing applications as well as the APIs that power our partner applications.  Our engineering team resolved the request queuing issue by adjusting database configurations and Kubernetes cluster settings. This added additional capacity, and we were able to return to normal operations. All systems are now operating normally. Our engineering team's highest priority is to understand exactly why we saw severe request queuing, and we will continue to monitor performance closely.

1. August 19, 2025 at 6:55 PM UTCresolved

   Between 11:15 and 11:50 am ET on August 19, our Launch service experienced degraded performance due to excessive database load from background job activity, which our teams quickly identified and resolved by isolating the problematic processes.