Istoricul incidentelor Vitalsource

1. 26 august 2026 la 16:16 UTCinvestigating

   În prezent investigăm o problemă care afectează Bookshelf Online.

2. 26 august 2026 la 16:24 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 26 august 2026 la 16:25 UTCmonitoring

   Continuăm să monitorizăm orice alte probleme.

4. 26 august 2026 la 16:30 UTCresolved

   Acest incident a fost rezolvat.

5. 26 august 2026 la 17:31 UTCpostmortem

   Marți, 25 august, între aproximativ 1:50 PM și 2:00 PM ET, și din nou pe scurt în jurul orei 2:45 PM ET, unii utilizatori au întâlnit erori, sarcini de pagină lentă, sau dificultăți de deschidere a cărților în Bookshelf Online. O perturbare similară a avut loc miercuri, 26 august, între aproximativ 12:06 PM şi 12:17 PM ET. Unii utilizatori au avut, de asemenea, probleme intermitente de sign-in în timpul acestor ferestre. Cauza a fost o dependență internă de servicii care a devenit instabilă și a încetat să accepte noi cereri. Alte părți ale platformei, inclusiv livrarea materialelor de curs prin integrarea LMS și comerțul electronic, nu au fost afectate. Am identificat cel mai probabil declanşator al recurenţei de miercuri, validăm o doză şi am întărit această componentă împotriva recurenţelor. Monitorizăm îndeaproape, în restul perioadei de început.

Traducere automată din actualizarea oficială a incidentului.

1. 25 august 2026 la 18:05 UTCinvestigating

   În prezent investigăm o problemă care afectează Bookshelf Online.

2. 25 august 2026 la 18:27 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 25 august 2026 la 18:40 UTCresolved

   Acest incident a fost rezolvat.

4. 26 august 2026 la 17:32 UTCpostmortem

   Marți, 25 august, între aproximativ 1:50 PM și 2:00 PM ET, și din nou pe scurt în jurul orei 2:45 PM ET, unii utilizatori au întâlnit erori, sarcini de pagină lentă, sau dificultăți de deschidere a cărților în Bookshelf Online. O perturbare similară a avut loc miercuri, 26 august, între aproximativ 12:06 PM şi 12:17 PM ET. Unii utilizatori au avut, de asemenea, probleme intermitente de sign-in în timpul acestor ferestre. Cauza a fost o dependență internă de servicii care a devenit instabilă și a încetat să accepte noi cereri. Alte părți ale platformei, inclusiv livrarea materialelor de curs prin integrarea LMS și comerțul electronic, nu au fost afectate. Am identificat cel mai probabil declanşator al recurenţei de miercuri, validăm o doză şi am întărit această componentă împotriva recurenţelor. Monitorizăm îndeaproape, în restul perioadei de început.

Traducere automată din actualizarea oficială a incidentului.

1. 20 august 2026 la 14:26 UTCinvestigating

   În prezent investigăm această problemă.

2. 20 august 2026 la 14:50 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 20 august 2026 la 14:57 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 5 august 2026 la 14:14 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. 4 august 2026 la 22:29 UTCidentified

   Istoricul secţiunii va fi temporar indisponibil pentru ~24 de ore. Colecta rămâne pe deplin funcțională.

2. 5 august 2026 la 16:38 UTCresolved

   All systems operational.

Traducere automată din actualizarea oficială a incidentului.

1. 20 iulie 2026 la 20:16 UTCinvestigating

   Ne confruntăm în prezent cu o degradare a serviciului. Suntem ancheta.

2. 20 iulie 2026 la 20:28 UTCinvestigating

   Continuăm să investigăm această problemă.

3. 20 iulie 2026 la 21:12 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

4. 20 iulie 2026 la 23:31 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 7 iulie 2026 la 22:41 UTCinvestigating

   TextbookX se confruntă în prezent cu probleme intermitente. Echipa investighează.

2. 7 iulie 2026 la 23:15 UTCidentified

   Problema a fost identificată, iar în prezent se pune în aplicare o soluție.

3. 7 iulie 2026 la 23:20 UTCresolved

   Incidentul a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 26 iunie 2026 la 09:12 UTCinvestigating

   Ne confruntăm în prezent cu o degradare a serviciului. Suntem ancheta.

2. 26 iunie 2026 la 09:59 UTCmonitoring

   A fost implementată o soluţie şi monitorizăm rezultatele.

3. 26 iunie 2026 la 10:11 UTCresolved

   Acest incident a fost rezolvat.

Traducere automată din actualizarea oficială a incidentului.

1. 22 iunie 2026 la 18:50 UTCidentified

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

2. 22 iunie 2026 la 19:09 UTCmonitoring

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

3. 22 iunie 2026 la 19:24 UTCresolved

   This incident has been resolved.

1. 4 mai 2026 la 16:02 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. 6 mai 2026 la 14:04 UTCresolved

   This incident has been resolved.

1. 28 martie 2026 la 00:55 UTCinvestigating

   We are currently investigating this issue.

2. 28 martie 2026 la 01:12 UTCmonitoring

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

3. 28 martie 2026 la 01:19 UTCresolved

   This incident has been resolved.

1. 10 martie 2026 la 12:49 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. 12 martie 2026 la 12:42 UTCresolved

   This incident has been resolved.

1. 27 ianuarie 2026 la 02:22 UTCinvestigating

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

2. 27 ianuarie 2026 la 02:29 UTCinvestigating

   We are continuing to investigate this issue.

3. 27 ianuarie 2026 la 02:53 UTCidentified

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

4. 27 ianuarie 2026 la 02:55 UTCmonitoring

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

5. 27 ianuarie 2026 la 03:14 UTCresolved

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

1. 5 decembrie 2025 la 09:09 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. 5 decembrie 2025 la 09:13 UTCidentified

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

3. 5 decembrie 2025 la 09:15 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. 5 decembrie 2025 la 09:21 UTCresolved

   This incident has been resolved.

1. 18 noiembrie 2025 la 14:53 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. 18 noiembrie 2025 la 18:33 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. 4 noiembrie 2025 la 21:57 UTCinvestigating

   We are investigating an issue impacting multiple applications.

2. 4 noiembrie 2025 la 22:21 UTCinvestigating

   We are continuing to investigate this issue.

3. 4 noiembrie 2025 la 22:52 UTCmonitoring

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

4. 4 noiembrie 2025 la 22:57 UTCresolved

   This incident has been resolved.

1. 23 septembrie 2025 la 22:15 UTCinvestigating

   We are currently investigating this issue.

2. 23 septembrie 2025 la 22:50 UTCmonitoring

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

3. 23 septembrie 2025 la 23:39 UTCresolved

   This incident has been resolved.

1. 4 septembrie 2025 la 11:45 UTCinvestigating

   We are investigating an issue impacting Bookshelf Online.

2. 4 septembrie 2025 la 12:09 UTCmonitoring

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

3. 4 septembrie 2025 la 13:12 UTCresolved

   This incident has been resolved.

4. 4 septembrie 2025 la 20:10 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. 25 august 2025 la 14:45 UTCinvestigating

   We are currently investigating this issue.

2. 25 august 2025 la 16:00 UTCidentified

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

3. 25 august 2025 la 17:59 UTCidentified

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

4. 25 august 2025 la 18:44 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. 25 august 2025 la 19:09 UTCmonitoring

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

6. 25 august 2025 la 21:05 UTCidentified

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

7. 25 august 2025 la 21:09 UTCresolved

   This incident has been resolved.

8. 25 august 2025 la 22:33 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. 19 august 2025 la 18:55 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.