diff --git a/content.en/plots/2024/11/25/2024-48-report.md b/content.en/plots/2024/11/25/2024-48-report.md deleted file mode 100644 index 11bcb9168..000000000 --- a/content.en/plots/2024/11/25/2024-48-report.md +++ /dev/null @@ -1,136 +0,0 @@ ---- -title: Week 2024-48 -plotly: true -slug: 2024-48 -weight: 1045611 ---- - -# Celestia Report Cal. Week 48 - 2024 - -## General Information - -The following results show measurement data that were collected in calendar week 48 in 2024 from `2024-11-25` to `2024-12-02`. - -- **Number of crawls: `143`** - - The number of crawls executed during the week indicated above. - -- **Number of visits: `115,548`** - - Every attempt to dial or connect to a peer counts as a visit. Regardless of errors that may occur. We visit peers many times during a given week to extract information from them or probe for their uptime. We visit all peers that we discover in the DHT and peers that we found to be still online from the previous week. - -- **Number of unique peer IDs discovered in the DHT: `276`** - - The total number of unique peers that our crawler learned about from other peers over the period of the given week and attempted to dial or connect to (visit). This is not the total number of Peer IDs that existed simultaneously in the network at any point during the week. It is the aggregate over the entire week. - -- **Number of unique IP addresses discovered: `273`** - - The total number of unique IP addresses that the discovered peers advertised to the DHT network within the given week. IPv4 and IPv6 addresses are included in this number even if they address the same peer. This is not the total number of unique IP addresses that participated in the DHT simultaneously at any given point in time. It is the aggregate over the entire week. - -- **Network Size: `181`** - - The average number of peers that were found simultaneously (i.e., throughout the duration of one crawl) connected to the network. This number signifies the average network size from all crawls, during the given week. - -Timestamps are in UTC if not mentioned otherwise. - -## DHT Servers Agents - -This plot shows the distribution of various DHT servers user agents over time. - -{{< plotly json="/plots/2024/11/25/celestia-agents-overall-stacked.json" height="600px" >}} - -This stacked chart illustrates how the distribution of DHT servers agent versions for all key user agents evolves over time. It offers insights into the uptake of newer versions among these agents. - -{{< plotly json="/plots/2024/11/25/celestia-versions-distribution.json" height="600px" >}} - - - - - - 💡 To show the Lightnode population only, double-click on the `celestia-node/light` label.--> - - - - - - - -## Churn Analysis - -This plot presents the Cumulative Distribution Function (CDF) of peer departure -times from the network over a measurement period of one-week. The plot -basically shows the percentage of nodes online at a point in time (`t=0`) that -will have disconnected after 1 hour, 2 hours, 3 hours, .. up to 24 hours after `t=0`. - -- **X-Axis (Time in Hours)**: Represents the elapsed time since the reference -point (`t=0`), measured in hours. -- **Y-Axis (Percentage of Offline Peers)**: Indicates the cumulative -percentage of peers that have disconnected from the network by the -corresponding time interval. Specifically, it shows the proportion of peers -that were online at `t=0` and have since gone offline. - -This visualization aids in understanding peer churn dynamics, which is crucial -for optimizing network stability, resource allocation, and improving overall -decentralized network performance. - -Note that the sum of the CDF is **NOT** 100%, as it only includes peers that were -online for up to 24h. - -{{< plotly json="/plots/2024/11/25/celestia-network-stability-cdf.json" height="800px" >}} - -## Geolocation - -Geographical data is sourced from the [MaxMind database](https://www.maxmind.com), which maps IP addresses to corresponding countries. - -This bar plot illustrates the distribution of observed nodes across different countries. - -{{< plotly json="/plots/2024/11/25/celestia-geo-agent-All-bars.json" height="600px" >}} - -This plot displays the weekly geographical distribution of nodes, categorized by country. - -{{< plotly json="/plots/2024/11/25/celestia-geo-agent-All-lines.json" height="600px" >}} - -### Cloud Providers - -Cloud providers data is sourced from [Udger](https://udger.com/resources/datacenter-list), which maps IP addresses to known hosting providers. - -#### Cloud Hosting Rate - -This line chart displays the count of nodes within the Celestia 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. - -{{< plotly json="/plots/2024/11/25/celestia-cloud-rate-agent-All-lines.json" height="600px" >}} - -This bar chart presents the weekly distribution of Celestia nodes among various cloud providers, including nodes not hosted within data centers (grouped under _Non-Datacenter_). - -{{< plotly json="/plots/2024/11/25/celestia-cloud-agent-All-bars.json" height="600px" >}} - -The line chart illustrates the trends in the distribution of all Celestia nodes across cloud providers over the given time period. Note that nodes hosted outside of data centers are not included in this representation. - -{{< plotly json="/plots/2024/11/25/celestia-cloud-agent-All-lines.json" height="600px" >}} - -## 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](https://github.com/libp2p/specs/tree/master/identify), hence necessitating a libp2p connection for discovery. - -{{< plotly json="/plots/2024/11/25/celestia-crawl-protocols.json" height="1200px" >}} - -### Errors - -{{< plotly json="/plots/2024/11/25/celestia-connection-errors-single.json" height="600px" >}} - -{{< plotly json="/plots/2024/11/25/celestia-crawl-errors-single.json" height="600px" >}} - -## Stale Peer Records - -This stacked plot depicts the count of peer records stored within each node's routing table and made accessible through the DHT. -These peer records are used to discover new remote peers within the network, enabling efficient and secure routing towards the target peer or content - -Ensuring the reachability of referenced peers shared within the network holds paramount importance. The plot delineates the occurrences of reachable and non-reachable (stale) peer records. Note that nodes running behind a NAT are counted as unreachable even though they may be online. - -For instance, if a peer's record is present in the routing tables of 100 other nodes and the peer is reachable, the plot will reflect an increase of 100 in the _online_ category. - -{{< plotly json="/plots/2024/11/25/celestia-stale-records-stacked.json" height="600px" >}} \ No newline at end of file