ENGINEup
READS · 24H0 · — ok
VIDEOon
AS OF2026-11-13 21:09 UTC
STATUS / 07
Measured, not declared.
Every number on this page comes from the service's own records for the last 24 hours. Nothing is green because somebody said so.
SURFACES
mvoom.com
This site
LIVE
mvoom.cc — the read, the pieces, the video
Where a URL becomes a recipe, in conversation
LIVE
teardowns.mvoom.com
The public library: every piece measured and published
LIVE
api.mvoom.com — the engine
Up for 4 d · 0 reads waiting
LIVE
@mvoom/cli · @mvoom/sdk · @mvoom/mcp
Published on npm, MIT — they talk to the engine over the versioned HTTP contract
LIVE
READS · LAST 24 HOURS
READS STARTED
0
0 in the last 7 days
FINISHED WITH A RECIPE
—
every read that started, finished
MEDIAN READ
—
From the first request to the signed quote, all passes included
WAITING NOW
0
Reads run one at a time on the current machine; this is the line
VIDEO · LAST 24 HOURS
RENDERS STARTED
0
0 finished · 0 did not · 0 in the queue
MEDIAN RENDER
—
0 frames rendered · measured pace 244 ms per frame
INCIDENTS
20 / 09 / 2026 — every read died after the second pass
First day in public. The production image was missing one of the engine's two bundles, so every read failed at 48% and the chat kept waiting instead of saying so. Fixed the same afternoon: the image now builds both bundles, a probe refuses any image that does not, and the chat hears the failure the moment it happens. This page exists because that failure was found by a person, not by a monitor.