Lookout · Arkiv node
Reading the node…
Catching up to the network
Next actions
- Reading the node…
When the disk fills up
Drag to see when that budget runs out. Below the alert threshold the real alert fires, so you can test the path to your phone.
Where the space goes
Actual allocated bytes, not apparent file sizes. Hover a name for the technical term.
What expires when
Each dot is a slice of the entities on this node, placed by when Arkiv deletes them (log scale). They drift left in real time and vanish at "now".
Stored entities
Last hour
■ entity data size ■ live entities
Calls to this node
| Method | Calls/min | Calls | Failed | Average | Just now | Typical | Slowest 5% | Slowest 1% |
|---|---|---|---|---|---|---|---|---|
| No calls yet. | ||||||||
Calls and failures count since Lookout started, leaving out the queries its own spec checks send to fail on purpose. Arkiv's own methods are in green. The node logs no reason for a failed call; the For Arkiv tab shows which query constructs it rejects.
In Arkiv's RPC pool
Pick any node in the pool to see how the load balancer sees it, or set LOOKOUT_PROVIDER to your provider address.
The outside view comes from the same public feed as nodes.arkiv.network; Lookout puts it next to what it measures inside your node.
Query language: this node vs the spec
Show every check
Live checks of arkiv_query, re-run every 10 minutes. IDs match Arkiv's conformance tracker, which is written from the code; this is what your node actually does.
Slow-query finder private
Run npm run probe against your own node. Results stay in ./private, are only served on localhost, and go to Arkiv privately, never in public.