All systems operational
Live: this page ran the checks below when it was requested, Mon, 14 Sep 2026 18:43:54 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.comRefuses an unauthenticated handshake with the documented invalid_api_key.Operational
- Webhook deliveryus-east-1The dispatcher completed a pass 1.7 s ago. 23 deliveries sent since this cell started.Operational
- Journal replicationus-east-1The bucket is 111 commands behind the journal, about 6.3 s of writing.Operational
- Market dataus-east-1The projection is 0.3 s behind the engine.Operational
- 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.
1.63M
commands sequenced in the last 24 hours. Every one of them is on disk, in order, before it is answered.
12 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: 50 ms.
2.9 ms / 6.7 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.
1.7 s
the widest gap between two clean passes of the webhook dispatcher in the last 30 minutes. It reads the queue every two seconds whether or not anything is due, so this number is how stale the worst reading of it got, not how long delivery takes. It has sent 23 deliveries since this cell started. Every event is a durable row before it is a POST.
0.3 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 minute, read back just now.