StatusService status
Novus Convert is a static site with no conversion backend. This page explains what that architecture means for availability, what can genuinely break, and how to check for yourself.
01What this page reports — and what it cannot
It publishes no uptime percentage and no incident feed, because it would not be able to earn either. This page is a pre-rendered file served from the same static deployment as the rest of the site: if you are reading it, that deployment is up, and if the deployment were down you would not be reading it. A green light drawn by the thing it is supposed to be monitoring is decoration, not a status report. What follows instead is an honest description of the failure modes that exist, so you can tell which one you are looking at.
02There is no conversion backend to go down
Conversions and compressions run in your browser on your own device. There is no conversion server, no job queue, and no processing API — so there is no class of outage where the site loads but conversions are unavailable because something behind it is unhealthy. Once a page and its engine have loaded, the conversion depends on your device and nothing else.
03The one request that reaches a server
A single endpoint runs on request: it reports whether your connection is in a jurisdiction that requires prior consent before advertising storage, so the cookie banner can state what is actually running. It is never cached, and it fails closed — if it errors or answers with something unexpected, consent is treated as required and non-essential storage stays off. A failure there suppresses advertising; it does not affect conversion.
04What can actually degrade
Four things, in rough order of likelihood. The hosting CDN can have a regional incident, which makes pages slow or unreachable. A first-time engine download needs a working network, so a flaky connection can stall the first conversion of a given type while later ones are fine. Your browser tab has finite memory, so a very large file can fail on a constrained device and succeed on a desktop. And the third-party advertising and analytics scripts have their own availability, entirely separate from whether the converter works.
05How to check in under a minute
Load the converter and drop in a small file — a successful conversion proves the engine path end to end. If a page will not load at all, try a hard reload to bypass the cached service worker. If a specific conversion fails, the error under the file names the cause the engine reported rather than a generic message. If you need a known-good sample to test with, examples.novusstreamsolutions.com publishes files in most supported formats.
06Being offline is a supported state
If you have used Convert or Compress online once, the interface and the engines you loaded are cached, and they keep working with no network. Losing connectivity therefore looks like an outage on most sites and looks like normal operation here — pages and codecs you have never visited still need a connection once.
07Reporting something broken
Email convert@novusstreamsolutions.com with the page URL, your browser and version, and — for a conversion failure — the input format, the output you selected, the file size, and the exact error text shown under the file. Never attach a confidential file to a first message; describe it and we will arrange a safe way to reproduce the problem.
08What changed recently
Releases and their contents are recorded in the changelog, which is the closest thing this site has to a status history: it says what shipped and when, rather than asserting a number nobody can verify.
