On Fri, Dec 26, 2025 at 01:12:30AM -0000, forest-relay-contact--- via tor-relays wrote:
Hello.
One of my relays, forest19 (E21B4A2C2852298186C0EA7E2F900EF03AE38D69), frequently appears offline in the consensus despite my uptime monitors and bandwidth graphs showing uninterrupted activity. About once a day to once every other day, I get a Tor Weather notice that my relay has been offline for the last 4 hours.
The relay is able to ping all authorities but Sarge, and I am not seeing abnormally high packet loss. How do I troubleshoot this?
One really helpful tool is looking at the individual votes, to see if there is a pattern of *which* dir auths can / can't reach you. Go to the bottom of https://consensus-health.torproject.org/#relayinfo and put in forest19 and click load, and we see that at this moment, you have five Running votes (from moria1, tor26, gabelmoo, dannenberg, and maatuska), and that's a majority of nine so you are considered Running, but it sure is close to not a majority. I'm running a tcptraceroute from an IP address nearby moria1 and it works, but from moria1's outbound IP address (128.31.0.39) my tcptraceroute currently fails after 212.20.21.242 -- that is, it appears something in Russia is filtering on moria1's IP address. It looks from moria1's logs like I could reach you an hour ago (at 21:31:04 EST) but the tests after that (at 21:52:24, at 22:13:44, at 22:35:04 all EST) have failed. So I am all set to vote not Running for you in the next vote, and maybe that will be enough to lose your Running flag again. Your IPv6 address is reachable the whole time. Since this is a Russian router we are talking about, one possibility is that they are censoring the public Tor relay IP addresses, but doing it only sometimes, or on some routes (which could look like sometimes as the routes change). --Roger