How much of the Kaspa network answers, whether it keeps up, what it runs, and how that is changing.
Right now
From the latest full crawl, finished
Every node we know of, one dot each
The nodes we could reach and talk to. Nodes that don't accept incoming connections can't be reached this way, so the network is larger: the blue dots are the private nodes our sensors hear from.
19,184 addresses advertised
13,638 tried
294 answered
How we count
Each node counted onceWe tell nodes apart by the ID each one announces when we connect. That's what a node tells us, not something we can verify.
8 second addressesAnswers from a node we had already counted, at another address such as both IPv4 and IPv6.
4 tools, not nodesOur New York, Nuremberg and Singapore sensors and 1 crawler run by someone else. A tool that doesn't say what it is looks like a node to us, and is counted as one.
Over time
One reading a day, from each day's last full crawl
Public nodes
Down 1 since 30 Sep, when there were 283. On an average day 8 nodes arrive and 8 leave. Each dot under the line is one of them, since 1 Oct, when records start. Dashed days are approximate: those crawls lost a few answers before saving them.
Software versions
Share of public nodes on each release, since 30 Sep, when records start.
kaspad 2.1.0kaspad 2.0.1all other versions
Hosting
The three biggest hosting providers run 32% of public nodes, up from 29% on 20 Jul. Half of all public nodes sit with 14 providers. Some early days come from crawls that lost a few answers before saving them, which barely moves a share.
Is your node reachable?
Test whether an address accepts Kaspa connections from the outside right now, and whether it follows the network.