Fertilize

State of the Radicle network

Radicle offers git-native code collaboration with no central server and no accounts. Nodes replicate whichever repositories they choose to seed. This page tracks the resulting network. The numbers are measured nightly from radicle.at, one of the oldest and largest public seed nodes. No trackers, no cookies, no third parties.

15,983
public repos on the network
~122 GiB
to mirror every one of them
1,891
nodes seeding repos
8.6×
average seed count per repo
32
countries with a locatable node
350
identities active in the last 3 months
Repos created per month
New repositories each month (bars) and the running total (line), back to November 2023. Only repos our seed has kept track of are counted, so older months come out low. The current month is still in progress.

01Replication & network reach

A repo can live on many nodes at once, and the more nodes seed it, the harder it is to lose. Here is how that looks across the 15,983 public repositories our seed can see and the 1,891 nodes seeding them.

1,891
nodes seeding repos
8.6×
avg. seed count per repo
~82%
of the network's public repos mirrored
78
repos with a single seed
Most widely seeded repositories
■ Official Radicle   ■ Community · seed count for each repo.
Repositories gaining seeds this week
Of 15,718 repositories with enough recorded history to compare, 921 gained seeds, 1,069 lost some and the median one held steady. 932 more went silent all week. Each figure compares a repository's typical seed count over the last week with the week before.
Chart all six together

Every repository our seed knows of has its own page, and most are listed at /repos.

Seed count spread
The repos radicle.at stores, grouped by seed count.
Repos by seed count
Every public repo radicle.at can see, including the many it does not store, grouped by seed count. The first bar is repos with a single seed, one outage from unreachable.

Our policy is to mirror the whole network. The ~18% of public repos it does not store are a mix of stale, abandoned and test repos that radicle-seed-prune removed and repos not yet fetched or unreachable. Most of the 1,891 nodes are small personal seeds; 41 seed 1,000 repos or more, radicle.at among them. For 11 repositories, radicle.at is the only seed.

How seed counts have moved

The first chart tracks seed counts back to July 2026.

Seed count over time
The 9,340 public repos known both 3 months ago and today. One column per day, shaded by how many repos sit on that many seeds. The line is the median seed count. Blank columns under a dashed line are the 12 days nothing was collected.
Seeds gained or lost per repo
Each repo's typical weekly seed count against the start of the period, for repos seen today. Moves of up to 3 seeds count as steady (about 8% from 44 seeds up).

Half the 15,137 repos in the bars had 9 or more seeds in the week to 31 August, and still 9 or more this past week. 79% of repos held steady; the rest moved (7% up, 14% down). A seed count is how many nodes announced the repo to radicle.at in the past 14 days.

The wider network our seed sees

3,473
nodes known to our seed
1,891
nodes seeding repos
41
large public seeds (1,000+ repos)
32
countries with a locatable node
What software the network runs
The Heartwood (radicle-node) version each node last reported, newest first. "1" is a build that reported only its major version.
Delegates with the most reach
A delegate is a maintainer's identity. Each bar is the median seed count of a delegate's repositories, so one popular repository cannot carry the rank. Ranked among 631 delegates with 3 or more repositories that have a seed count.

Their pages: cloudhead, erikli, kristoff, frank, tareifz z6MkfM6p, codeberg-mirror-kaiya, Gabriel, tareifz z6MkqRAA, neo, lorenz, ff0x@mean-six, shawn.webb-hbsd-cdcfi-01, 17, strawmelonjuice.Fennekin, gendor.

Nodes by size
How many repos each node seeds. Most seed fewer than ten repos, or none at all.
How nodes connect
The kind of address each node gives for others to reach it.
Active vs dormant nodes
Nodes with a reachable address, by when they were last seen: active within 3 months, idle within a year, dormant for longer.
Where locatable nodes are
Countries of the nodes with a public IP address. Only 305 of 3,473 nodes can be placed.

Our seed can see 3,473 nodes, but only 1,891 of them seeded any repository in the last 14 days, and just 41 seed 1,000 or more. The largest group, 1,592 nodes, has no known address; 1,233 give a domain name, 396 an IP address, 218 only a Tor address and 34 a Tailscale one. Of the 305 nodes that can be placed on a map, 107 are in Germany and 78 in the US.

Collaboration: issues & patches

Counts are per Radicle identity, one key per device, so one person can appear as several.

11,085
issues + patches
4,743
patches (code review)
6,342
issues
5.6%
of repos see any collaboration
Most collaborative repositories
Issues and patches (Radicle's pull requests) per repo. Automation means identities run by programs, such as CI and machines reporting their own state.

In the last year people opened or worked on 6,342 issues and 4,743 patches (about 1.3 issues per patch) in only 735 of the repositories radicle.at stores (5.6%). The ten most active hold 33% of that activity, led by strom with 698. Most of what radicle.at stores saw no issue or patch all year. Over all time, 85.2% of the issues and patches on the repos radicle.at stores involve only automated identities, and 99% of those sit in 3 repositories.

People vs automation over time
Issues and patches per month, by people or automation. Volume is log-scaled: in a typical month of the last year automation made 8.3 times as many as people. The current month is still in progress.

Automation arrived in September 2024 and did not crowd people out: their issues and patches went from about 220 a month then to about 1,300 a month over the last six months. Read Share for automation's part of each month, and Volume for people's own line.

1,044
identities that ever collaborated here
350
active in the last 3 months
109
active in the last month
34%
of all identities still active
Active collaborators
How many identities were active in each period up to today. Periods nest, so each shorter period's bar sits inside the longer ones.
Active collaborators over time
On each day, how many identities had been active in the period before it, one line per period.

Collaboration has a committed core and a long tail of drop-ins: only 34% of the 1,044 identities that have ever opened or commented on an issue or patch here (1,078 counting automation) were active in the last three months.

Repositories merging patches per month
A patch is Radicle's pull request. Bars count repos that merged at least one patch that month. August 2026 set a record: 85 repositories merged a patch. The current month is still in progress.
How long the typical merge takes
In 96 of the 140 repos here, the typical patch merges within the hour. Automated identities are left out, so this is the time between people.

Across the public history radicle.at has replicated, 47,789 patches have merged and 61,049 are still open; issues stand at 10,572 closed against 4,266 open. Automation opened 40,616 of the merged patches. One repository accounts for 54,573 of the open patches. The record starts in December 2022, well before this site began measuring anything.

Beyond issues and patches

Anyone can define a new kind of collaborative object (COB). These are the COB types radicle.at has seen, dated by when each COB was created.

15,543
CI jobs recorded
284
repositories that ran CI
105
nodes that took part in a job
19
other COB types in use
Radicle CI jobs per month
Each bar is one month's jobs, split among the nodes in proportion to how many each took part in, busiest at the bottom. Past the twelve busiest, the rest share one grey slice. An undivided bar means a single node took part that month. A job is one run of Radicle CI on one commit. The current month is still in progress.
Repositories and nodes using CI
A repository counts from its first job, a node from the first job it took part in.
Releases published
90 releases published with radicle-artifact from 34 repositories. The thirteen busiest get a row each, the rest share one. Each square is a release. Releases too close together to draw apart share one square, with ×3 beside it for three where there is room.
COB types in use
Each dot is a repository, placed where it started using that type. Bigger dots hold more COBs. Green is Radicle CI, pink radicle-artifact, blue everything else.

02The repositories we seed

Our seed mirrors public repositories from across the Radicle network so they stay available even when their authors are offline.

13,096
repos stored
121.7 GiB
total size
0.23 MiB
median; half are tinier
52%
of bytes in the top 1% of repos
Repository size distribution
Most repositories are small: 75% are under 1 MiB, and only 14 exceed 1 GiB.
Largest repositories on disk
Size on disk of the largest repositories radicle.at stores.
Collection growth over time
Total storage (GiB) and repository count, day by day. The step downs are weekly runs of radicle-seed-prune, which removes stale repos.

Half of all repositories are under 0.23 MiB, little more than metadata and a few commits, while the largest 1% hold 52% of the bytes.

03Traffic & visitors

The seed answers two kinds of web traffic: the explorer at app.radicle.at (the pages people open) and the API at seed.radicle.at (what the explorer and other tools call). Over the last year, automated clients made 100% of explorer requests and 97% of API requests.

Explorer traffic, by client type
app.radicle.at · requests by client. Meta crawlers made the most requests: 49% in the last year, 37% over all time.
API traffic, by client type
seed.radicle.at · requests by client. Meta crawlers made the most requests in the last year (45%), and other automated clients over all time (32%).
Explorer requests over time
Requests by client type. People are the thin green sliver. Automated requests in August 2026 were 19 times those of August 2025. The last day is only partly counted.

Strip out the crawlers and scanners, and people made 243 explorer requests in a typical month over the last year. September 2026 so far counts 1,294, 5.3 times that. Automated clients that send an ordinary browser User-Agent are counted as people, so a jump this size can be automation that was not caught.

04What gets browsed

Requests to the explorer and the API since April 2024 named 13,866 distinct repositories, crawlers included.

Featured repositories pinned on the landing page
Pinned on app.radicle.at, so every visitor sees them first. Crawlers included.

Over the last year the top organic repository, webspace_app, drew more requests than any pinned one: 49,271, against 30,774 for radicle-jetbrains-plugin.

Most-viewed issues & patches
Repos ranked by how often people opened their issue and patch pages in the explorer, crawlers excluded. A bar opens those pages there.

05Who visits

Human visits only. Crawlers are told apart by each request's User-Agent and network origin.

Unique visitors per month
Distinct human IP addresses each month, new and returning. One address is not always one person. September 2026 so far counts 573, 3.9 times a typical month, which may include automation that passes as a browser.
Device mix over time
Share of human visits by device, month by month. The current month is still in progress.
Browser mix over time
Share of human visits by browser, month by month. The current month is still in progress.
Operating system over time
Share of human visits by OS, month by month. The current month is still in progress.
Where visitors come from
Distinct visitor addresses, by country.
Visits by hour of day (UTC)
Human requests per hour of the day. Over the last year the busiest hour, 20:00 UTC, had 2.0 times the requests of the quietest, 01:00.
00:0006:0012:0018:0023:00
How visitors arrive
Referrer of human explorer visits: direct (typed in or opened from inside the app), from a search engine, or an external link. Counts requests, not people.

06Speed & reliability

Only the API is timed; the explorer is a static app. Blocked requests are not timed. On a typical day in the last month the API answered half its requests within 10 ms and 99% within 1.4 s. The slowest 1% got slower over that month, from about 1.2 s to about 1.9 s.

API response time over time
Median, 90th and 99th percentile response time per day (log scale), all clients together. The last day is only partly counted.
API responses by status
Responses by HTTP status. From September 2026 this includes crawlers blocked before they reach the API.
Bandwidth served over time
Bytes the seed sent per month (explorer + API), split human vs automated. Automated clients took 97% of the bytes in August 2026. The current month is still in progress.
Connect your node with radicle.at

Connecting to this always-on seed helps your repos and their updates spread across the network faster. Any public repo you publish is mirrored here too, so others can fetch it while your own node is offline. It also speeds up fetching the repos our seed already stores.

z6MkjDYUKMUeY58Vtr8dGJrHRvnTfjKWVGCBYJDVTHXsXzm5@seed.radicle.at:8776

Connect once from your terminal:

rad node connect z6MkjDYUKMUeY58Vtr8dGJrHRvnTfjKWVGCBYJDVTHXsXzm5@seed.radicle.at:8776

Or make it permanent by adding it to preferredSeeds in ~/.radicle/config.json:

"preferredSeeds": [
  "z6MkjDYUKMUeY58Vtr8dGJrHRvnTfjKWVGCBYJDVTHXsXzm5@seed.radicle.at:8776"
]

Support radicle.at

This is one of the oldest and largest public seeds on the Radicle network, online since March 2024 and storing about 82% of the network's known public repositories. Around the clock and for free, it keeps projects reachable and runs the explorer at app.radicle.at and the API at seed.radicle.at that other tools call.

~82%
of the network's public repos mirrored
13,096
repos mirrored for everyone
11
repos whose only seed is radicle.at
2.5M
web requests answered since April 2024

Running it costs real disk, bandwidth, and time. If our seed is useful to you or to the network, a small contribution keeps it healthy and growing.

Donate to keep it flourishing

The button goes to Liberapay, which handles cards and recurring donations.

Prefer not to create an account? Send directly.
Bank transfer (SEPA)
DE63 1001 1001 2624 5948 04

Account holder Konstantinos Maninakis. Inside the euro area an instant transfer arrives the same minute and costs nothing. From outside EU use BIC NTSBDEB1XXX.

Bitcoin
bc1pemmvu4325yuqrn8y44f6rllwp4hqp7znrv3qsr8yv5vx8la3etvqylwnle

Every bit helps cover disk, bandwidth, and upkeep. Thank you for keeping the Radicle network resilient.

How these stats are made · privacy
Notes & limits. These numbers cover only the public repositories our seed can see and the web requests to our own explorer and API. Private repositories are invisible to it, and git traffic between nodes and visits to other explorers or seeds are not counted. They are one seed's view, not the whole network.
How each number is worked out, and where it could be incorrect
  • What is missing. Repos fetched or synced directly between nodes, including over Tor or other private transports, leave no trace here. "Known to the network" (15,983) exceeds "seeded here" (13,096) because our seed can see repos it does not store.
  • People vs. robots is inferred from request patterns and User-Agents, including crawlers that spread across many addresses and imitate a browser. Some automation still passes as people and the odd real visitor is counted as automated, so human counts can be off in both directions.
  • Human vs. automated collaboration is inferred per identity from timing: hundreds of issues or patches minutes apart, a steady schedule kept up across days, or patches in bulk and never an issue. A burst that is mostly issues, on a few days, counts as a person moving a tracker in. Automation that acts only when somebody pushes shares their timing and is missed. Only identities checked by hand are ever named as automation. An issue or patch counts as automated when every participant on it is.
  • The monthly people-vs-automation series places each issue or patch in the month it was last active, because the seed keeps only the current state of each thread. Recent months are the most complete; earlier ones undercount whatever is still active today. It keeps repos the seed has dropped since 23 August 2026, which the per-repo lists do not.
  • Repos created per month dates each repo by the commit at the root of its Radicle identity, which is the creator's own clock and sometimes wrong, so dates before 2023 or in the future are dropped. It counts every repo our seed has held since 23 August 2026, including ones since pruned. It misses repos pruned before then (over 2,000) and repos our seed never fetched, which skew old, so it undercounts, most of all in the early months. Some recent repos are spam that was pruned within days.
  • CI jobs, releases and other COB types count every collaborative object (COB) beyond issues and patches in the public repos our seed stores, each dated by the commit that created it, which is its author's own clock. A repo or node counts from its first dated COB. Repos our seed does not store are missing, so every figure there is a floor for the network.
  • The "Freshly created repos" list shows the newest repos that reached our seed, placed by creation date, so one that arrives late lands below the top. Unlike the births chart, it drops repos no longer stored here.
  • Seed counts and node counts come from our seed's routing table and shift daily. A seed count is how many nodes announce a repo: a declared intent to serve it, not a verified copy on disk. Nodes with restrictive seeding policies announce fewer repos than they actually serve, so node sizes here are a lower bound. The repo counts and the count of nodes seeding repos cover the last 14 days: a node quiet that long drops out until it returns. The "nodes known to our seed" count has no such limit, so it does not fall when a node goes quiet.
  • "Official Radicle" repos are a hand-kept list of Radicle-team projects (core protocol, apps and CI), not inferred from delegates, since a maintainer's personal repos share the same delegate.
  • The headline ~122 GiB "to mirror every one of them" is an estimate: the exact size of the repos our seed holds, plus the rest priced at the median repo size (0.23 MiB). The largest repos dominate the total (the top 1% hold 52% of the bytes) and are already stored here, so it should land close, but one large repo our seed lacks would move it.
  • Visitors and traffic. Country is approximate, from an offline IP database, by distinct IP; one network address is not one person. Repository request counts include every explorer and API request that names the repository, crawlers included. Response times are measured at the seed itself, so requests answered from a browser or upstream cache never reach it and are neither counted nor timed.
  • How far back it goes. The node has run since 15 March 2024. Repository stats begin 16 March 2024, web logs April 2024, and the storage-size series late May 2024.


Take the data. Every headline figure above as JSON at /summary.json, and as plain prose at /llms.txt. Both are rebuilt nightly and are CC BY 4.0: take them, chart them, quote them.

radicle.at · an independent Radicle seed · last updated · built with open data from the node itself · Privacy.
seed.radicle.at and stats.radicle.at are independent community projects and not affiliated with the Better Internet Foundation or the Radicle Team.
aradicle.toolsartifact
homegrown apps & tools for Radicle
Link copied