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 November 9, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked just nowLive · every 60s

Know the moment Vivlio breaks

Vivlio is healthy right now. We keep checking (every 60 seconds) and email you when 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), and outage reports from engineers. How PulsAPI monitoring works

Status report

Vivlio Status Summary

As of 12:44 UTC on 9 November 2026, Vivlio is operational. PulsAPI checked Vivlio's official status page and found 11 of 11 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for Vivlio, counting degraded performance as up. The latest incident, "All our web shops are unavailable", was on Oct 26, 2026 and lasted 25 min.

Cite as: PulsAPI, “Vivlio status”, checked 9 November 2026, 12:44 UTC. https://www.pulsapi.com/services/vivlio

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.

All our web shops are unavailableResolved Oct 26, 2026 · 25 minResolved

This incident has been resolved. --- [2026-10-26T08:38:27.546+01:00] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-10-26T08:38:06.434+01:00] (investigating) We are currently investigating this issue.

Incident sur le paiement / Payment issueResolved Oct 2, 2026 · 0 minResolved

Chers partenaires, Un incident est survenu auprès de notre prestataire de paiement le 2 octobre 2026 vers 15h. L'incident a été résolu ce jour à 16h15. L'impact pour les utilisateurs durant cette période : - Il était impossible de finaliser la commande - La validation du paiement était en en erreur - La validation du paiement pouvait prendre du temps Des retry ont été effectués et les commandes ont finalement été honorées. Nous vous remercions pour votre compréhension. Bien cordialement, _________________________ Dear partners, An incident occurred with our payment provider on October 2, 2026, around 3:00 p.m. The incident was resolved today at 4:15 p.m. Impact on users during this period: - Orders could not be completed - Payment validation resulted in errors - Payment validation could take longer than usual Retries were carried out, and the orders were finally fulfilled. Thank you for your understanding. Best regards,

Délais d'envoi des exports / Delay for submitting exportsResolved Oct 1, 2026 · 6h 18mResolved

Chers partenaires, La situation est désormais revenue à la normale. Les exports sont de nouveau à jour et les livres qui devaient être publiés ce jour ont bien été intégrés. Notre équipe support se tient disponible si vous avez besoin d'accompagnement. Bien cordialement, ___________________________ Dear Partners, The situation has now returned to normal. Exports are back on track, and the books that were scheduled to be published today have been successfully added. Our support team is available if you need assistance. Best regards, --- [2026-10-01T12:11:19.265+02:00] (identified) Cet incident fait référence à l'incident survenu le 01/10/2026 / This incident refers to the incident that occured on October 1, 2026. Chers partenaires, Suite à l'incident survenu plus tôt dans la journée, nous souhaitons vous informer que nos exports de métadonnées rencontrent des délais d'envois plus long que la normale. Cela peut engendrer des délais pour l'affichage de nouveautés, d'affichage des promotions ou encore des erreurs de validation pour les précommandes. Une nouvelle tentative des précommandes sera effectuée dès 12h30. Quant aux exports de métadonnées, ils seront bientôt revenus à la normale. Merci pour votre compréhension. Bien cordialement, ___________________________ Dear Partners, Following the incident that occurred earlier today, we would like to inform you that our metadata exports are experiencing longer-than-usual processing times. This may result in delays in the display of new items and promotions, as well as validation errors for pre-orders. We will attempt to process pre-orders again starting at 12:30 p.m. As for metadata exports, they will soon return to normal. Thank you for your understanding. Best regards, --- [2026-10-01T12:10:28.818+02:00] (identified) Cet incident fait référence à l'incident survenu le 01/10/2026 / This incident refers to the incident that occured on October 1, 2026. Chers partenaires, Suite à l'incident survenu plus tôt dans la journée, nous souhaitons vous informer que nos exports de métadonnées rencontrent des délais d'envois plus long que la normale. Cela peut engendrer des délais pour l'affichage de nouveautés, d'affichage des promotions ou encore des erreurs de validation pour les précommandes. Une nouvelle tentative des précommandes sera effectuée dès 12h30. Quant aux exports de métadonnées, ils seront bientôt revenus à la normale. Merci pour votre compréhension. Bien cordialement, ___________________________ Dear Partners, Following the incident that occurred earlier today, we would like to inform you that our metadata exports are experiencing longer-than-usual processing times. This may result in delays in the display of new items and promotions, as well as validation errors for pre-orders. We will attempt to process pre-orders again starting at 12:30 p.m. As for metadata exports, they will soon return to normal. Thank you for your understanding. Best regards,

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 history91 days observed
Aug 11100.00% average · 1 day with incidentsNov 9

Going further back: Vivlio uptime by month and every recorded Vivlio outage.

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 it every 60 seconds.

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 it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

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

2660+ 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