Hi nusenu,
This can be tracked here:
https://gitlab.torproject.org/tpo/network-health/metrics/onionoo/-/issues/40055
Keep in mind that we recently replaced the legacy Collector service with
a rewrite in Rust, due to performance and memory issues in the old
implementation. The new service has been tuned for production, which has
required frequent restarts. sometimes multiple times a day. While no
data has been lost (a parallel instance running the old code syncs with
the new one daily at 2 AM), the restarts have caused an erratic
scheduler. This may have impacted Onionoo and any other service or
application that depends on Collector for its data.
The status update issues are, I hope, most likely a symptom of this
transitional period rather than a deeper bug. My current priority is to
stabilise the Collector pipeline, and once that is done, to monitor
downstream services for any lingering issues.
Cheers,
-hiro
On 11/4/26 23:09, nusenu wrote:
Hi hiro,
this still appears to be an issue as of onionoo data from 2026-04-11
18:00 UTC.
Is there a gitlab issue I could follow to learn about the status
and maybe timeline for the solution as this field is becoming crucial
for me?
kind regards,
nusenu
_______________________________________________
tor-relays mailing list -- [email protected]
To unsubscribe send an email to [email protected]
