We've rewritten CollecTor from the ground up in Rust, replacing the legacy Java service that has been increasingly unstable over the past months. The new service, collector-rs, was deployed yesterday and is now live.
Shoutout to Juga who has been the main developer behind the redesigned service.
A couple of things to be aware of:
- Data continues to be available in the usual folders, so existing workflows should not be affected.
- You may notice some folders are temporarily duplicated as part of the transition. This is cosmetic and the underlying data is consistent.
- The instability of the old CollecTor may have affected services that depend on it as an upstream data source, including Onionoo, Tor Weather, the metrics website, and any community-run services or apps that consume CollecTor data. The new deployment should resolve these issues going forward.
If you run into any issues or notice anything unexpected, please don't hesitate to reach out or open an issue on the GitLab repo.
Cheers,
hiro
···
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
We've rewritten CollecTor from the ground up in Rust, replacing the legacy Java service that has been increasingly unstable over the past months. The new service, collector-rs, was deployed yesterday and is now live.
Shoutout to Juga who has been the main developer behind the redesigned service.
A couple of things to be aware of:
- Data continues to be available in the usual folders, so existing workflows should not be affected.
- You may notice some folders are temporarily duplicated as part of the transition. This is cosmetic and the underlying data is consistent.
- The instability of the old CollecTor may have affected services that depend on it as an upstream data source, including Onionoo, Tor Weather, the metrics website, and any community-run services or apps that consume CollecTor data. The new deployment should resolve these issues going forward.
If you run into any issues or notice anything unexpected, please don't hesitate to reach out or open an issue on the GitLab repo.
Cheers,
hiro
Hi again,
We are now two weeks into the migration, and things have been a bit bumpy for the downstream services from collector. As a result, onionoo.torproject.org has sometimes returned outdated data or statuses with missing information.
I expect these issues to stabilize within this week, and things should be back to normal from next week onward. Once things are stable again, we will overwrite the first_seen field for those relays/bridges that had it reset.
Please do get in touch if you notice any issues, and thanks for being part of the Tor community.
Cheers,
-hiro
···
On 3/4/26 16:11, Silvia Puglisi [Hiro] via tor-relays wrote:
Subject: Migration Update – Temporary Service Disruptions
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org
Subject: Migration Update – Temporary Service Disruptions
Hi again,
We are now two weeks into the migration, and things have been a bit
bumpy for the downstream services from collector. As a result,
onionoo.torproject.org has sometimes returned outdated data or
statuses with missing information.
I expect these issues to stabilize within this week, and things
should be back to normal from next week onward. Once things are
stable again, we will overwrite the first_seen field for those
relays/bridges that had it reset.
Could you provide an update on the situation?
kind regards,
nusenu
···
--
_______________________________________________
tor-relays mailing list -- tor-relays@lists.torproject.org
To unsubscribe send an email to tor-relays-leave@lists.torproject.org