Instructure Security Incident
Resolved
This incident has been resolved.
May 4, 4:02 PMResolved May 6, 2:04 PMNone
Status Provider
Home
/
Status
/
Service
Home
/
Status
/
Service
Digital textbooks and course materials for educational institutions.
Source
auto
Category
Education
Adapter
STATUSPAGE IO
Verified
Pending review
Current state
Operational
Checked 33m ago
14
Components
0
Active incidents
0
Maintenance
50%
90d uptime
Instructure Security Incident
May 4, 4:02 PM
Normalized official status-page data for incidents, maintenance, components, and history.
50%
Known uptime
4 known history days
14
Components tracked
0 outage, 0 degraded
50
Incidents indexed
0 active right now
26
Maintenance windows
0 active or scheduled
Components with the most recent status-page events.
Acrobatiq
Operational
Akademos TextbookX
Operational
Analytics
Operational
Bookshelf Online
Operational
Manage Platform
Operational
Component changes, incidents, and maintenance windows grouped by day.
operational
degraded
outage
maintenance
unknown
2
operational days
0
degraded days
2
outage days
0
maintenance days
86
unknown days
Latest outages and degradations detected from the official status page.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
This incident has been resolved. A failure in one of our underlying services caused this disruption, but we have successfully restored service.
This incident has been resolved.
Cloudflare has reported that its services are currently operating normally. They are no longer observing elevated errors or latency across the Cloudflare network.
This incident has been resolved.
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.
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.
Scheduled and completed maintenance windows are separated from incidents.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
The scheduled maintenance has been completed.
Maintenance is complete.
The scheduled maintenance has been completed.
Uptimus tracks the official Vitalsource status page, normalizes upstream events, and separates incidents from scheduled maintenance.
Official source
https://status.vitalsource.com
Adapter
STATUSPAGE IO
Alert streams
Incidents, component changes, and maintenance windows.
Public SEO page
Indexable status history for users searching outage information.
Regional reports can be layered on top of official provider status when user signals are available.
Showing 1 to 14 of 14 tracked components.
| Component | Status | Type | Last changed |
|---|---|---|---|
V3/V4 APIs | Operational | Component | Not recorded |
VitalSource Launch - LTI, LMS, SAML, Office365, OAuth2 and other integrations | Operational | Component | Not recorded |
Bookshelf Online | Operational | Component | Not recorded |
Manage Platform | Operational | Component | Not recorded |
Store, Sampling and Ecommerce Platform | Operational | Component | Not recorded |
VitalSource Explore | Operational | Component | Not recorded |
Analytics | Operational | Component | Not recorded |
Acrobatiq | Operational | Component | Not recorded |
Verba Collect | Operational | Component | Not recorded |
Verba Connect | Operational | Component | Not recorded |
Verba Compete | Operational | Component | Not recorded |
Verba Compare | Operational | Component | Not recorded |
Akademos TextbookX | Operational | Component | Not recorded |
Sylla | Operational | Component | Not recorded |
Follow outages, degraded components, and maintenance updates in your Uptimus workspace with email, push, and webhook alerts.
Official provider components
Incident and maintenance separation
Workspace alerts and webhooks
Related status pages based on category, adapter type, and operational history.
Vitalsource is currently marked as Operational in Uptimus based on the latest official status page check.
Supported status page providers are checked continuously by our scraper scheduler. The public page is cached briefly for SEO and performance.
No. Uptimus stores incidents and maintenance windows separately when the upstream provider exposes enough detail.
Yes. Create an Uptimus workspace, follow this provider, and choose email, push, or webhook notifications.
