Week 2024-26

Avail Report Cal. Week 26 - 2024 #

General Information #

The following results show measurement data that were collected in calendar week 26 in 2024 from 2024-06-24 to 2024-07-01.

  • Number of crawls 336
  • Number of visits 4,273,334

    Visiting a peer means dialing or connecting to it. Every time the crawler or monitoring process tries to dial or connect to a peer we consider this as visiting it. Regardless of errors that may occur.

  • Number of unique peer IDs visited 19,736
  • Number of unique peer IDs discovered in the DHT 17,301
  • Number of unique IP addresses found 8,167

Timestamps are in UTC if not mentioned otherwise.

Churn Analysis #

This visualizes the uptime of peers over a specific period of time. The plot may display trends in churn rate, distribution of uptime periods, or patterns in peer activity. It helps analyze the stability and reliability of the network by identifying fluctuations in peer participation and examining potential factors influencing churn.

024681012141618202224020406080100
all (360)Avail Node/v1.10 (247)Avail Node/v1.11 (113)Uptime (hours)Online Peers (%)Churn Analysis

Geolocation #

Geographical data is sourced from the MaxMind database, which maps IP addresses to corresponding countries.

This bar plot illustrates the distribution of observed nodes across different countries.

52.5%9.6%7.2%6.6%4.3%3.9%3.4%2.3%1.6%1.3%1.2%1.2%4.8%DENLmultiUSFRFIGBPLSGCAAUJPothers020406080100120140160
CountryCountCountry Distribution of All NodesTotal: 310Data: week ending 30 Jun 2024. Source: Nebula

This plot displays the weekly geographical distribution of nodes, categorized by country.

2024-06-252024-06-262024-06-272024-06-282024-06-292024-06-30050100150200250
CountryDEUSmultiNLFRGBothersDateCountCountry Distribution of All NodesTotal Mean: 136Data: week ending 30 Jun 2024. Source: Nebula

Cloud Providers #

Cloud providers data is sourced from Udger, which maps IP addresses to known hosting providers.

Cloud Hosting Rate #

This line chart displays the count of nodes within the Avail network that are hosted on known commercial cloud providers, compared to those that are not. It tracks the distribution over a specified period, offering insights into the infrastructure preferences for node hosting.

Regular analysis of this chart can reveal trends in the adoption of cloud services for nodes. Such information is crucial for understanding the network’s resilience and the potential reliance on cloud infrastructure.

2024-06-252024-06-262024-06-272024-06-282024-06-292024-06-30050100150200250300350
ProviderDatacenterNon-DatacenterDateCountCloud Rate of All NodesTotal Mean: 136Data: week ending 30 Jun 2024. Source: Nebula

This bar chart presents the weekly distribution of Avail nodes among various cloud providers, including nodes not hosted within data centers (grouped under Non-Datacenter).

20.0%19.1%14.5%14.2%12.6%6.4%2.3%1.7%1.6%1.3%0.8%0.5%5.2%Digital Ocean, IncComtrance GmbhHetzner OnlineNon-DatacenterGrier ForensicsContabo GmbHOplinkDevel.cz Lab s.r.o.OVHPlusServer GmbHCensys, Inc.Utel Datacenterothers0102030405060
Cloud ProviderCountCloud Distribution of All NodesTotal: 316Data: week ending 30 Jun 2024. Source: Nebula

The line chart illustrates the trends in the distribution of all Avail nodes across cloud providers over the given time period. Note that nodes hosted outside of data centers are not included in this representation.

2024-06-252024-06-262024-06-272024-06-282024-06-292024-06-300102030405060708090
Cloud ProviderComtrance GmbhDigital Ocean, IncGrier ForensicsHetzner OnlineContabo GmbHDevel.cz Lab s.r.o.othersDateCountCloud Distribution of All NodesTotal Mean: 91Data: week ending 30 Jun 2024. Source: Nebula

Crawls #

Protocols #

This plot illustrates the evolving count of nodes supporting each of the listed protocols over time. It exclusively presents data gathered from nodes accessible through a libp2p connection via our crawler. The identification of supported protocols relies on the libp2p identify protocol, hence necessitating a libp2p connection for discovery.

2024-06-252024-06-262024-06-272024-06-282024-06-292024-06-300100200300400500
/ipfs/ping/1.0.0/ipfs/id/push/1.0.0/ipfs/id/1.0.0/Avail/kad/paritytech/grandpa/1/Avail/transactions/1/Avail/sync/2/Avail/state/2/Avail/light/2/Avail/sync/warp/Avail/block-announces/1/6f09966420b2608d1947ccfb0f2a362450d1fc7fd902c29b67c906eaa965a7ae/transactions/1/6f09966420b2608d1947ccfb0f2a362450d1fc7fd902c29b67c906eaa965a7ae/kad/6f09966420b2608d1947ccfb0f2a362450d1fc7fd902c29b67c906eaa965a7ae/light/2/6f09966420b2608d1947ccfb0f2a362450d1fc7fd902c29b67c906eaa965a7ae/state/2/6f09966420b2608d1947ccfb0f2a362450d1fc7fd902c29b67c906eaa965a7ae/block-announces/1/6f09966420b2608d1947ccfb0f2a362450d1fc7fd902c29b67c906eaa965a7ae/sync/2/6f09966420b2608d1947ccfb0f2a362450d1fc7fd902c29b67c906eaa965a7ae/grandpa/1/6f09966420b2608d1947ccfb0f2a362450d1fc7fd902c29b67c906eaa965a7ae/sync/warp/d3d2f3a3495dc597434a99d7d449ebad6616db45e4e4f178f31cc6fa14378b70/grandpa/1/d3d2f3a3495dc597434a99d7d449ebad6616db45e4e4f178f31cc6fa14378b70/kad/d3d2f3a3495dc597434a99d7d449ebad6616db45e4e4f178f31cc6fa14378b70/block-announces/1/d3d2f3a3495dc597434a99d7d449ebad6616db45e4e4f178f31cc6fa14378b70/state/2/d3d2f3a3495dc597434a99d7d449ebad6616db45e4e4f178f31cc6fa14378b70/sync/2/d3d2f3a3495dc597434a99d7d449ebad6616db45e4e4f178f31cc6fa14378b70/sync/warp/d3d2f3a3495dc597434a99d7d449ebad6616db45e4e4f178f31cc6fa14378b70/transactions/1/d3d2f3a3495dc597434a99d7d449ebad6616db45e4e4f178f31cc6fa14378b70/light/2DateCountObserved ProtocolsData: week ending 30 Jun 2024. Source: Nebula

Errors #

2024-06-252024-06-262024-06-272024-06-282024-06-292024-06-3002k4k6k8k10k12k
Cloud Providerconnection_refusedconnection_reset_by_peerio_timeoutnegotiate_stream_multiplexernetwork_unreachableno_good_addressesno_route_to_hostpeer_id_mismatchprotocol_not_supportedunknownDateCountConnection ErrorsData: week ending 30 Jun 2024. Source: Nebula
2024-06-252024-06-262024-06-272024-06-282024-06-292024-06-3005101520
Cloud Providerconnection_refusedio_timeoutnegotiate_stream_multiplexerprotocol_not_supportedstream_resetunknownDateCountCrawl ErrorsData: week ending 30 Jun 2024. Source: Nebula

Stale Node Records #

All Peers #

This stacked plot depicts the count of node records stored within each node’s routing table and made accessible through the DHT. These node records serve as a mechanism through which nodes discover new remote nodes in the network.

Ensuring the reachability of referenced nodes shared within the network holds paramount importance. The plot delineates the occurrences of reachable and non-reachable (stale) node records. Note that nodes running behind a NAT are counted as unreachable even though they may be online.

For instance, if a node’s record is present in the routing tables of 100 other nodes and the node is reachable, the plot will reflect an increase of 100 in the online category.

2024-06-252024-06-262024-06-272024-06-282024-06-292024-06-30010k20k30k40k50k60k70k80k90k
Record TypeReachableUnreachableDateCount of RecordsReachable vs. Unreachable Records Over TimeData: week ending 30 Jun 2024. Source: Nebula