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.

17,467
public repos on the network
~157 GiB
to mirror every one of them
1,897
nodes seeding repos
6.0×
average seed count per repo
32
countries with a locatable node
257
identities active in the last 3 months
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 17,467 public repositories our seed can see and the 1,897 nodes seeding them.

1,897
nodes seeding repos
6.0×
avg. seed count per repo
~88%
of the network's public repos mirrored
199
repos with a single seed
■ Official Radicle   ■ Community · seed count for each repo.
Of 16,932 repositories with enough recorded history to compare, 497 gained seeds, 1,009 lost some and the median one held steady. 1,008 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.

The repos radicle.at stores, grouped 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 ~12% 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,897 nodes are small personal seeds; 28 seed 1,000 repos or more, radicle.at among them. For 93 repositories, radicle.at is the only seed.

How seed counts have moved

The first chart tracks seed counts back to July 2026.

The 9,329 public repos known both 4 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.
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).

The median seed count of the 16,257 repos in the bars went from 7 nodes in the week to 19 October to 6 this past week, a move this period cannot tell apart from its noise. 1% of repos ended higher and 19% lower. 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,630
nodes known to our seed
1,897
nodes seeding repos
28
large public seeds (1,000+ repos)
32
countries with a locatable node
The Heartwood (radicle-node) version each node last reported, newest first. "1" is a build that reported only its major version.
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 736 delegates with 3 or more repositories that have a seed count.

Their pages: erikli, cloudhead, radicle-mirror, fosskar z6Mkqumz, fosskar z6Mkuikg, maninak, shirahara z6Mkg4WM, kristoff, efstajas z6MkeVA8, josh, shirahara z6MkvVZk, dirk1980-nb, lorenz, julianp, efstajas z6MkqG3P.

How many repos each node seeds. A node can announce at most 2,973 repos at once, so a node in the top bar may seed far more than shown. Most seed fewer than ten repos, or none at all.
The kind of address each node gives for others to reach it.
Nodes with a reachable address, by when they were last seen: active within 3 months, idle within a year, dormant for longer.
How many repos each node seeds, for nodes whose announcements fill the 2,973 limit. 24 of the 26 other such nodes have sent enough announcements for an estimate. Ours, radicle.at, is in green at its exact count. The dot is the estimate and the line the range the true count most likely falls in. The dashed line marks the 2,973 repos one announcement can list.

Their pages: Mistera-alpha, community.computer, smdev.

Countries of the nodes with a public IP address. Only 327 of 3,630 nodes can be placed.

Our seed can see 3,630 nodes, but only 1,897 of them seeded any repository in the last 14 days, and just 28 seed 1,000 or more. The largest group, 1,623 nodes, has no known address; 1,323 give a domain name, 420 an IP address, 230 only a Tor address and 34 a Tailscale one. Of the 327 nodes that can be placed on a map, 116 are in Germany and 82 in the US.

Collaboration: issues & patches

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

14,484
issues + patches
5,940
patches (code review)
8,544
issues
5.2%
of repos see any collaboration
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 8,544 issues and 5,940 patches (about 1.4 issues per patch) in only 796 of the repositories radicle.at stores (5.2%). The ten most active hold 41% of that activity, led by AnyPS5 with 1,714. Most of what radicle.at stores saw no issue or patch all year. Over all time, 83.1% of the issues and patches on the repos radicle.at stores involve only automated identities, and 99% of those sit in 3 repositories.

Issues and patches per month, by people or automation. On Volume each gridline is ten times the one below. In a typical month of the last year automation made 7.1 times as many as people. The current month is still in progress.

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

1,224
identities that ever collaborated here
257
active in the last 3 months
123
active in the last month
21%
of all identities still active
How many identities were active in each period up to today. Periods nest, so each shorter period's bar sits inside the longer ones.
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 21% of the 1,224 identities that have ever opened or commented on an issue or patch here (1,259 counting automation) were active in the last three months.

A patch is Radicle's pull request. Bars count repos that merged at least one patch that month. The current month is still in progress.
In 108 of the 159 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, 48,874 patches have merged and 64,788 are still open; issues stand at 12,588 closed against 4,665 open. Automation opened 41,178 of the merged patches. One repository accounts for 58,050 of the open patches. The record starts in December 2022, well before this site began measuring anything.

Bars count the issues opened and closed each month, the line how many were still open at its end. It covers 10,465 of the 17,045 public issues opened by people, those whose every close and reopen could be dated. The current month is still in progress.
For the issues closed each month, how long they had been open: the median, and the time within which 85% of them closed. A month with fewer than 10 issues closed is left out, and so is an issue reopened since. The current month is still in progress.
People's patches that were ever drafts, by how long they stayed drafts before being marked ready for review, merged or archived. 54% left draft within a week. The last bar counts the 114 patches that are still drafts.

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.

18,550
CI jobs recorded
317
repositories that ran CI
126
nodes that took part in a job
19
other COB types in use
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.
A repository counts from its first job, a node from the first job it took part in.
191 releases published with radicle-artifact from 61 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.
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.

15,439
repos stored
157.0 GiB
total size
0.25 MiB
median; half are tinier
50%
of bytes in the top 1% of repos
Most repositories are small: 73% are under 1 MiB, and only 13 exceed 1 GiB.
Size on disk of the largest repositories radicle.at stores.
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.25 MiB, little more than metadata and a few commits, while the largest 1% hold 50% 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 99% of explorer requests and 97% of API requests.

app.radicle.at · requests by client. Other automated clients made the most requests: 49% in the last year, 46% over all time.
seed.radicle.at · requests by client. Other automated clients made the most requests: 60% in the last year, 49% over all time.
Requests by client type. People are the thin green sliver. Automated requests in October 2026 were 28 times those of October 2025. The last day is only partly counted.

Strip out the crawlers and scanners, and people made 242 explorer requests in a typical month over the last year. November 2026 so far counts 1,261, 5.2 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 16,019 distinct repositories, crawlers included.

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,359, against 30,291 for radicle-jetbrains-plugin.

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.

Distinct human IP addresses each month, new and returning. One address is not always one person. November 2026 so far counts 974, 6.7 times a typical month, which may include automation that passes as a browser.
Share of human visits by device, month by month. The current month is still in progress.
Share of human visits by browser, month by month. The current month is still in progress.
Share of human visits by OS, month by month. The current month is still in progress.
Distinct visitor addresses, by country.
Human requests per hour of the day. Over the last year the busiest hour, 18:00 UTC, had 2.0 times the requests of the quietest, 02:00.
00:0006:0012:0018:0023:00
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 7.9 ms and 99% within 1.0 s.

Median, 90th and 99th percentile response time per day (log scale), all clients together. The last day is only partly counted. The API's log from 16:59 UTC on 28 June to 17:38 UTC on 28 July 2026 was lost, so none of its requests in that window are counted.
Responses by HTTP status. From September 2026 this includes crawlers blocked before they reach the API.
Bytes the seed sent per month (explorer + API), split human vs automated. Automated clients took 97% of the bytes in October 2026. The current month is still in progress. The API's log from 16:59 UTC on 28 June to 17:38 UTC on 28 July 2026 was lost, so none of its requests in that window are counted.
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 88% 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.

~88%
of the network's public repos mirrored
15,439
repos mirrored for everyone
93
repos whose only seed is radicle.at
3.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" (17,467) exceeds "seeded here" (15,439) because our seed can see repos it does not store. The API's request log from 16:59 UTC on 28 June to 17:38 UTC on 28 July 2026 was lost, so every figure drawn from it (web requests answered, API traffic by client type, API responses by status, what gets browsed, bandwidth and API response time) leaves out the API's requests in that window. The explorer's log is complete, so explorer and visitor figures are too.
  • 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.
  • Issues opened and closed, time to close and time in draft replay each issue's and patch's own signed history, op by op, for the instant of every close, reopen and draft. Each instant is its author's own clock. Who may act is judged against each repo's delegates today, so a former delegate's action can be misjudged, and only histories that replay to the state the node itself reports are counted. Automated identities are left out, and so are repos pruned before the replay first read them.
  • 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.
  • Estimated node sizes. A node lists at most 2,973 repos in one announcement. On starting up, a node lists its 2,973 lowest repo ids, and since ids are spread evenly, how far up the id range that list reaches gives the node's size. Each later announcement lists a fresh random 2,973, and how much two such lists overlap gives the size too, the way a wildlife census counts tagged animals caught a second time. The estimates use the announcements our seed received over the last 14 days, and a node is shown only once its range is narrow enough to be useful. Ranges are 95% intervals for a node whose size held steady over that time. A node still growing has a true count near the top of its range or just past it, and one that dropped repos in the last few days still shows its earlier size. Our seed is not among them, because its repos are counted from its own storage. "Nodes by size" places each node by what our seed's routing table lists for it, which for these nodes is about one announcement's 2,973 plus any repos it has since announced changes to or our seed has fetched from it, so that chart counts these nodes at fewer repos than estimated here.
  • "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 ~157 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.25 MiB). The largest repos dominate the total (the top 1% hold 50% 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