Since you mentioned first seen date issues, we published a workaround that provides more accurate values, +- 10 days, for up to 5 years, using the uptime API data from Onionoo. Nothing beyond 5 years is easily available making 5 years the current limit.
When Onionoo resolves first seen data quality issue, we'll switch back to that. Following along here: https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/work_items/40055 On Thursday, May 14th, 2026 at 1:45 PM, ProSecureRelays <[email protected]> wrote: > Hey there, > > thank you so much for you quick response and updating the site – now > everything looks fine! > > I was really confused if the error was not on my end. > > And thank you to both of you for hosting the metrics sites! > > Best regards, > > Joker > > Von: Tor at 1AEO via tor-relays [mailto:[email protected]] > Gesendet: Montag, 11. Mai 2026 07:37 > An: support and questions about running Tor relays (exit, non-exit, bridge) > Cc: ProSecureRelays; Tor at 1AEO > Betreff: [tor-relays] Re: AROI Validation vanished due to ciissversion:3 on > 1AEO Metrics > > Just updated and everything should be live now. > > Your validation looks good with v3: > https://metrics.1aeo.com/johnschnee1337.github.io/ > > Glad the web site is helpful! > > On Monday, May 4th, 2026 at 1:09 AM, ProSecureRelays via tor-relays > <[email protected]> wrote: > > Hey there, > > is there any information out regarding the AROI-Status and the trasisition > from ciisversion:2 to ciisversion:3? > > I was proud having it all setup, but then I followed the advice on creating > an ed25519 key and added the proof in my github page. > > The setup was done correctly as far as I can see, however, this led to > loosing my AROI Status :‘( … > > I’m happy if someone sees my fault or has a clue what to do now to get the > AROI back. > > Of course it would be easy to just revert the change to the contact info, but > the must be a „Go-Live“ when the ciisv3 is the desired value? > > Best regards, > > Joker > > P.S. > > What I also noticed – I have only one relay, but since I configured the > ed-key, there was a notice in the tor log that MyFamily Descriptor is still > needed aswell. > > [warn] FamilyId was configured, but MyFamily was not. FamilyId is good, but > the Tor network still requires MyFamily while clients are migrating to use > family keys instead. > > As with one relay, I didn’t see the benefit, but added the fingerprint as > desired with the MyFamily Option. The warning is gone since then. > > Additionally I also lost my „First-Seen“ Date when doing the change to v3. > But I heard this is already under investigation. > > Picture 1: Happy Family Cert is installed and valid. > > Picture 2: 1AEO stats claims missing ciisversion:2. > > Picture 3: On the Page from Nusenu (OrNetStats), I still see myself as > verified, but the update rate is quite low. This reflects the data before the > change.
publickey - [email protected] - 0x9288289B.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ tor-relays mailing list -- [email protected] To unsubscribe send an email to [email protected]
