Vivlio logo

Is Vivlio Down?

SaaSLive status, outages, and incident history

No. Vivlio is up right now.

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

OperationalChecked 3m agoLive · 60s while moving

Know the moment Vivlio breaks

Vivlio is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

Official Vivlio status page
How we know: the official Vivlio status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), 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
Admin Backend
Operational
API » Cloud API
Operational
API » Download API
Operational

8 more components tracked

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

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

See all of them free

Component statuses may change independently during partial outages.

Recent Vivlio Outages & Incidents

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

Commandes en erreur / Error while processing the orderResolved Sep 25, 2026 · 0 minResolved

Chers partenaires, Nous avons identifié un incident qui a commencé le lundi 21/09 à partir de 15h et qui a été résolu le mercredi 23/09 à 9h20. En raison d'un problème de communication entre notre serveur et le serveur de paiement, les commandes ont automatiquement échouées, engendrant un remboursement immédiat pour le client. Nous comptons 118 utilisateurs impactés au total et 77 d'entre-eux ont déjà renouvelé leur commande avec succès. La stratégie de contact des 47 utilisateurs n'ayant pas renouvelé leur commande est en cours de définition. L'équipe support se tient disponible pour vous accompagner et/ou répondre à vos interrogations. Merci de votre compréhension. ___________________ Dear Partners, We have identified an incident that began on Monday, September 21, at 3:00 p.m. and was resolved on Wednesday, September 23, at 9:20 a.m. Due to a communication issue between our server and the payment server, orders automatically failed, resulting in an immediate refund for the customer. A total of 118 users were affected, and 77 of them have already successfully placed their orders again. We are currently determining how to contact the 47 users who have not yet placed their orders again. The support team is available to assist you and/or answer any questions you may have. Thank you for your understanding.

Impossible to authenticateResolved Sep 18, 2026 · 0 minResolved

Chers partenaires, Nous avons identifié un incident ce jour qui a commencé à 13h50. Pendant 1h30, En raison d'un problème lié aux tokens d'authentification, il était impossible de s'authentifier auprès d'une librairie externe. Une centaine d'utilisateurs ont été impactés par cet incident. L'équipe support se tient disponible pour vous accompagner et/ou répondre à vos interrogations. Merci de votre compréhension. ___________________ Dear Partners, We identified an incident today that began at 1:50 p.m. For 1.5 hours, due to an issue with authentication tokens, it was impossible to authenticate with an external library. Approximately 100 users were affected by this incident. The support team is available to assist you and/or answer any questions you may have. Thank you for your understanding.

Database server upgradeScheduled for Sep 15, 2026 · 3h 0mScheduled

The scheduled maintenance has been completed. --- [2026-09-16T01:00:07.549+02:00] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-16T00:00:17.527+02:00] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-09-11T15:57:47.710+02:00] (scheduled) We are upgrading our database server to be able to provide stable and improved performances. This migration will take between 1h and 3h and is schedule at night to minimize user impact. The impact will be visible on the following services: - Ordering of ebook / abook - Admin backend will be unavailable - ONIX ingestion and export will be delayed - Download of ebooks / abooks will degraded - Library (PNB) ordering, loan and download The other services will not be impacted, in particular: - Bookshelf synchronisation - Authentication - DRM services Sorry for the inconvenience. We will do our best to minimize the interruption. You can contact our team at contact@vivlio.com if you have any questions.

Vivlio Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Vivlio incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% averageSep 25

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?

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. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

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%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Vivlio changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Vivlio outages?

PulsAPI reads the official Vivlio status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

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 free account and subscribe to Vivlio: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

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. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Vivlio plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Vivlio with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services