Ethereum logo

Ethereum Network Monitoring

Ethereum is a programmable blockchain that uses proof of stake. ProbeLab crawls the discv5 network of the consensus layer to show client diversity, node locations, cloud hosting and support for upcoming forks. We also check the bootstrap nodes and measure block arrival times on GossipSub.

8,190
8K
Compared to 1 week ago
-1%
Network Size (Consensus)
Nov. 9, 2026, 10 p.m. UTC
Last updated 7 hours ago
Lighthouse
Lighthouse
Dominant Client (Consensus)
Nov. 9, 2026, 10 p.m. UTC
Last updated 7 hours ago
US
US
Dominant Country (Consensus)
Nov. 9, 2026, 10 p.m. UTC
Last updated 7 hours ago
9,560
10K
Compared to 1 week ago
-0%
Network Size (Execution)
Nov. 9, 2026, 10 p.m. UTC
Last updated 7 hours ago
Geth
Geth
Dominant Client (Execution)
Nov. 9, 2026, 10 p.m. UTC
Last updated 7 hours ago
US
US
Dominant Country (Execution)
Nov. 9, 2026, 10 p.m. UTC
Last updated 7 hours ago

Monitored Components

Bootstrappers

Topology

GossipSub

Security

ENR Viewer

Chrono

Core Statistics

Client diversity, infrastructure, and fork support of the consensus layer (discv5 crawl) and the execution layer (discv4 and discv5 crawls).

Active Agents Distribution (24h) Consensus

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

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

Cloud Distribution (24h) Consensus

Cloud Distribution (24h)

Shows how many online peers run in a cloud data center. One value is the average number of online peers per crawl in the 24 hours up to the latest crawl. A peer is in Cloud if ipregistry.co marks its IP address as a cloud provider address. All other peers are in Non-Cloud, also the peers without IP address data.

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.

Snapshot of clients running with hosting providers

Cloud Distribution (24h) Execution

Cloud Distribution (24h)

Shows how many online peers run in a cloud data center. One value is the average number of online peers per crawl in the 24 hours up to the latest crawl. A peer is in Cloud if ipregistry.co marks its IP address as a cloud provider address. All other peers are in Non-Cloud, also the peers without IP address data.

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.

Snapshot of clients running with hosting providers

Fork Digest Over Time Consensus

Fork Digest 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 ...

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 Version Over Time Consensus

Next Fork Version 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 ...

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 ...

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

Related Work

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

YouTube thumbnail: 7EnDYwcMGq4
Talk

devp2p, libp2p, ethp2p - Untangling Ethereum’s Networking Stack

Ethereum's execution layer runs devp2p: RLPx transport, capability negotiation, and request-response subprotocols carrying the mempool and sync. Its consensus layer runs libp2p, a modular general-purpose …

YouTube thumbnail: tB2k2axL6DE
Talk

What can Ethereum learn from other networks?

Ethereum's peer-to-peer layer was designed for a protocol that looked very different from the one we run today, and it did its job well. But …

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) …