All systems operational
Live: this page ran the checks below when it was requested, Thu, 27 Aug 2026 21:40:06 GMT. There is no snapshot behind it.
Systems
- REST APIapi-sandbox.clobberhq.comAnswers, and refuses an unauthenticated request with the documented invalid_api_key.Operational
- WebSocket feedfeed-sandbox.clobberhq.comAnswers the WebSocket handshake.Operational
- Matching enginesandbox-1The engine and the journal are up, and the cell is accepting commands.Operational
- Journal replicationus-east-1The bucket is 94 commands behind the journal.Operational
- Market dataus-east-1The projection is 0.5 s behind the engine.Operational
- Dashboarddashboard.clobberhq.comServed.Operational
- Documentationdocs.clobberhq.comServed.Operational
What the engine measured about itself
1.38M
commands sequenced in the last 24 hours. Every one of them is on disk, in order, before it is answered.
24 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: 343 ms.
5.0 ms / 8.4 ms
journal fsync, p50 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.
94
commands the off-site copy is behind the journal, right now. This is the recovery point: what a lost machine would cost.
0.5 s
the query side's lag behind the engine, right now. Orders, fills and ledger history are read from there.
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 twenty seconds, read back from Datadog just now.