Web3 Is Built on IP Addresses: Mapping 11,000+ Blockchain Nodes Across 8 Networks

A blockchain is “decentralized” in software, but it still runs on hardware: real machines, in real data centers, reachable at real IP addresses. Strip away the abstraction and every public network — Solana, IPFS, Polkadot, Monero — is ultimately a set of peers advertising routable addresses so the rest of the network can find them. That is the layer WorldIP.io was built to map, and today we are turning it on for web3.

We have added a new web3 node map that identifies which IP addresses are running blockchain and peer-to-peer nodes, and folds that signal into the same per-IP intelligence we already publish for the rest of the internet. At launch it covers 8 decentralized networks and more than 11,000 nodes, and every single one links straight through to its full IP report.

What is actually new

• A browsable node directory at /web3. One page per network shows the live node count and a map of where those nodes physically live, sized by country and coloured by the dominant network.
• Per-network pages such as /web3/solana and /web3/ipfs that list every node address — each one annotated with its hosting network (ASN), operator, and country, and linked to its own /ip page.
• A decentralization report that measures how concentrated each network really is at the infrastructure level — what share of its nodes sit behind a single hosting provider or in a single country.
• A “web3 footprint” section on every ASN and country page, so you can see how much blockchain infrastructure a given network or jurisdiction hosts.

The difference: IP intelligence applied to web3

Plenty of dashboards will tell you a network has, say, a few thousand nodes. The piece almost nobody joins up is which addresses those are, and what those addresses actually are. That join is exactly what we do best.

For every node we observe, we resolve the full chain of facts we already maintain for the entire IPv4 space: IP → ASN → organization → country, plus reverse DNS and routing. So a raw peer list stops being a column of numbers and becomes a readable picture of where a decentralized network really lives — which clouds carry it, which countries concentrate it, and whether any single address is taking part.

Crucially, this is a neutral, informational signal. Running a node is legitimate participatory infrastructure, not abuse, so the web3 tag is deliberately kept out of an IP’s reputation score. It never raises or lowers an address’s trust score; it simply tells you something concrete about what that address does.

Eight networks, mapped on day one

At launch the directory spans gossip-based chains, content and storage networks, and data-availability layers:

• Solana — cluster gossip + RPC nodes (the largest set, several thousand reachable peers).
• IPFS — libp2p content peers, the most geographically spread network we track, across dozens of countries and hundreds of ASNs.
• Polkadot — relay-chain nodes.
• Arweave — permaweb storage peers.
• Monero — remote and P2P nodes.
• Avail and Celestia — data-availability network nodes.
• Filecoin — storage providers.

Each per-network page carries a live census — for example, the Solana directory currently lists thousands of unique addresses spread across dozens of countries and a couple of hundred distinct networks. Because we re-take the census daily, the counts track reality as machines join and leave.

How decentralized is “decentralized”?

The headline promise of these networks is that no single party controls them. At the protocol level that is true. At the hosting level it is a measurable question — and the answer is often more concentrated than the marketing suggests.

The decentralization report ranks each network by the share of its nodes that run on a single top hosting provider and in a single top country. A handful of familiar names — the big public clouds and a few large European hosters — carry a striking fraction of supposedly distributed infrastructure. Lower top-provider and top-country shares mean a genuinely more decentralized network; the report lets you compare them side by side and judge for yourself.

Where the data comes from

Decentralized networks are public by design. Every node has to advertise a reachable address — through gossip and distributed hash tables — or no peer could ever connect to it. Seeing a network’s nodes is not a leak or a flaw; it is the network operating exactly as intended, and the same information any other participant sees.

We collect those peer lists from each project’s own published feeds, supplement them with our own discovery crawler where a project has no public list, normalize everything to IP addresses, and store both a lookup table and a daily census so we can show change over time. Full per-network sources and attribution live on the data sources page linked from the map.

Try it

Start at the web3 node map, open a network like Solana or IPFS to browse its nodes, and read the decentralization report to see how concentrated they really are. Or look up any IP the normal way — if it runs a node, you will now see a web3 badge sitting right alongside its geolocation, ASN, routing, and reputation. It is the same neutral, first-party IP intelligence we have always published, now extended to the networks that claim to need no servers at all.