- tor-relays - lists.torproject.org

New Tool: Tor Relay Leaderboards, Operator Metrics, & Network Health
by Tor at 1AEO 25 Jun '25

25 Jun '25

Hi All, Wanted to share an update on a new Tor metrics site we've launched: https://1aeo.com/metrics (updates every 30 min!) It builds on Allium (originally from git.jordan.im/allium, now end-of-life) and adds several new features—all powered by Tor Onionoo API (and more soon!) and open source for anyone to use, self-host, or build on. New Features - screenshots and some plain text Tor relay email list friendly versions below: - Operator Leaderboard (by AROI): See the top contributors across bandwidth, consensus weight, relay count, uptime, OS diversity, and geographic spread. Celebrating everybody's contributions! - Enhanced Operator Pages (by AROI): Quickly spot issues and compare operator setups across the Tor network. - Network Health Overview: Across all of Tor, show breakdowns of relay counts, bandwidth, uptime, operator diversity, AS and geo distribution, version compliance, and more. Goals: - Provide operators with new visibility into their relays and network-wide trends - Easily answer common questions without referring back to specifications and many page long text files - Push the boundaries of what “vibe” coding can do We’d love your feedback—especially through GitHub issues for tracking requests, bugs, or incorrect data: https://github.com/1aeo/allium/issues What’s Next: - Add support for consensus health parsing and other Onionoo endpoints (e.g. bandwidth stats) - Incorporate charts/graphs - Improve historical data tracking Hope it’s helpful, and open to suggestions from the community! Credits: Beyond Jordan's great open source work on Allium, many of the top operators have been reviewing and sharing feedback, AROI definition from Nusenu, Onionoo data, and many others! Top 5 Operators by Bandwidth (AROI) Rank Operator Relays Bandwidth Consensus Weight Guard/Mid/Exit Count Countries Platforms ----- -------------------------- ------- --------- ----------------- -------------------- --------- --------- 1 nothingtohide.nl 294 60.4 Gbit/s 6.61% 34 / 8 / 252 1 294 non‑Linux 2 quetzalcoatl‑relays.org 574 57.3 Gbit/s 3.80% 0 / 0 / 574 10 1 3 1aeo.com 566 53.3 Gbit/s 3.44% 293 / 273 / 0 2 1 4 prsv.ch 349 52.5 Gbit/s 4.26% 217 / 57 / 75 20 2 5 artikel10.org 128 30.2 Gbit/s 3.47% 0 / 0 / 128 1 1 Network Heavyweight Rankings Rank Operator Relays Net. Wt. Bandwidth G/M/E Countries---- ------------------------- ------ -------- ------------- --------- ---------- 1 nothingtohide.nl 294 6.55% 60.0 Gbit/s 34/8/252 1 2 prsv.ch 353 4.38% 51.3 Gbit/s 214/52/87 19 3 quetzalcoatl-relays.org 574 4.00% 58.1 Gbit/s 0/0/574 10 4 artikel10.org 128 3.47% 30.3 Gbit/s 0/0/128 1 5 1aeo.com 614 3.27% 54.2 Gbit/s 308/306/0 2 6 tor.r0cket.net 144 2.54% 28.2 Gbit/s 0/24/120 1 7 shadowbrokers.eu 32 2.25% 16.4 Gbit/s 3/0/29 3 8 applied-privacy.net 104 2.14% 21.3 Gbit/s 0/0/104 1 9 for-privacy.net 86 1.83% 20.1 Gbit/s 43/0/43 2 10 relayon.org 112 1.27% 17.5 Gbit/s 41/7/64 2 Exit Authorities Rank Operator Exits Exit % Tot. Auth. Exit BW Countries---- ------------------------- ------ ------- ----------- ------------ ---------- 1 nothingtohide.nl 252 14.44% 6.55% 51.1 Gbit/s 1 2 quetzalcoatl-relays.org 574 10.52% 4.00% 58.1 Gbit/s 10 3 artikel10.org 128 9.13% 3.47% 30.3 Gbit/s 1 4 tor.r0cket.net 120 6.69% 2.54% 26.9 Gbit/s 1 5 shadowbrokers.eu 29 5.71% 2.25% 15.7 Gbit/s 3 6 applied-privacy.net 104 5.64% 2.14% 21.3 Gbit/s 1 7 digitalcourage.de 30 2.95% 1.12% 9.2 Gbit/s 1 8 nos-oignons.net 54 2.78% 1.06% 11.3 Gbit/s 1 9 for-privacy.net 43 2.64% 1.83% 10.8 Gbit/s 2 10 prsv.ch 87 2.07% 4.38% 10.4 Gbit/s 19 Diversity Masters Rank Operator Relays Score Bandwidth Countries Platforms Unique AS---- ------------------------- ------ ------ ------------- ---------- ---------- ---------- 1 tor(a)zgato.ru 81 92.5 6.6 Gbit/s 26 1 39 2 prsv.ch 353 61.0 51.3 Gbit/s 19 2 20 3 Safe-mail 33 51.5 4.2 Gbit/s 16 1 18 4 your@e-mail 22 48.5 1.4 Gbit/s 13 1 21 5 nobody(a)tor.org 23 35.5 1.6 Gbit/s 8 1 18 6 a-n-o-n-y-m-e.net 17 35.5 1.9 Gbit/s 11 1 12 7 peca-relay 20 32.0 1.8 Gbit/s 10 2 9 8 freiraum 14 31.5 769.2 Mbit/s 10 1 10 9 FlashTor 11 31.0 289.5 Mbit/s 9 2 10 10 quetzalcoatl-relays.org 574 30.5 58.1 Gbit/s 10 1 9 Frontier Pioneers (Rare Countries) Rank Operator Rare Bandwidth Countries Specialization---- ------------------------- ----- ------------- ---------- ------------------------------- 1 freiraum 6 769.2 Mbit/s 6 AE, IN... 2 olokerunningtor 5 131.3 Mbit/s 5 AO, KE... 3 tor(a)zgato.ru 5 6.6 Gbit/s 4 EU, GE... 4 cembranutboys.com 3 211.5 Mbit/s 3 BZ, CW, TT 5 prsv.ch 8 51.3 Gbit/s 2 AM, TR 6 osservatorionessuno.org 2 1.2 Gbit/s 2 PT, TR 7 janfuger 2 193.4 Mbit/s 2 MK, TR 8 privacyhaven(a)duck.com 2 345.9 Mbit/s 2 IN, TR 9 email(a)airmail.cc 1 476.3 Mbit/s 1 AM 10 Safe-mail 1 4.2 Gbit/s 1 TR Network Veterans Rank Operator Relays Score Bandwidth Countries Platforms Specialization---- ------------------------------ ------ ------ ------------- ---------- ---------- --------------------- 1 tor(a)insc.de 1 6450 1.7 Mbit/s 1 1 6450 days * 1.0 2 tor-trouble 1 6105 198.7 Mbit/s 1 1 6105 days * 1.0 3 dennis 1 5469 66.8 Mbit/s 1 1 5469 days * 1.0 4 A1F1E776E110F29C 2 4884 51.4 Mbit/s 1 1 4884 days * 1.0 5 Jon Gjengset 1 4489 8.9 Mbit/s 1 1 4489 days * 1.0 6 Ranlvor 1 4248 44.2 Mbit/s 1 1 4248 days * 1.0 7 aholiday(a)yahoo.com 1 4096 931.8 Kbit/s 1 1 4096 days * 1.0 8 insomnia@orwell1984 1 4095 4.4 Mbit/s 1 1 4095 days * 1.0 9 tor(a)theyosh.nl 1 4082 79.7 Mbit/s 1 1 4082 days * 1.0 10 Ry4an Brase 1 4037 8.4 Mbit/s 1 1 4037 days * 1.0 On Monday, May 26th, 2025 at 11:44 PM, Tor at 1AEO via tor-relays <tor-relays(a)lists.torproject.org> wrote: > Couldn't find an updated single reference of Tor relay trackers. > Summarized up the main active trackers, as each varies slightly in data and presentation. > Please take a look and let me know if anything’s missing or needs updating. > > Tracker List: Table pasted below; screenshot attached > Also viewable on our blog (with working links): > https://1aeo.com/blog/navigating-tor-relay-trackers-measure-compare.html > > Our favorite: Allium – super easy to deploy, offers ASN and family-level summaries, and update interval is configurable (ours refreshes every 30 min): > https://1aeo.com/metrics/ > Source: https://git.jordan.im/allium/ > > Thanks for your input, and happy operating! > > > > Name > > Live May '25 > > Bandwidth > > Aggregate By Family or AS > > Top 10 > > Charts & Graphs > > Map/Geo Features > > Update Frequency > > Search & Filter > > Relay Details > > Historical Data > > Source Code > > Source Last Updated > > Tor Relay Search > > Yes > > Yes > > Yes > > Yes > > Yes > > No > > Continuously > > Nickname, Fingerprint, ASN, and more > > Bandwidth stats; Configuration; Uptime; Flags; Exit policy > > Bandwidth stats > > Partial > > 12/20 > > OrNetStats > > Yes > > Yes > > Yes > > Yes > > Yes > > No > > Monthly > > Operator > > Bandwidth, Configuration; Uptime; Flags; Exit policy > > Guard/Exit probability trends > > Partial > > 05/25 > > 0x7c0 Relay Metrics > > Yes > > Yes > > Yes > > Yes > > No > > No > > Hourly > > ASN; Families > > Bandwidth, Configuration; Uptime; Flags; Exit policy > > No > > Yes > > 06/24 > > Onionite > > Yes > > Yes > > No > > Yes > > No > > No > > On-demand > > Relays/Bridges search > > Bandwidth; Configuration; Uptime; Flags; Exit policy > > Bandwidth > > Yes > > 02/23 > > TorStatus > > Yes > > Yes > > No > > Yes > > No > > No > > ~15-minute > > Country; Flags; Contact > > Bandwidth, Configuration; Uptime; Flags; Exit policy > > No > > Yes > > 02/25 > > TorMap > > No > > — > > — > > — > > — > > — > > — > > — > > — > > — > > Yes > > 05/25 > > >

1 0

Request to redact reverse DNS (host name) for my relay
by Tor ITA Relay 24 Jun '25

24 Jun '25

Hello Tor Team, I am running a Tor relay and have noticed that the reverse DNS (host name) of my IP address is publicly shown on metrics.torproject.org. For privacy reasons, I would like to kindly request that the host name be redacted. Relay fingerprint: B8D94C8036FEE5253E32CA3158E916466191C407 Thank you very much for your time and support. Best regards, Gianluca

3 2

Some learning points and conclusions for our AMA
by Nothing to hide 21 Jun '25

21 Jun '25

Hi fellow operators, The first Ask Me Anything by Tor operators was held on 13-06-2025. The result can be viewed here: https://www.reddit.com/r/TOR/comments/1la9zgw/tor_operators_ask_me_anything/. We also made a quick evaluation for learning and improving the format going forward. This (and other AMA stuff) can be viewed here: https://codeberg.org/nothingtohide/TorAma/src/branch/main/250613-AMA-1/eval…. If you have any questions or suggestions, feel free to reach out. Have a great day, Nothing to hide

1 0

Attempting to create a relay with Orbot
by blueapple128 20 Jun '25

20 Jun '25

Hi, I am trying to use Orbot's "Enable your device to be a non-exit relay" option, but (after waiting enough hours) the relay's nickname fails to show up in Tor Metrics' Relay Search. How can I begin to debug this?

2 2

Tor Operators Ask Me Anything - 13-06-2025
by Nothing to hide 13 Jun '25

13 Jun '25

Hi Tor operators, We already briefly mentioned an upcoming Ask Me Anything (AMA) by Tor operators during the Tor Operator Meetup on the 10th of May. And now it's time for the announcement: https://www.reddit.com/r/TOR/comments/1krv4rt/tor_operators_ask_me_anything…. During this AMA, anyone can engage with us directly and ask us anything they're curious about. The following Tor operators are participating: R0cket, Nothing to hide, Artikel10 and CCC Stuttgart. The Ask Me Anything will be held on Friday 13 June 2025 between 08:00-23:00 UTC on /r/TOR. Feel free to ask your questions the 13th or to share this AMA with people or your communities. We also have a post on Mastodon to share: https://mastodon.social/@tor_ama/114545560947637613. We're experimenting with this format to see whether it benefits the community. Our goal is to provide answers and context about Tor, dispel myths and inspire more people to become Tor operators--or encourage current operators to expand their efforts, perhaps by scaling up or running exit relays. This initial AMA will help us learn from our mistakes and if successful, establish a regular series where other operators (of all shapes and sizes) can participate. We're looking forward to the 13th of June! And if anyone has questions about the AMA, feel free to ask them or send people our way :). Have a great day, Nothing to hide

1 1

upcoming CIISS update
by nusenu 10 Jun '25

10 Jun '25

Hi, I'm working on a new contactinfo information sharing specification version. Current version (2): https://nusenu.github.io/ContactInfo-Information-Sharing-Specification/ Some likely changes will be: * add happy family proof https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/407/diffs * add signal username field https://support.signal.org/hc/en-us/articles/6712070553754-Phone-Number-Pri… * maybe add keyoxide field as suggested by boldsuck: https://github.com/nusenu/ContactInfo-Information-Sharing-Specification/iss… Feel free to send me your suggestions and opinions before 2025-06-30 by creating github issues or by replying to this thread. kind regards, nusenu -- https://nusenu.github.io

1 0

Observing Moria1’s Higher Missing-Relay Measured Rate (May 24–30 2025)
by Tor at 1AEO 04 Jun '25

04 Jun '25

Been exploring how each directory authority measures relays and noticed that, over the week of May 24–30, Moria1 consistently reports significantly fewer relays measured than its peers—about 6% missing versus ~3.5% for most other authorities (over 2 σ below the mean). Quick stats (May 24–30): - Moria1: Weekly missing avg = 556 relays, Z-score = 2.44 - All authorities: Mean missing = 314 relays, σ = 99 Attached the full spreadsheet, some tables, and charts below. Has anyone else spotted this pattern or have ideas why Moria1’s “number of relays voted about” is lower? Any insights or pointers would be greatly appreciated! Sharing on tor-relay list as the ticket that caught my attention doesn't allow me to comment as I'm not part of the "project": https://gitlab.torproject.org/tpo/network-health/analysis/-/issues/90 Source: Used "Number of relays voted about" section of Consensus Health pages. Ex: https://consensus-health.torproject.org/consensus-health-2025-05-24-03-00.h… Attached xlsx with all the same data shared below. "Number of Relays Voted About" for May 24th to 30th 2025 Authority Weekly Missing Average Z-score moria1 556 2.44 longclaw 231 0.84 dizum 233 0.82 faravahar 263 0.51 tor26 363 0.49 maatuska 287 0.27 gabelmoo 292 0.23 bastet 296 0.18 dannenberg 308 0.07 Average 314 Standard Deviation 99 Authority 05-30-25 05-29-25 05-28-25 05-27-25 05-26-25 05-25-25 05-24-25 Average moria1 93.31% 93.90% 94.10% 93.86% 93.86% 94.09% 92.81% 93.71% tor26 95.05% 97.39% 96.28% 95.95% 95.95% 95.94% 94.56% 95.87% dizum 96.46% 97.78% 97.92% 97.83% 97.83% 97.84% 96.10% 97.40% gabelmoo 96.55% 96.92% 97.16% 96.83% 96.83% 96.81% 95.55% 96.66% dannenberg 95.60% 96.84% 97.19% 96.85% 96.85% 96.90% 95.73% 96.57% maatuska 96.17% 96.73% 97.37% 96.97% 96.97% 97.05% 95.73% 96.71% longclaw 97.12% 97.52% 97.74% 97.59% 97.59% 97.61% 96.36% 97.36% bastet 96.35% 96.83% 97.13% 96.83% 96.83% 96.80% 95.49% 96.61% faravahar 96.76% 97.26% 97.56% 97.10% 97.10% 97.27% 95.92% 96.99% Average 95.93% 96.80% 96.94% 96.64% 96.64% 96.70% 95.36% 96.43% 05-30-25 Total Running Missing 05-29-25 Total Running Missing 05-28-25 Total Running Missing 05-27-25 Total Running Missing 05-26-25 Total Running Missing 05-25-25 Total Running Missing 05-24-25 Total Running Missing moria1 9046 8441 605 moria1 8751 8217 534 moria1 8803 8284 519 moria1 8794 8254 540 moria1 8794 8254 540 moria1 8753 8236 517 moria1 8836 8201 635 tor26 9003 8557 446 tor26 8740 8512 228 tor26 8719 8395 324 tor26 8709 8356 353 tor26 8709 8356 353 tor26 8739 8384 355 tor26 8818 8338 480 dizum 9193 8868 325 dizum 8915 8717 198 dizum 8900 8715 185 dizum 8891 8698 193 dizum 8891 8698 193 dizum 8857 8666 191 dizum 8932 8584 348 gabelmoo 8951 8642 309 gabelmoo 8678 8411 267 gabelmoo 8718 8470 248 gabelmoo 8708 8432 276 gabelmoo 8708 8432 276 gabelmoo 8664 8388 276 gabelmoo 8743 8354 389 dannenberg 9191 8787 404 dannenberg 8916 8634 282 dannenberg 8902 8652 250 dannenberg 8893 8613 280 dannenberg 8893 8613 280 dannenberg 8858 8583 275 dannenberg 8939 8557 382 maatuska 8951 8608 343 maatuska 8678 8394 284 maatuska 8713 8484 229 maatuska 8705 8441 264 maatuska 8705 8441 264 maatuska 8655 8400 255 maatuska 8738 8365 373 longclaw 8951 8693 258 longclaw 8679 8464 215 longclaw 8718 8521 197 longclaw 8707 8497 210 longclaw 8707 8497 210 longclaw 8662 8455 207 longclaw 8743 8425 318 bastet 8950 8623 327 bastet 8675 8400 275 bastet 8718 8468 250 bastet 8707 8431 276 bastet 8707 8431 276 bastet 8661 8384 277 bastet 8743 8349 394 faravahar 8970 8679 291 faravahar 8748 8508 240 faravahar 8731 8518 213 faravahar 8721 8468 253 faravahar 8721 8468 253 faravahar 8678 8441 237 faravahar 8755 8398 357 consensus 8664 consensus 8446 consensus 8508 consensus 8465 consensus 8465 consensus 8428 consensus 8389 [image.png] [image.png]

2 1

Navigating Top Relay Trackers: Measure and Compare Tor Nodes
by Tor at 1AEO 27 May '25

27 May '25

Couldn't find an updated single reference of Tor relay trackers. Summarized up the main active trackers, as each varies slightly in data and presentation. Please take a look and let me know if anything’s missing or needs updating. Tracker List: Table pasted below; screenshot attached Also viewable on our blog (with working links): https://1aeo.com/blog/navigating-tor-relay-trackers-measure-compare.html Our favorite: Allium – super easy to deploy, offers ASN and family-level summaries, and update interval is configurable (ours refreshes every 30 min): https://1aeo.com/metrics/ Source: https://git.jordan.im/allium/ Thanks for your input, and happy operating! Name Live May '25 Bandwidth Aggregate By Family or AS Top 10 Charts & Graphs Map/Geo Features Update Frequency Search & Filter Relay Details Historical Data Source Code Source Last Updated [Tor Relay Search](https://metrics.torproject.org/rs.html) Yes Yes Yes Yes Yes No Continuously Nickname, Fingerprint, ASN, and more Bandwidth stats; Configuration; Uptime; Flags; Exit policy Bandwidth stats [Partial](https://github.com/torproject/metrics-web) 12/20 [OrNetStats](https://nusenu.github.io/OrNetStats/) Yes Yes Yes Yes Yes No Monthly Operator Bandwidth, Configuration; Uptime; Flags; Exit policy Guard/Exit probability trends [Partial](https://github.com/nusenu/OrNetStats) 05/25 [0x7c0 Relay Metrics](https://relays.0x7c0.com/) Yes Yes Yes Yes No No Hourly ASN; Families Bandwidth, Configuration; Uptime; Flags; Exit policy No [Yes](https://git.jordan.im/allium) 06/24 [Onionite](https://onionite.net/) Yes Yes No Yes No No On-demand Relays/Bridges search Bandwidth; Configuration; Uptime; Flags; Exit policy Bandwidth [Yes](https://github.com/lukechilds/onionite) 02/23 [TorStatus](https://torstatus.rueckgr.at/) Yes Yes No Yes No No ~15-minute Country; Flags; Contact Bandwidth, Configuration; Uptime; Flags; Exit policy No [Yes](https://github.com/paulchen/torstatus) 02/25 [TorMap](https://tormap.org/) No — — — — — — — — — [Yes](https://github.com/TorMap/tormap) 05/25 [image.png]

1 0

Tor Relay Deployment Dilemma: When to Not Pay for Underutilized Server Resources?
by Tor at 1AEO 23 May '25

23 May '25

Part 3 - Looking for feedback on our Tor relay configuration decision: Looking for guidance on optimizing server / bandwidth spending for Tor guard / middle relays across datacenters. Our current setup: - All same cost: Three servers in different datacenters, each with 10 Gbps unmetered bandwidth. - Identical hardware/software: Each server has 128 threads, 512GB–768GB RAM, and the same software stack. - Diversity benefits: Each server hosts fewer than 10 other relays, enhancing overall network diversity. - Primary differences: Geographic location and upstream peering/routing. Current Utilization: - Server 1: 2Gbps utilized (20% utilization) - Server 2: 6Gbps utilized (60% utilization) - Server 3: 8Gbps utilized (80% utilization) Overall, using 16 Gbps out of 30 Gbps purchased -- roughly half our bandwidth is idle / "wasted". Assuming we can't significantly optimize these servers any further and given the significant under utilization on Server 1 (80% idle) and Server 2 (40% idle), what would you do in this scenario? Some options we’re considering: - Consolidation: Paying only for the servers with the highest utilization. - Repurposing: Allocating the idle bandwidth to another purpose that benefits Tor (or a similar effort). - Reinvestment: Using the funds from Servers 1 and 2 to acquire additional high-utilization capacity (e.g., more of Server 3 configuration) to boost our overall contribution closer to 24 Gbps. - Other strategies: Any alternative approaches you might suggest. Appreciate any thoughts or best practices to help reduce wasted expenditure while maximizing the utility of our available resources. Thanks for your insights!

3 8

Seeking Advice on Running a Tor Exit Node in India
by RUSTEDUSTED 19 May '25

19 May '25

Dear Tor Operators, I hope this message finds you well. I am planning to set up a Tor exit node and would like to seek your valuable advice and guidance before proceeding. Specifically, I want to understand the following: - What are the essential technical and operational considerations I should be aware of before running an exit node? - Are there best practices or configurations you recommend to ensure the node runs securely and efficiently? - What kind of bandwidth allocation is ideal? I am considering allocating around 30-40 Mbps on my internet connection—would this be sufficient or optimal? - Could you please share insights on the legal responsibilities and potential risks involved with operating a Tor exit node in India? - Are there any specific resources, communities, or contacts you recommend I engage with for ongoing support? - (most importantly) what hardware accelerations should my device support?? is it fine if i run it on raspberry pi 5 or would it need a modern x86 CPU? I appreciate any advice or resources you can share. I am eager to contribute responsibly and effectively to the Tor network. Thank you very much for your time and help. Best regards, Pradnyesh Email: rustedusted(a)proton.me Location: Pune, India

3 2