network-health

network-health@lists.torproject.org

February 2026

2 participants
2 discussions

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

27 Feb '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

1 0

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