- network-health - lists.torproject.org

Explanation on (negative) spikes in number of relays
by ttlns 19 Apr '26

19 Apr '26

Around 2 weeks ago, I posted the following concerns regarding "negative spikes" for the number of relays measured by metrics.torproject.org [1] in forum.torproject.org [2] (and earlier on r/TOR [3] ) : > Are there any good explanations on why these spikes occurred? > Might those outages imply some centralized infrastructure? If so, how is that not a major concern? So far, I have not received any definite explanations. If those spikes happen to be measurement errors, I imagine that there should be logs somewhere to support this explanation. 3. Does such evidence exist publicly? 4. If not (3), where would that evidence be stored? Sources: [1] http://metrics.torproject.org/networksize.html?start=2022-01-01&end=2026-03… [2] https://forum.torproject.org/t/explanation-on-negative-spikes-in-number-of-… [3] https://www.reddit.com/r/TOR/comments/1s8wx24/explanation_on_spikes_in_numb… I appreciate any clues, hints, or pointers on where to ask further. Best, ttlns

2 5

Less that two weeks old?
by Johannes Kingma 18 Apr '26

18 Apr '26

https://metrics.torproject.org/rs.html#details/DB16235B1337EEE3D0004F83EF29… I read "This relay appears to be less than 2 weeks old.This blog post <https://blog.torproject.org/lifecycle-new-relay>explains the lifecycle of a new relay, and why it will not be immediately fully used to capacity." But in fact it show history back to about 1.5 years. Has been rebooted less that 2 week ago would be better.

1 0

incorrect data on metrics.torproject.org relay search
by txt.file 14 Apr '26

14 Apr '26

Please explain how a Tor relay can have graphs on https://metrics.torproject.org/rs.html#details/506C582367B6ABED6EEF3936DCEB… since 2023-02-17 but at the same time have "First Seen 2026-04-06 23:00:00 (7 days 9 hours 22 minutes and 50 seconds)" in the data. Why has the "first seen" of my 3 year old relay reset? regards txt.file PS: Am not subscribed to this list.

2 1

500 Internal Server Error on TorMetrics site
by mossy_road_523 17 Mar '26

17 Mar '26

Repeatdly getting a "500 Internal Server Error" on the Tor Metrics website. Happens when I visit the Users page and click either the "Top 10 Countries by Relay Users" or "Top 10 Countries by Bridge Users" links. All other links on that page (Tor Metrics --> Users) work. Sent with [Proton Mail](https://proton.me/mail/home) secure email.

2 1

Possibly invalid "First seen" metadata in metrics.torproject.org
by Eric Cheng 11 Mar '26

11 Mar '26

Hi all, I checked a few webtunnel bridges, and their "First seen" dates are all showing "1970-01-01 00:00:00". https://metrics.torproject.org/rs.html#details/7A78527DBDB7EFF85E5AA926A1B9… https://metrics.torproject.org/rs.html#details/6996BC2264025E9A87D51324CF56… https://metrics.torproject.org/rs.html#details/81895A2C4E22E861615DD9127543… For the top relays, I checked a few, and instead of showing the year 1970, they showed dates with times exactly at certain hours. I feel like this kind of coincidence is weird. 2024-08-25 00:00:00 https://metrics.torproject.org/rs.html#details/9AB93B5422149E5DFF4BE6A3814E… 2025-06-26 21:00:00 https://metrics.torproject.org/rs.html#details/5835631C79E55CDFDCF9E2D14CB9… 2019-02-18 00:00:00 https://metrics.torproject.org/rs.html#details/9AB93B5422149E5DFF4BE6A3814E… Is this correct behavior? Information for relays was published: 2026-02-27 05:00:00 UTC. Information for bridges was published: 2026-02-27 03:57:24 UTC. Thanks, Eric

4 3

Exit Relay DNS Health Module for Exitmap - Seeking Guidance Before Deployment
by Tor at 1AEO 22 Feb '26

22 Feb '26

Hi Network Health Team, A few large-scale exit relay operators have asked for better visibility into DNS health across their relays. We've built an exitmap module, dnshealth, to address this and want your input before we start running scans and publishing results. What It Does - Generates unique DNS queries per relay (wildcard subdomain → expected IP) to avoid caches - Classifies failures: timeout, NXDOMAIN, wrong IP, SOCKS errors - Outputs structured JSON with latency and error details All code is open source: https://github.com/1aeo/exitmap Initial testing: ~98% success rate across ~3k exits, 50-90 true failures per scan, 4-8 min runtime. Before We Proceed 1. Any concerns with us running regular scans and publishing results? 2. Recommendations on scan frequency or methodology? Happy to adjust our approach based on your guidance.

3 6

"500 Internal Server Error" for Tor user metrics
by dutt 15 Jan '26

15 Jan '26

Hey there, https://metrics.torproject.org/userstats-censorship-events.html shows a "500 Internal Server Error". Home->Users->Top-10 countries by possible censorship events Not sure since when, but it's been like that for at least 24h. Kind regards and thanks for your work, everyone! Dutt

2 1

on blacklist
by hallogen＠posteo.de 11 Jan '26

11 Jan '26

Hello I was surprised to find that I was blacklisted on some sites. I found a long blacklist on GitHub, including my Tor relay's IP address. I've now disabled the relay, of course. Too bad. hallogen https://github.com/firehol/blocklist-ipsets/blob/master/et_tor.ipset

2 1

500 Internal Error - Top-10 countries by possible censorship events
by Culda, Alexandru 09 Jan '26

09 Jan '26

Hi there, My name is Alexandru Culda and I am a Master’s students in the Netherlands studying InfoSec. I am tasked with doing a literature review on how China’s blocking TOR and its countermeasures to circumvent the censorship. I was interested in this specific metric: Top-10 countries by possible censorship events (https://metrics.torproject.org/userstats-censorship-events.html) but it seems I get a 500 Internal Server Error. It would be tremendously helpful to get access to this list for research purposes. Its provision would be deeply appreciated, both by me and my professor. If needed, I can provide more information about the scope of the research. Deeply appreciating your time and consideration whilst hoping I could get access to this, Alexandru Culda

2 1

Hyperlinks Not Forwarding to Correct URL's
by Andrew Pelletier 05 Jan '26

05 Jan '26

https://bridges.torproject.org/info#reserved The URL's for bridge distribution mechanism(s) are not functioning anymore on metrics.torproject.org on relay pages. When I go to a relay on metrics.torproject.org and click on "Reserved" as shown in the screenshot, it no longer forwards to correct place. https://metrics.torproject.org/rs.html#details/19C9B070003C9670BB6B5693771F… Under "Bridge Distribution Mechanism" Click Reserved https://bridges.torproject.org/info#reserved And instead it forwards to this URL which does not have the relevant information. https://support.torproject.org/tor-browser/circumvention/#reserved [image.png] I found this documentation here: https://support.torproject.org/relays/running/bridge-distribution-method/ Which references this link that has the actual information: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/blob/main/doc/dis… I was wondering if these hyperlinks could be updated on metrics.torproject.org to go to the correct URL mentioned previously (e.g. for reserved): https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/blob/main/doc/dis… Thanks and appreciate the project, - Andrew Pelletier

2 1