HORIZEN IT SERVICES
System Status

We run on what we sell.

This page is derived from Horizen's own operations substrate — the same native collectors and content-addressed machinery we point at client fleets. Nothing below is hand-typed: every number came out of a live endpoint, and the provenance line at the bottom says exactly which fetch produced it.

Operations door — UP snapshot

Snapshot baked at publish time: fetched 2026-07-04 20:14:53 GMT from the substrate door (/health + /room/status). If your browser can reach the door, the tiles refresh live below.

forge chassis
7900xt
Windows 10 22H2 · build 19045.6809
chassis uptime
8.1 d
no pending reboot at snapshot
disk C: free
1819 GB
of 4000 GB (45.5% free)
door service uptime
4625 s
substrate door on :6969
content-addressed blobs
8,590
room store, fingerprint-verified
crystal projection
byte-exact
AMD Radeon RX 7900 XT · Vulkan · 3.8 MB resident · 7 ms
kv-mirror tokens saved
53,266,566
135 cache entries · 110 hits
tool calls served
306
this door boot
provenance · snapshot fetched 2026-07-04 20:14:53 GMT from http://[::1]:6969 · /health receipt ◇4448739e · /room/status receipt ◇4b45bcdf · collector: mythpath-door (native Rust: sysinfo + registry + WMI) · baked into this page at publish; the page itself is a content-addressed object.

How this page is made

The numbers above are collected by the same native agent surface we deploy to client endpoints — posture and health read straight from the OS, room metrics read from the substrate door. At publish time we fetch the door, bake the snapshot into this page, and content-address the result. In the browser, a small script then tries to re-fetch /room/status live; when the door is not reachable from your network (it is not exposed to the public internet, and it does not emit CORS headers for third-party origins), the badge above stays snapshot and you are seeing the publish-time truth, labeled as such. Per-client fleet detail lives behind the portal, never on a public page.