Is Vivlio Down?

SaaSLive status, outages, and incident history

No. Vivlio is up right now.

Every monitored Vivlio system is operational as of August 11, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 47m agoLive, rechecked every 60s

Start monitoring Vivlio Official Vivlio status page

How we know: the official Vivlio status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Vivlio Component Status

The main Vivlio systems on this page. All 11 are operational right now.

11operational

API » Cloud API

Operational

API » Download API

Operational

API » Order API

Operational

8 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Admin Backend, Application » Desktop Application, Application » Ereader Device, Application » Mobile Application, Application » Website my.vivlio.com, DRM » Adobe, DRM » LCP, Ecommerce.

Create a free account

Component statuses may change independently during partial outages.

Recent Vivlio Outages & Incidents

Incident history from the official Vivlio status page, including resolution updates.

Uptime history4 days observed

Aug 8100.00% averageAug 11

Some web shops are extremely slow.Resolved Aug 5, 2026 · 41 minResolved

This incident has been resolved. --- [2026-08-05T18:26:06.784+02:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-08-05T18:14:47.341+02:00] (identified) The issue has been identified and a fix is being implemented. --- [2026-08-05T18:13:49.288+02:00] (investigating) We are currently investigating this issue.

Book download problemsResolved Jul 30, 2026 · 5h 47mResolved

No new problems have been seen. The incident is now closed. --- [2026-07-30T12:33:08.126+02:00] (monitoring) We are continuing to monitor for any further issues. --- [2026-07-30T12:31:47.867+02:00] (monitoring) No new problem appears on our monitoring showing that the data cleanup was effective. --- [2026-07-30T11:52:57.901+02:00] (monitoring) We have identified a source of the problem. The data have been cleaned and customers should now be able to download their books. We are still working on the problem to find the root cause and secure the fix. Sorry for the impact on customer, we are all committed to resolve it fully quickly. --- [2026-07-30T11:50:34.750+02:00] (monitoring) Some customers experienced download error of their book. This is mostly impacting new purchases. The problem is not global only some customers where impacted.

Error with Adobe links / Problème de licence AdobeResolved May 19, 2026 · 43h 18mResolved

Chers partenaires, Le rattrapage des livres impactés depuis le 11 mai s'est terminé ce jour. Nous vous confirmons que les livres de notre catalogue ne sont plus concernés par le problème avec la lecture des fichiers Adobe. Les premiers retours de nos utilisateurs sont positifs, ils ne présentent plus de problèmes à l'ouverture des livres. Nous restons à votre écoute et disponibles si vous rencontrez toujours des difficultés. Belle journée, Bien cordialement, __________ Dear Partners, The process of resolving the issue affecting books since May 11 was completed today. We can confirm that the books in our catalog are no longer affected by the error message with Adobe files. First feedbacks from our users has been positive; they are no longer experiencing issues when opening the books. We remain at your disposal and available if you continue to encounter difficulties. Have a great day, Best regards, --- [2026-05-20T17:59:57.175+02:00] (identified) Chers partenaires, Un correctif a été déployé ce jour pour que le problème ne se présente plus sur les nouveaux téléchargements. Le rattrapage de tous les livres impactés est en cours. Nous mettrons à jour la Status Page dès résolution totale du problème. Merci pour votre compréhension. Bonne journée, Bien cordialement, _____________ Dear Partners, A fix has been deployed today to ensure that the issue no longer occurs with new downloads. We are currently working to resolve the issue for all affected books. We will update the Status Page once the issue has been fully resolved. Thank you for your understanding. Have a great day, Best regards, --- [2026-05-20T10:15:59.190+02:00] (identified) Chers partenaires, Notre équipe technique a identifié la cause de l'erreur E_LIC_WRONG_DEVICE_TYPE. L'impact est sur tous les livres qui ont été téléchargés pour la première fois depuis le 11 mai. Nous allons corriger les titres impactés depuis le 11 mai et nous allons corriger le problème pour que les nouveaux titres ne soient plus impactés. Nous mettrons à jour cette Status Page dès résolution du problème. Encore merci pour votre patience et votre compréhension. Bonne journée, Bien cordialement, ______________ Dear Partners, Our technical team has identified the cause of the E_LIC_WRONG_DEVICE_TYPE error. This issue affects all books that were downloaded for the first time on or after May 11. We will correct the titles affected since May 11 and fix the issue so that new titles are no longer affected. We will update this Status Page as soon as the issue is resolved. Thank you again for your patience and understanding. Have a great day, Best regards, --- [2026-05-19T15:46:31.952+02:00] (investigating) Chers partenaires, Nous avons identifié un problème avec l'ouverture des liens Adobe sur du logiciel Adobe Digital Editions ainsi que sur les supports de lecture de notre écosystème compatibles (gamme de liseuses compatibles). Le problème est en cours d'analyse par notre équipe technique. Nous vous remercions pour votre patience et votre compréhension. Bien cordialement, ________________ Dear Partners, We have identified an issue with opening Adobe links in Adobe Digital Editions as well as on compatible devices within our ecosystem (range of compatible e-readers). Our technical team is currently investigating the issue. Thank you for your patience and understanding. Best regards, --- [2026-05-19T15:23:05.764+02:00] (investigating) We are currently investigating this issue.

Live Vivlio Outage Reports

Problems reported by engineers using Vivlio. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total

24h agoNothing reportednow

No Vivlio problems reported yet.

Something wrong with Vivlio on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Vivlio

Vivlio exposes 14 monitored components on its status page at status.vivlio.com — Order API, Ecommerce and Website my.vivlio.com among them. Follow Vivlio downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

Over the past 30 days, PulsAPI has measured Vivlio uptime at 100.00%. Response times, incident history, and SLA tracking for Vivlio are available on the PulsAPI dashboard.

Vivlio Status FAQ

Is Vivlio down right now?

PulsAPI checks Vivlio every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Vivlio status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Vivlio is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Vivlio recovers.

How do I check Vivlio uptime history?

PulsAPI tracks Vivlio uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Vivlio.

How fast does PulsAPI detect Vivlio outages?

PulsAPI polls the official Vivlio status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Vivlio components?

Yes. PulsAPI monitors 11 individual Vivlio components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Vivlio goes down?

Yes. Create a PulsAPI account and subscribe to Vivlio. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Vivlio status changes.

How do I report an issue with Vivlio to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Vivlio problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Vivlio?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Vivlio alongside up to 9 other services at pulsapi.com/signup.

Track Vivlio with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Vivlio status changes.

Start free trial