[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-relays] Re: Relay forest18 is still not on the consensus

To: tor-relays@xxxxxxxxxxxxxxxxxxxx
Subject: [tor-relays] Re: Relay forest18 is still not on the consensus
From: forest-relay-contact--- via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx>
Date: Fri, 19 Dec 2025 20:32:42 -0000
In-reply-to: <176552590017.445321.6572093112154051554@lists-01.torproject.org>
List-id: "support and questions about running Tor relays (exit, non-exit, bridge)" <tor-relays.lists.torproject.org>
References: <176552590017.445321.6572093112154051554@lists-01.torproject.org>
Reply-to: forest-relay-contact@xxxxxxxxxxxxx
User-agent: HyperKitty on https://lists.torproject.org/

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

It seems they are no longer blocking all of the directory authorities
and forest18 has finally appeared on the consensus. This is despite
them being less than helpful in a support ticket, as they demanded that
I do a KYC check to run a Tor relay in their India location (I'm not
sure if they really understood that it was a non-exit).

Right now, only Serge (66.111.2.131) is blocked. Sadly, this provider
does not support IPv6, so I cannot try to connect to Serge over that.
But either way, enough authorities can now see the relay that it has
been added to the consensus and traffic is slowly ramping up.

Regards,
forest
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEvLrj6cuOL+I/KdxYBh18rEKN1gsFAmlFtl8ACgkQBh18rEKN
1gsINg/+NOCGetyZk340nTDPvTLjdJksqm7fqEXKmNUzwYeC2h7i4mTtm9bX3OiO
pvaD7C6l9B3ai2vI9w32jRWR6M8l2DI2JclviyUVKIxnhexdYim/2jVJQZMfNyuW
/EcB0ty082J8bwUG0nhHLBms+Hvd/M8sn+J5o5N6KMc9+jyA1i0ocmc1fprx9vqT
SG0t4ULHwzmWIQOJQ0HE/inR4ur68WgsGFh3e/9twVIhLn10JWbQub4kaPLGs+lI
IFuhNKOw6ZOEXPq+ehxxEpR2s01qsPB0avzOBghHYI5TiexnHNn2c4j2qQZAF/Ig
ufzJq0tzSTvyq2awfpjitOyN7zFvFoCUGxXRQ60hAxQJD8BOvvGWmGdCH71Gf6HO
fcmMK6DS7P0u0xuEt95tJDYAGBVxw/RVcz/g6jFa76RZ9PIV1oCEyyjDH8a97LA0
tT1akEXqhRC4P5G5JAccliSBSdijoZl6eaSw8h5e8WxpMJh7EFWJKfVdi4WfCj93
NEjlOCSb8/bxrnJJke+ibnWtHAIuwYSw7YlTuCg3ES1EEDouBiBTaF6kxI4Qk+xL
xuYUSyjxifoz+MjEzxikaMDyC7lnf/LnKkPhx2h1ZDP0TpHpukUnPkvp7cLwgLiQ
Us2EIJYmAhN91uKPUBYQfssJ/3hm5uAoUIKDELvdk6SaPXTgZII=
=tqJ/
-----END PGP SIGNATURE-----
_______________________________________________
tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx

Follow-Ups:
- [tor-relays] Re: Relay forest18 is still not on the consensus
  - From: George via tor-relays
- [tor-relays] Re: Relay forest18 is still not on the consensus
  - From: John Crow via tor-relays
- [tor-relays] Re: Relay forest18 is still not on the consensus
  - From: Tor at 1AEO via tor-relays

References:
- [tor-relays] Re: Relay forest18 is still not on the consensus
  - From: forest-relay-contact--- via tor-relays

Prev by Author: [tor-relays] Re: Relay forest18 is still not on the consensus
Next by Author: [tor-relays] Re: abuse report from relays in family 7EAAC49A7840D33B62FA276429F3B03C92AA9327
Previous by thread: [tor-relays] Re: Relay forest18 is still not on the consensus
Next by thread: [tor-relays] Re: Relay forest18 is still not on the consensus
Index(es):
- Author
- Thread