Bibliu Outage History

Bibliu had 7 outages in the last 2 years totaling 9h 33m of downtime — averaging 0.3 incidents per month.

There were 7 Bibliu outages since October 14, 2025 totaling 9h 33m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.bibliu.com

Minor June 22, 2026

BibliU is currently unavailable from Canvas learning management systems

Detected by Pingoru: Jun 22, 2026, 02:44 PM UTC
Resolved: Jun 22, 2026, 02:44 PM UTC
Duration: —

Affected: ReaderAdmin

Timeline · 4 updates

investigating Jun 22, 2026, 12:20 PM UTC

Status: Investigating Signing in to BibliU is currently having issues from Canvas learning management systems. We are currently investigating the issue. Affected components Reader (Partial outage) Admin (Partial outage)
identified Jun 22, 2026, 01:14 PM UTC

Status: Identified The team has identified the issue, and are working on fixing the root cause. Affected components Reader (Partial outage) Admin (Partial outage)
monitoring Jun 22, 2026, 01:54 PM UTC

Status: Monitoring We released the necessary changes and are now monitoring the BibliU platform and our integrations. Affected components Reader (Partial outage) Admin (Partial outage)
resolved Jun 22, 2026, 02:44 PM UTC

Status: Resolved This incident has been resolved. Affected components Reader (Operational) Admin (Operational)

Read the full incident report →

Minor March 4, 2026

Admin and Ops dashboard unable to load

Detected by Pingoru: Mar 04, 2026, 10:39 PM UTC
Resolved: Mar 04, 2026, 10:39 PM UTC
Duration: —

Affected: Admin

Timeline · 3 updates

investigating Mar 04, 2026, 09:49 PM UTC

Status: Investigating The BibliU Ops and Admin tools are unable to load any data due to an internal server error when connecting to MySQL. Affected components Admin (Full outage)
identified Mar 04, 2026, 10:35 PM UTC

Status: Identified We believe we have identified the underlying issue and are working to implement a patch. Affected components Admin (Full outage)
resolved Mar 04, 2026, 10:39 PM UTC

Status: Resolved The underlying problem has been resolved, caused by an out of storage database. Affected components Admin (Operational)