It's great to see more geographic diversity of Tor relays!
Currently, looks like two main issues and a minor third issue for forest18
1) Stable flag: struggling with consistent ORPort reachability from 8 of 9 voting directory authorities ("Stable MTBF" in source below)
2) Fast flag: The speed is also very slow, shown by very low bandwidth scanner results from the 6 bandwidth directory authorities (Consensus Weight from Authorities, i.e. "Cons Wt" in source below)
3) Uptime: Relay reports and operator directly controls, also shows low, ~2 days.
Source: https://metrics.1aeo.com/relay/6435C5172690160DA25681BEBA1EA5EAC6F2BE70/#authority-votes
On Friday, December 19th, 2025 at 12:33 PM, forest-relay-contact--- via tor-relays <tor-relays@xxxxxxxxxxxxxxxxxxxx> wrote:
>
>
> 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,
> forestAttachment:
publickey - tor@1aeo.com - 0x9288289B.asc
Description: application/pgp-keys
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-relays mailing list -- tor-relays@xxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to tor-relays-leave@xxxxxxxxxxxxxxxxxxxx