Ethereum logo

Execution Layer Topology

discv4 + discv5 DHTs

Key metrics on network structure, geographic peer distribution, client diversity, and fork support across the Ethereum Execution Layer. We crawl the discv4 and the discv5 DHTs and count each node once. A node counts if its eth handshake or its node record (ENR) shows an Ethereum mainnet fork ID.

Geographic Distribution

Node IP address to country mapping, based on data sourced from https://ipregistry.co/.

Country Distribution (24h) Execution

Country Distribution (24h)

Shows the online peers per country, as the average number per crawl in the 24 hours up to the latest crawl. The color of a country shows this number, and the text below the map shows the sum over all countries. Peers without a known country are not on the map. The country of a peer comes from the IP address mapping of ipregistry.co. Select an agent type to show only the peers of that type. Note that nodes behind NAT cannot be measured and geographic data may not be fully accurate due to VPNs or proxy usage.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Loading ...

Geolocation Over Time Execution

Geolocation Over Time

Shows the number of online peers per country in each crawl. The six countries with the most peers in the selected time range have their own series. Other holds the rest, including the peers without a known country. The country of a peer comes from the IP address mapping of ipregistry.co. Select an agent type to show only the peers of that type.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

DHT Server geolocation per agent version over time

Countries Distribution (24h) Execution

Countries Distribution (24h)

Shows the online peers per country, as the average number per crawl in the 24 hours up to the latest crawl. The bars show the ten countries with the most peers by their two-letter country code. Hover over a bar to see the country name. other holds the rest, including the peers without a known country. The label on each bar is its share of all peers. The country of a peer comes from the IP address mapping of ipregistry.co. Select an agent type to show only the peers of that type.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Snapshot of active agents geolocation within the last 24hrs

Agent Version Distributions

Network structure representation through client and agent distribution.

Client Diversity Trend Execution

Client Diversity Trend

Shows the number of online peers per agent type (client software) in each crawl. The areas are stacked, so their top is the number of all online peers. The six agent types with the most peers in the selected time range have their own series. Other contains all other agent types.

The Unknown category represents nodes where the agent version could not be retrieved through the libp2p identify protocol. This situation can occur due to various reasons, such as the node terminating the connection before completing the full protocol negotiation.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Client participation over time

Active Agents Distribution (24h) Execution

Active Agents Distribution (24h)

Shows the client software (agent type) of the online peers. One value is the average number of online peers per crawl in the 24 hours up to the latest crawl. The six agent types with the most peers are shown separately. Other contains all other agent types. The percentages are shares of all online peers.

Our Nebula crawler gets the agent version of a peer through the libp2p identify protocol. Unknown contains the peers where this did not work, for example because the peer closed the connection before the protocol negotiation completed.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Snapshot of active agents within the last 24hrs

Agent Versions Trend Execution

Agent Versions Trend

Shows the number of online peers per version of one agent type (client software) in each crawl. The areas are stacked, so their top is the number of online peers of this agent type. Select the agent type in the menu. The menu lists the six agent types with the most peers in the selected time range, and the first one is the default. The six most common versions in the selected time range have their own series. Other contains all other versions and the peers where we cannot read a version from the agent version.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Agent version participation over time

Agent Version Distribution (24h) Execution

Agent Version Distribution (24h)

Shows the versions of one agent type (client software) among the online peers. One value is the average number of online peers per crawl in the 24 hours up to the latest crawl. Select the agent type in the menu. The menu lists the six agent types with the most peers, and the first one is the default. The eight most common versions are shown separately. Other contains all other versions and the peers where we cannot read a version from the agent version. The percentages are shares of all peers of the selected agent type.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Snapshot of versions active per agent within the last 24hrs

Protocols & Infrastructure

Discovery protocols, devp2p capabilities (e.g. eth/69, snap/1) per agent version, and infrastructure providers.

Discovery Protocols Over Time Execution

Discovery Protocols Over Time

Execution layer clients find peers through the discv4 DHT, the discv5 DHT, or both. We crawl both DHTs and count each node once, by its node key. This chart shows in which of the two DHTs a node answered our crawler. It shows how far the clients have moved from discv4 to discv5.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Count of nodes per DHT in which our crawlers reached them

Cloud Provider Dependency Over Time Execution

Cloud Provider Dependency Over Time

Shows the number of online peers per cloud provider in each crawl. The areas are stacked, so their top is the number of all online peers. The providers with the most peers in the selected time range have their own series. The other providers are in Other. Non-Cloud contains the peers that do not run in a cloud data center and the peers without IP address data. The cloud flag and the provider of an IP address come from ipregistry.co.

Select an agent type in the menu to see only its peers.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Count of nodes deployed per cloud provider and per agent

Supported Protocols Over Time Execution

Supported Protocols Over Time

Shows the number of online peers per crawl that support a protocol, for the 40 protocols with the most peers in the selected time range. A peer counts once for each protocol that it supports, so the lines do not add up to the number of peers. The protocol list of a peer comes from the libp2p identify exchange. Peers without a known protocol list are not in this chart. Select an agent type in the menu to see only its peers.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Number of peers supporting the top 40 protocols in the network.

Fork Support

EIP-2124 fork IDs that the nodes announce: the current fork and the next fork that they know about.

Fork ID Over Time Execution

Fork ID Over Time

Shows the number of online nodes per fork digest over time, as the nodes announce in their node record (ENR). The fork digest identifies the fork that a node follows, so the chart shows how the nodes move to a new fork, for example from Electra to Fulu. Fulu BPO1 and Fulu BPO2 are the blob-parameter-only forks after Fulu. Only nodes with a known Ethereum mainnet fork digest are counted. The data comes from our Nebula crawls of the discv5 DHT, with one value per crawl, where one node is one IP address and port. Select an agent type to see only the nodes that run this client.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Loading ...

Next Fork Over Time Execution

Next Fork Over Time

Shows the number of online nodes per next fork version over time, as the nodes announce in their node record (ENR). A node announces the version of the next fork that its software has scheduled. If no fork is scheduled, it announces the version of its current fork. So the chart shows how many nodes run software that is ready for an upcoming fork, for example Gloas. Only nodes with a known Ethereum mainnet fork digest are counted. The data comes from our Nebula crawls of the discv5 DHT, with one value per crawl, where one node is one IP address and port. Select an agent type to see only the nodes that run this client.

Data is provided as is, without warranty. Scraping and automated bulk extraction are not permitted. See our Terms of Use.

Loading ...

Related Work

Blog posts, papers and talks by the ProbeLab team about Ethereum.

ArXiv Preprint
Paper

Quantifying Ethereum Energy Consumption via Network Mapping

Ethereum’s electricity use fell by about 99.95% after the network moved from proof of work to proof of stake. Service providers still need to report …

From rawpixel.com / Freepik
Blog post

ProbeLab's 2025 Review and 2026 Outlook

What we've achieved in 2025 and what we're targeting in 2026

MIDDLEWARE '25 Conference Paper
Paper

PANDAS: Peer-to-peer, Adaptive Networking Allowing Data Availability Sampling within Ethereum Consensus Timebounds

Layer-2 protocols such as rollups can help address Ethereum's throughput limits. An efficient data availability layer is key for layer-2 support in Ethereum, but broadcast …

SIGMETRICS '26 Conference Paper
Paper

Multiple Sides of 36 Coins: Measuring Peer-to-Peer Infrastructure Across Cryptocurrencies

Blockchain technologies underpin an expanding ecosystem of decentralized applications, financial systems, and infrastructure. However, the fundamental networking layer that sustains these systems, the peer-to-peer (P2P) …

Ethereum Logo Blog Hero
Blog post

Behind the Scenes of Ethereum's Pectra Upgrade: A Data-Driven Analysis

The Pectra Upgrade in Numbers from the P2P Network.

Springer Cluster Computing Journal Article
Paper

The Impact of Connectivity and Software in Ethereum Validator Performance

Modern public blockchains like Ethereum rely on p2p networks to run distributed and censorship-resistant applications. With its wide adoption, it operates as a highly critical …