Counters are taken from the web server and rsync daemon logs, aggregated hourly and written to a text file per month. Egress figures are payload bytes delivered to clients; they exclude the traffic we pull from upstream during synchronisation, which is a further 1 to 3 TB per month. Units are decimal: 1 TB = 1,000 GB.
| Month | Egress | Relative | Requests | Unique clients | Peak 5-min rate |
|---|---|---|---|---|---|
| 2025-10 | 31.4 TB | ################ | 176.2 M | 288,410 | 2.61 Gbit/s |
| 2025-11 | 33.8 TB | ################# | 189.7 M | 301,772 | 2.84 Gbit/s |
| 2025-12 | 30.2 TB | ############### | 170.4 M | 279,335 | 2.42 Gbit/s |
| 2026-01 | 35.9 TB | ################## | 201.3 M | 318,904 | 3.05 Gbit/s |
| 2026-02 | 34.1 TB | ################# | 191.8 M | 309,517 | 2.88 Gbit/s |
| 2026-03 | 39.7 TB | #################### | 223.1 M | 342,260 | 3.24 Gbit/s |
| 2026-04 | 41.2 TB | ##################### | 231.5 M | 356,881 | 3.47 Gbit/s |
| 2026-05 | 40.5 TB | #################### | 227.6 M | 351,044 | 3.12 Gbit/s |
| 2026-06 | 43.8 TB | ###################### | 246.1 M | 372,619 | 3.55 Gbit/s |
| 2026-07 | 45.1 TB | ####################### | 253.4 M | 389,205 | 3.60 Gbit/s |
| 2026-08 | 48.3 TB | ######################## | 271.4 M | 412,584 | 3.81 Gbit/s |
| 2026-09 * | 37.6 TB | ################### | 211.2 M | 358,127 | 3.44 Gbit/s |
| Total | 461.6 TB | 2,593.7 M | not additive | 3.81 Gbit/s max |
Client counts are distinct source addresses seen within the month and must not be added across rows: a machine that downloads updates every week is one address in every month it appears in. Roughly 23 % of the August addresses were IPv6 only.
| Total egress | 48.3 TB |
|---|---|
| Mean rate over the month | 144 Mbit/s |
| 95th percentile rate | 521 Mbit/s |
| Peak 5-minute average | 3.81 Gbit/s |
| Time of peak | 2026-08-14 19:25 UTC (Ubuntu 24.04.6 point release) |
| Busiest day | 2026-08-14, 4.12 TB |
| Quietest day | 2026-08-03, 0.94 TB |
| Uplink capacity | 2 × 10 GbE LACP, policed at 10 Gbit/s |
| Peak concurrent HTTP connections | 6,412 |
| Peak rsync sessions | 12 of 12 |
| Requests | 271,400,000 |
| Mean object size | 178 KB |
| Unique client addresses | 412,584 |
| Repository | Egress | Share | Requests | Mean object | Tree size |
|---|---|---|---|---|---|
| Ubuntu | 14.8 TB | 30.6 % | 89.4 M | 166 KB | 2.80 TB |
| Debian | 11.2 TB | 23.2 % | 71.8 M | 156 KB | 2.10 TB |
| Rocky Linux | 6.4 TB | 13.3 % | 28.3 M | 226 KB | 940 GB |
| Arch Linux | 5.1 TB | 10.6 % | 19.6 M | 260 KB | 84 GB |
| Alpine Linux | 3.9 TB | 8.1 % | 41.2 M | 95 KB | 78 GB |
| OpenWrt | 2.6 TB | 5.4 % | 12.4 M | 210 KB | 1.10 TB |
| Debian CD/ISO | 2.2 TB | 4.6 % | 0.6 M | 3.67 MB | 940 GB |
| Ubuntu releases (ISO) | 1.5 TB | 3.1 % | 0.4 M | 3.75 MB | 620 GB |
| CPAN | 0.4 TB | 0.8 % | 7.4 M | 54 KB | 17 GB |
| Other paths | 0.2 TB | 0.4 % | 0.3 M | 667 KB | — |
| Total | 48.3 TB | 100.0 % | 271.4 M | 178 KB | 8.68 TB |
Note the asymmetry between tree size and traffic: Alpine is 78 GB on disk and still moves 3.9 TB a month, because container builds pull the same handful of small packages over and over. OpenWrt is fourteen times larger on disk and moves less than a tenth of the requests, because a router is flashed once and then left alone. Arch produces an unusually large mean object because it ships few but large packages and its users upgrade the whole system at once.
| Breakdown | Egress | Share | Requests |
|---|---|---|---|
| HTTPS (443) | 39.1 TB | 80.9 % | 241.8 M |
| HTTP (80) | 6.8 TB | 14.1 % | 29.1 M |
| rsync (873) | 2.4 TB | 5.0 % | 0.5 M |
| IPv4 | 29.8 TB | 61.7 % | 169.4 M |
| IPv6 | 18.5 TB | 38.3 % | 102.0 M |
| Total egress | 48.3 TB | 100.0 % | 271.4 M |
Protocol rows and address-family rows each total 48.3 TB; they are two views of the same bytes, not five separate figures. rsync accounts for a large share of bytes per session and almost no requests, since a downstream mirror opens one session and copies a whole tree through it.
Egress has grown by about 38 % over the last twelve months, from 31.4 TB in October 2025 to 48.3 TB in August 2026, and September 2026 is on course to pass 49 TB. The growth is not evenly spread: point releases and the Alpine and Arch package churn move the line, while the ISO trees are flat outside release weeks. At the current rate the 10 Gbit/s policer is reached only during release peaks, so the next constraint is disk capacity rather than bandwidth; the array is at 54 % with no new trees planned.
Figures for closed months are not edited afterwards. If a month is corrected because of a counter reset or a log rotation fault, the correction is noted here. The last such correction was in March 2025, before the period shown above.
countme value in its requests. We pass it to nobody
and do not count it separately; it is only visible in the raw log line while that log
exists.