7 datasets
The node database of achow101's Bitcoin DNS seeder as a text dump, one line per known address with reachability over several time windows, last-seen time, height, services, version and user agent. Written continuously by the dnsseedrs crawler behind the seeder, which asks nodes for addresses and keeps retrying each one. Useful for node counts per network and software adoption; a single live snapshot from one vantage point, without history.
Daily snapshots of the peers connected to KIT's Bitcoin monitoring nodes, one JSON file per day with each peer's services, version, user agent, autonomous system, coarse location, relay statistics and latency. The monitor connects to reachable nodes and records what they relay, following the group's published methodology. Useful for studying the node population and propagation over many years; peer IP addresses are anonymised.
The node database of Will Clark's Bitcoin DNS seeder seed.bitcoin.fish.foo as a text dump, one line per known address with reachability over several time windows, height, services, version, user agent and retry statistics. Written continuously by a dnsseedrs crawler behind the seeder. Useful as an independent vantage point, since this seeder is not hardcoded in Bitcoin Core; a single live snapshot without history.
Exports of reachable Bitcoin nodes from the Bitnod.es node explorer, one CSV file per day with each node's address, port, country, ISP, services, protocol version, user agent and block height, covering IPv4, IPv6, Tor and I2P addresses. The site runs the bitnodes crawler and publishes a cumulative last-seen export per day. Useful for node counts by country, provider and software version; only listening nodes are included.
Snapshots of reachable Bitcoin nodes from a revival of the bitnodes.io crawler, each a JSON document listing every node with version, user agent, services and height across IPv4, IPv6, Tor, I2P and CJDNS, with monthly archives adding geolocation and ASN. The crawler recursively requests addresses from nodes and publishes snapshots through a rate-limited public API and an archive page. Useful for node counts by network, country and software; only listening nodes are counted.
Daily exports of the address manager of Bitcoin Core nodes via the getrawaddrman RPC, one JSON file per node with every known address and its metadata, with history in the git log. A scheduled job fetches the exports from the peer.observer nodes and commits them. Useful for studying address propagation and addrman churn; the nodes are a small sample with their own connectivity.
Daily time series on the health of Bitcoin's P2P network: reachable nodes by network type, unique and long-term reachable node estimates, and the quality of addresses served by each DNS seed. Produced by virtu's p2p-metrics- exporter, which crawls the network and queries the DNS seeds. Useful for tracking node counts and DNS seed quality over time; only listening nodes are counted.