59 Vitalsource incidents · 2022年6月 — official updates, affected components, duration and resolution details.
我们正在调查一个影响Bookshelf在线的问题.
一项措施已经执行,我们正在监测结果.
我们正在继续监测任何其他问题.
这一事件已经得到解决.
8月25日星期二, 大约下午1: 50至2: 00 PM ET, 8月26日星期三, 大约12:06到12:17 PM ET, 一些用户在这些窗口中也遇到间歇性的签入问题. 原因是内部服务依赖性变得不稳定并不再接受新的请求. 该平台的其他部分,包括通过LMS集成和电子商务提供课程材料,没有受到影响。 我们已查明了星期三复发的可能触发因素,正在验证一个定律,并且使这一部分更加硬化,防止复发。 我们正在密切监测任期的其余期间.
自动翻译自官方事件更新。
我们正在调查一个影响Bookshelf在线的问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
8月25日星期二, 大约下午1: 50至2: 00 PM ET, 8月26日星期三, 大约12:06到12:17 PM ET, 一些用户在这些窗口中也遇到间歇性的签入问题. 原因是内部服务依赖性变得不稳定并不再接受新的请求. 该平台的其他部分,包括通过LMS集成和电子商务提供课程材料,没有受到影响。 我们已查明了星期三复发的可能触发因素,正在验证一个定律,并且使这一部分更加硬化,防止复发。 我们正在密切监测任期的其余期间.
自动翻译自官方事件更新。
我们目前正在调查这一问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
A networking issue caused an outage of Bookshelf Online from approximately 9:05 to 9:15 AM ET. Service has been fully restored.
Section history tracking will be temporarily unavailable for ~24 hours. Collect remains fully functional.
All systems operational.
我们目前正在经历服务退化。 我们正在调查.
我们正在继续调查这一问题.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
教科书X目前时断时续。 调查组正在调查.
这一问题已经确定,目前正在实施一个解决办法.
此事已决.
自动翻译自官方事件更新。
我们目前正在经历服务退化。 我们正在调查.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
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.
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.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
This incident has been resolved.
We are investigating an issue affecting checkout on our store platform.
We are continuing to investigate this issue.
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. A failure in one of our underlying services caused this disruption, but we have successfully restored service.
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
We have confirmed that this is an issue with one of our service providers.
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.
This incident has been resolved.
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
Cloudflare has reported that its services are currently operating normally. They are no longer observing elevated errors or latency across the Cloudflare network.
We are investigating an issue impacting multiple applications.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue impacting Bookshelf Online.
Bookshelf is back online, and we are monitoring its impact.
This incident has been resolved.
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.
We are currently investigating this issue.
We have made some changes that have improved our performance and are monitoring closely for any other issues.
We are continuing to work on this issue. The Manage Platform UI is offline for maintenance.
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.
A fix has been implemented and we are monitoring the results.
We are continuing to work on a fix for this issue.
This incident has been resolved.
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.
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.