2 systems are down
Live: this page ran the checks below when it was requested, Mon, 05 Oct 2026 23:29:39 GMT. There is no snapshot behind it.
Systems
- REST APIapi-sandbox.clobberhq.comThe health endpoint answered 530.Down
- WebSocket feedfeed-sandbox.clobberhq.comThe feed answered 530 to a handshake.Down
- Journal replicationus-east-1No reading for the shipping lag.No reading
- Market dataus-east-1No reading for the projection.No reading
- Dashboarddashboard.clobberhq.comServed.Operational
- Documentationdocs.clobberhq.comServed.Operational
What the engine measured about itself
The engine is not probed from outside: it answers through the surfaces above, not on a hostname of its own. These are its own measurements, and each carries the window it was taken over.
574,883
commands sequenced in the last 24 hours. Every one of them is on disk, in order, before it is answered.
7.7 ms
p99 from request to the engine's answer, averaged over the last 24 hours. The answer already carries the fills, because it is the engine's. Worst five minutes in the window: 25 ms.
2.8 ms / 5.1 ms
journal fsync, mean and p99 over the last 24 hours. This is the floor under the number above, and it is set by the disk.
0
ledger conservation violations in the last 24 hours. The engine re-derives every balance from its entries and compares.
Every line above came out of a check that ran on this request: the systems are probed from this server over the same public hostnames your code uses, and a system is green because it answered, not because anyone believed it would. The measurements are the cell's own, pushed every minute, read back just now.