User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
vivlio.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps 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. Every report with a known place can appear on the map. Updates every minute.
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 34 min ago. Last stored result reached it in 685 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 520 ms | 0 |
| Tue 02 | 0 | 0.0 | 700 ms | 0 |
| Tue 04 | 0 | 0.0 | 770 ms | 0 |
| Tue 06 | 0 | 0.0 | 813 ms | 0 |
| Tue 08 | 0 | 0.0 | 504 ms | 0 |
| Tue 10 | 0 | 0.0 | 498 ms | 0 |
| Tue 12 | 0 | 0.0 | 751 ms | 0 |
| Tue 15 | 0 | 0.0 | 599 ms | 0 |
| Tue 17 | 0 | 0.0 | 623 ms | 0 |
| Tue 19 | 0 | 0.0 | 765 ms | 0 |
| Tue 21 | 0 | 0.0 | 667 ms | 0 |
| Wed 00 | 0 | 0.0 | 644 ms | 0 |
| Wed 02 | 0 | 0.0 | 743 ms | 0 |
| Wed 04 | 0 | 0.0 | 701 ms | 0 |
| Wed 06 | 0 | 0.0 | 658 ms | 0 |
| Wed 09 | 0 | 0.0 | 638 ms | 0 |
| Wed 11 | 0 | 0.0 | 703 ms | 0 |
| Wed 13 | 0 | 0.0 | 502 ms | 0 |
| Wed 15 | 0 | 0.0 | 777 ms | 0 |
| Wed 17 | 0 | 0.0 | 713 ms | 0 |
| Wed 19 | 0 | 0.0 | 792 ms | 0 |
| Wed 22 | 0 | 0.0 | 797 ms | 0 |
| Thu 00 | 0 | 0.0 | 743 ms | 0 |
| Thu 02 | 0 | 0.0 | 759 ms | 0 |
| Thu 04 | 0 | 0.0 | 770 ms | 0 |
| Thu 06 | 0 | 0.0 | 882 ms | 0 |
| Thu 08 | 0 | 0.0 | 733 ms | 0 |
| Thu 10 | 0 | 0.0 | 706 ms | 0 |
| Thu 12 | 0 | 0.0 | 741 ms | 0 |
| Thu 14 | 0 | 0.0 | 668 ms | 0 |
| Thu 16 | 0 | 0.0 | 580 ms | 0 |
| Thu 19 | 0 | 0.0 | 733 ms | 0 |
| Thu 21 | 0 | 0.0 | 653 ms | 0 |
| Thu 23 | 0 | 0.0 | 701 ms | 0 |
| Fri 01 | 0 | 0.0 | 734 ms | 0 |
| Fri 03 | 0 | 0.0 | 533 ms | 0 |
| Fri 05 | 0 | 0.0 | 763 ms | 0 |
| Fri 07 | 0 | 0.0 | 702 ms | 0 |
| Fri 09 | 0 | 0.0 | 741 ms | 0 |
| Fri 10 | 0 | 0.0 | 632 ms | 0 |
| Fri 12 | 0 | 0.0 | 542 ms | 0 |
| Fri 14 | 0 | 0.0 | 567 ms | 0 |
| Fri 16 | 0 | 0.0 | 714 ms | 0 |
| Fri 17 | 0 | 0.0 | 500 ms | 0 |
| Fri 19 | 0 | 0.0 | 743 ms | 0 |
| Fri 21 | 0 | 0.0 | 530 ms | 0 |
| Fri 23 | 0 | 0.0 | 624 ms | 0 |
| Sat 00 | 0 | 0.0 | 685 ms | 0 |
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
No outages on record for Vivlio 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 Vivlio goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Vivlio alerts to Slack, Discord or a webhook — free.
Vivlio, at vivlio.com, is one of the Cloud & developer services we monitor. Champion européen du livre numérique spécialisé dans les liseuses, Vivlio propose un écosystème de lecture numérique complet au service de la lecture, des lecteurs et des libraires.
Vivlio publishes an official status page at status.vivlio.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 654 ms average, 500–790 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Vivlio incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
654 ms on average over the last 24 hours (500–790 ms).
Yes, at https://status.vivlio.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Vivlio here at once, the problem is on Vivlio's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with Vivlio. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.