Headers served
610.6M
Current height
7 870 548
Total Bridges
198
Build version
v0.26.4
Make this Notebook Trusted to load map: File -> Trust Notebook
No OTEL
With OTEL
Node Categories Distribution
Category A:
{catA} nodes
({catA_pct})
Category B:
{catB} nodes
({catB_pct})
Category C:
{catC} nodes
({catC_pct})
Category D:
{catD} nodes
({catD_pct})
Category E:
{catE} nodes
({catE_pct})
Headers Served
Bridges by Continent
Version Distribution
Anomalies timeline
Major anomalies
Last Anomalies
process_runtime - runtime of the node process: goroutines, heap usage, GC cycles and pauses. Fast growth can indicate load spikes, leaks, or runaway routines.hdr - header sync metrics: current chain height, highest synced header, and block lag. Sustained lag suggests network issues, stuck peers, or throttled I/O.
node_runtime - uptime since last restart. Resets to zero on restart; frequent resets point to instability or crashes.
eds_store_put_time - latency to persist data (EDS/chunks). Rising p95/p99 means disk bottlenecks, fsync pressure, or high I/O contention.
shrex_nd_server_responses_total / shrex_eds_server_responses_total - counts of served ND/EDS requests. Surges mean high demand; drops with timeouts may indicate network or resource limits.
Loading...
Potential Risk
process_runtime - monitor goroutines, heap growth, and GC activity to catch memory pressure early.hdr - track sync lag vs. chain height to detect falling behind the network in real time.
node_runtime - uptime trend; frequent resets correlate with crashes, OOM, or operator restarts.
eds_store_put_time - persistent write latency; spikes often map to slow disks or saturated I/O paths.
shrex ND/EDS responses - workload level for serving data. Use together with errors/timeouts to spot networking or capacity limits.
No risks at the moment.