Filecoin logo

GossipSub

Key metrics on the Filecoin pubsub network

Bandwidth consumption statistics, Message bandwidth consumption, Number of duplicates, Block arrival times.

Bandwidth

Bandwidth consumption breakdown per direction and message type

Inbound Outbound Bandwidth Usage

Inbound Outbound Bandwidth Usage

Shows the GossipSub bandwidth of our Hermes node in kilobytes per second (kB/s), averaged over 5-minute intervals, per direction:

  • In: messages and control messages that our node received, including duplicate copies of messages.
  • Out: messages and control messages that our node sent.
  • Drop: messages and control messages that our node dropped instead of sending them.

The size of the IHAVE, IWANT and IDONTWANT control messages is an estimate from the number of message IDs in them. Subscriptions, GRAFT and PRUNE messages are not included. Vertical lines mark a new deployment of our Hermes node.

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

Bandwidth Usage in Kilobytes/s agg. in 5m intervals

Bandwidth Usage by Message Type

Bandwidth Usage by Message Type

Shows the GossipSub bandwidth of our Hermes node per message type in kilobytes per second (kB/s), averaged over 5-minute intervals:

  • Deliver: the first copy of a message that our node received and delivered after validation.
  • Duplicated: more copies of a message that our node already had.
  • Msg: messages that our node sent to its peers.
  • Ihave and Iwant: control messages. Their size is an estimate from the number of message IDs in them.

The direction menu shows only received (Inbound) or sent (Outbound) traffic, or all traffic (Any Direction). Vertical lines mark a new deployment of our Hermes node.

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

Insights into the share of each messages bandwidth consumption

Bandwidth Usage Distribution

Bandwidth Usage Distribution

Shows the share of each message type or topic in the GossipSub bandwidth of our Hermes node over the latest 24 hours of data. Hover over a slice to see its share in percent.

  • By Type shows the message types: deliver is the first copy of a message that our node received, duplicated are more copies of a message that our node already had, msg are messages that our node sent, and ihave and iwant are control messages.
  • By Topic shows the GossipSub topics.

The second menu selects the direction: Inbound (received), Outbound (sent), or Any Direction, where each slice name starts with in or out. Control messages that our node dropped are not included.

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

Loading...

Control Messages

Control message distribution over time for each topic

Control RPCs Received by GossipSub

Control RPCs Received by GossipSub

Shows how many GossipSub control messages per second our Hermes node received (in) and sent (out), per 5-minute interval. ihave counts the IHAVE messages, in which a peer announces the IDs of messages that it has. iwant counts the message IDs that peers asked for in IWANT messages, not the number of IWANT messages. Vertical lines mark a new deployment of our Hermes node.

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

Loading ...

Control Messages Received by GossipSub

Control Messages Received by GossipSub

Shows how many message IDs per second our Hermes node received (in) and sent (out) in GossipSub control messages, per 5-minute interval. In an IHAVE message (ihave), a peer announces the IDs of messages that it has. In an IWANT message (iwant), a peer asks for messages by their IDs. The topic menu shows only the message IDs of one topic. Vertical lines mark a new deployment of our Hermes node.

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

Loading ...

Duplicates

Duplicate message statistics per topic, geographic distribution and client implementation

Duplicates Received by GossipSub peers

Duplicates Received by GossipSub peers

Shows, per topic and per 5-minute interval, the number of different messages of which our Hermes node received at least one duplicate. A duplicate is one more copy of a message that our node already received. A message counts only once per interval, also when more duplicates of it arrived. Vertical lines mark a new deployment of our Hermes node.

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

Total number of duplicates received by our node over time.

Duplicates Per Topic CDF

Duplicates Per Topic CDF

Shows the distribution of the number of duplicates per message for each topic on the selected day. A duplicate is one more copy of a message that our Hermes node already received. The x-axis shows how many duplicates of a message our node received. The y-axis shows the share of unique messages, identified by their message IDs, with this number of duplicates or fewer. Click a topic in the legend to show or hide it, and use the date picker to select another day.

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

Loading ...

Time to First Duplicate

Time to First Duplicate

Shows the distribution of the time to the first duplicate per topic on the selected day. This is the time in milliseconds from the moment our Hermes node delivered a message to the moment the first duplicate of this message arrived. A duplicate is one more copy of a message that our node already received. Only messages with at least one duplicate count. Messages whose first duplicate arrived before our node delivered the message, for example during validation, are not included. The x-axis shows the first 2 seconds. The tooltip shows the number of samples, which is the number of messages of each topic. Click a topic in the legend to show or hide it, and use the date picker to select another day.

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

CDF of how long it took for the first duplicate to arrive.

Duplicate Message Sizes Per Topic CDF

Duplicate Message Sizes Per Topic CDF

Shows the distribution of message sizes per topic on the selected day. Each message that our Hermes node received and delivered counts once, by its message ID, also when it had no duplicates. The x-axis shows the size in kB (1 kB = 1,024 bytes). The y-axis shows the share of messages of this size or smaller. The tooltip shows the number of samples, which is the number of messages of each topic. Click a topic in the legend to show or hide it, and use the date picker to select another day.

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

Loading ...

Msg Size / Count Correlation

Msg Size / Count Correlation

Under the same network bandwidth, larger messages take longer to be fully transmitted between peers. Since a peer can only detect a message duplicate after downloading it completely, the likelihood of receiving duplicates increases with message size.

This heatmap shows how the size of the messages in one topic relates to the number of duplicates that our Hermes node received of them on the selected day. Each cell shows the number of unique messages with this size and this number of duplicates. The x-axis groups the message size in steps of 20 kB (1 kB = 1,024 bytes). The y-axis shows the number of duplicates: the row 2-3 holds the messages with 2 duplicates. The menu selects the topic, and the date picker selects the day.

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

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

Filecoin Logo Blog Hero
Blog post

Filecoin Network Health Weekly Reports are Live

Dive into Filecoin's DHT most important metrics.

ResNetLab Technical Report
Paper

Accelerating Content Routing with Bitswap: A multi-path file transfer protocol in IPFS and Filecoin

Bitswap is a Block Exchange protocol designed for P2P Content Addressable Networks. It leverages merkle-linked graphs in order to parallelize retrieval and verify content integrity. …

arXiv Preprint
Paper

GossipSub: Attack-Resilient Message Propagation in the Filecoin and ETH2.0 Networks

Permissionless blockchain environments necessitate the use of a fast and attack-resilient message propagation protocol for Block and Transaction messages to keep nodes synchronised and avoid …