Vitalsource driftsforstyrrelser

1. 26. august 2026 kl. 16.16 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem påvirker Bogreol Online.

2. 26. august 2026 kl. 16.24 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 26. august 2026 kl. 16.25 UTCmonitoring

   Vi fortsætter med at overvåge for yderligere spørgsmål.

4. 26. august 2026 kl. 16.30 UTCresolved

   Denne hændelse er blevet løst.

5. 26. august 2026 kl. 17.31 UTCpostmortem

   Tirsdag den 25. august, mellem ca. 1: 50 PM og 2: 00 PM ET, og igen kort omkring 2: 45 PM ET, nogle brugere stødt på fejl, langsom side belastninger, eller vanskeligheder med at åbne bøger i Boghylde Online. En lignende afbrydelse fandt sted onsdag den 26. august mellem ca. 12: 06 og 12: 17 ET. Nogle brugere oplevede også intermitterende signal- i problemer under disse vinduer. Årsagen var en intern tjenesteafhængighed, der blev ustabil og stoppede med at acceptere nye anmodninger. Andre dele af platformen, herunder kursus materiale levering via LMS-integration og e-handel, blev ikke påvirket. Vi har identificeret den sandsynlige udløser for onsdag gentagelse, validerer en rettelse, og har hærdet denne komponent mod gentagelse. Vi overvåger nøje resten af perioden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 25. august 2026 kl. 18.05 UTCinvestigating

   Vi er i øjeblikket ved at undersøge et problem påvirker Bogreol Online.

2. 25. august 2026 kl. 18.27 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 25. august 2026 kl. 18.40 UTCresolved

   Denne hændelse er blevet løst.

4. 26. august 2026 kl. 17.32 UTCpostmortem

   Tirsdag den 25. august, mellem ca. 1: 50 PM og 2: 00 PM ET, og igen kort omkring 2: 45 PM ET, nogle brugere stødt på fejl, langsom side belastninger, eller vanskeligheder med at åbne bøger i Boghylde Online. En lignende afbrydelse fandt sted onsdag den 26. august mellem ca. 12: 06 og 12: 17 ET. Nogle brugere oplevede også intermitterende signal- i problemer under disse vinduer. Årsagen var en intern tjenesteafhængighed, der blev ustabil og stoppede med at acceptere nye anmodninger. Andre dele af platformen, herunder kursus materiale levering via LMS-integration og e-handel, blev ikke påvirket. Vi har identificeret den sandsynlige udløser for onsdag gentagelse, validerer en rettelse, og har hærdet denne komponent mod gentagelse. Vi overvåger nøje resten af perioden.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 20. august 2026 kl. 14.26 UTCinvestigating

   Vi undersøger i øjeblikket dette spørgsmål.

2. 20. august 2026 kl. 14.50 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 20. august 2026 kl. 14.57 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 5. august 2026 kl. 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 kl. 22.29 UTCidentified

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

2. 5. august 2026 kl. 16.38 UTCresolved

   All systems operational.

1. 20. juli 2026 kl. 20.16 UTCinvestigating

   Vi oplever i øjeblikket en forringelse af tjenesten. Vi efterforsker det.

2. 20. juli 2026 kl. 20.28 UTCinvestigating

   Vi fortsætter med at undersøge dette spørgsmål.

3. 20. juli 2026 kl. 21.12 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

4. 20. juli 2026 kl. 23.31 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 7. juli 2026 kl. 22.41 UTCinvestigating

   TextbookX oplever i øjeblikket intermitterende problemer. Holdet efterforsker.

2. 7. juli 2026 kl. 23.15 UTCidentified

   Spørgsmålet er blevet identificeret, og et fix er ved at blive gennemført.

3. 7. juli 2026 kl. 23.20 UTCresolved

   Hændelsen er løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 26. juni 2026 kl. 09.12 UTCinvestigating

   Vi oplever i øjeblikket en forringelse af tjenesten. Vi efterforsker det.

2. 26. juni 2026 kl. 09.59 UTCmonitoring

   Et fix er blevet gennemført, og vi overvåger resultaterne.

3. 26. juni 2026 kl. 10.11 UTCresolved

   Denne hændelse er blevet løst.

Automatisk oversat fra den officielle hændelsesopdatering.

1. 22. juni 2026 kl. 18.50 UTCidentified

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

2. 22. juni 2026 kl. 19.09 UTCmonitoring

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

3. 22. juni 2026 kl. 19.24 UTCresolved

   This incident has been resolved.

1. 4. maj 2026 kl. 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. maj 2026 kl. 14.04 UTCresolved

   This incident has been resolved.

1. 28. marts 2026 kl. 00.55 UTCinvestigating

   We are currently investigating this issue.

2. 28. marts 2026 kl. 01.12 UTCmonitoring

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

3. 28. marts 2026 kl. 01.19 UTCresolved

   This incident has been resolved.

1. 10. marts 2026 kl. 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. marts 2026 kl. 12.42 UTCresolved

   This incident has been resolved.

1. 27. januar 2026 kl. 02.22 UTCinvestigating

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

2. 27. januar 2026 kl. 02.29 UTCinvestigating

   We are continuing to investigate this issue.

3. 27. januar 2026 kl. 02.53 UTCidentified

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

4. 27. januar 2026 kl. 02.55 UTCmonitoring

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

5. 27. januar 2026 kl. 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. december 2025 kl. 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. december 2025 kl. 09.13 UTCidentified

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

3. 5. december 2025 kl. 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. december 2025 kl. 09.21 UTCresolved

   This incident has been resolved.

1. 18. november 2025 kl. 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. november 2025 kl. 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. november 2025 kl. 21.57 UTCinvestigating

   We are investigating an issue impacting multiple applications.

2. 4. november 2025 kl. 22.21 UTCinvestigating

   We are continuing to investigate this issue.

3. 4. november 2025 kl. 22.52 UTCmonitoring

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

4. 4. november 2025 kl. 22.57 UTCresolved

   This incident has been resolved.

1. 23. september 2025 kl. 22.15 UTCinvestigating

   We are currently investigating this issue.

2. 23. september 2025 kl. 22.50 UTCmonitoring

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

3. 23. september 2025 kl. 23.39 UTCresolved

   This incident has been resolved.

1. 4. september 2025 kl. 11.45 UTCinvestigating

   We are investigating an issue impacting Bookshelf Online.

2. 4. september 2025 kl. 12.09 UTCmonitoring

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

3. 4. september 2025 kl. 13.12 UTCresolved

   This incident has been resolved.

4. 4. september 2025 kl. 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 kl. 14.45 UTCinvestigating

   We are currently investigating this issue.

2. 25. august 2025 kl. 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 kl. 17.59 UTCidentified

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

4. 25. august 2025 kl. 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 kl. 19.09 UTCmonitoring

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

6. 25. august 2025 kl. 21.05 UTCidentified

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

7. 25. august 2025 kl. 21.09 UTCresolved

   This incident has been resolved.

8. 25. august 2025 kl. 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 kl. 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.