User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Entertainment
libbyapp.com · Entertainment
Checks are succeeding and user reports are near the baseline.
Live diagnosis
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last check reached it in 120 ms · 5 min ago.
No status feed
Libby does not publish a status feed we can read.
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 20:30 | 0 | 0.0 | 866 ms | 0 |
| 20:45 | 0 | 0.0 | 448 ms | 0 |
| 21:00 | 0 | 0.0 | 167 ms | 0 |
| 21:15 | 0 | 0.0 | 2466 ms | 0 |
| 21:30 | 0 | 0.0 | 349 ms | 0 |
| 21:45 | 0 | 0.0 | 442 ms | 0 |
| 22:00 | 0 | 0.0 | 286 ms | 0 |
| 22:15 | 0 | 0.0 | 903 ms | 0 |
| 22:30 | 0 | 0.0 | 335 ms | 0 |
| 22:45 | 0 | 0.0 | 326 ms | 0 |
| 23:00 | 0 | 0.0 | 289 ms | 0 |
| 23:15 | 0 | 0.0 | 339 ms | 0 |
| 23:30 | 0 | 0.0 | 120 ms | 0 |
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Libby yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Libby goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Libby alerts to Slack, Discord or a webhook — free.
Libby is listed in our Entertainment category and checked at libbyapp.com. Libby is OverDrive's app for borrowing e-books and audiobooks from public libraries.
Libby has no official status feed we can read, so this page relies on our own checks and user reports.
What usually goes wrong with Libby: loans not downloading, library card sign-in errors, and audiobooks that will not play.
Measured uptime from our checks: 100% over 1 day of checks. No public incidents logged since monitoring began 1 day ago.
Response time over the last 24 hours: 613 ms average, 120–3512 ms range across 23 successful checks.
Checks are succeeding and user reports are near the baseline.
We have not recorded a public Libby incident since monitoring began 1 day ago.
From our own checks: 100% over 1 day of checks.
613 ms on average over the last 24 hours (120–3512 ms).
Not one we can read. This page uses independent checks of libbyapp.com and user reports.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For Libby, watch for loans not downloading, library card sign-in errors, and audiobooks that will not play. If many people report Libby here at once, the problem is on Libby's side.