Ensuring reachability of referenced nodes shared within the network is critical.
Shows the number of node records in the routing tables of all nodes that our Nebula crawler visited, per crawl. Reachable counts the records of nodes that the crawler could reach, Unreachable the records of nodes that it could not reach (stale records). A node is reachable if it answered the discv5 requests of the crawler without an error. Note that nodes running behind a NAT are counted as unreachable even though they may be online. For instance, if a node’s record is present in the routing tables of 100 other nodes and the node is reachable, the plot will reflect an increase of 100 in the Reachable series.
On 2026-01-12 (the vertical line), we changed the deduplication logic when queuing peers to crawl. We crawl the discv5 DHT which indexes Ethereum Node Records. Each record contains a NodeID among other things. Before that date we skipped crawling records whose NodeID we had already seen and crawled before. However, the newly discovered ENR for the same NodeID could in theory contain more up-to-date information about the node's network addresses. Therefore, after that date we started to probe every ENR that we can find even if we had probed the NodeID before during that same network crawl.
Reachable vs Unreachable DHT Records Over Time