Hello,

This issue occurs in Onionoo when there are problems with Collector, as has been the case over the past few weeks.

In our current pipeline, Onionoo fetches several documents from Collector. These documents are then processed and used to provide the information exposed through the Onionoo API and relay-search.

If there is any misalignment between Collector and Onionoo, some of the data may not be set correctly during processing. One of the fields that is particularly affected in this situation is the first_seen field.

We are currently working on a new pipeline that should address these kinds of issues among other things. However, the API for this new pipeline is not currently online, we took it offline during a recent database migration, so I cannot provide a solution at the moment.

If you are a researcher and you are interested some particular data points that is messed up on onionoo maybe I could help you with that.

Talk soon,

-hiro 

On 6/3/26 03:43, mossy_road_523--- via network-health wrote:
I used the Advanced Search box on Tor Metrics to look for all running bridges with a start day between 9999 and 30000 days ago (the epoch was 20556 days ago).
The webpage complained about the size of the result set, and handed back the first 2000.
So, there are a lot of bridges in the "First Seen == epoch" state.
(The tool wouldn't allow a starting value > 9999, so I had to use that. 9999 days is > 27 years, so there's certainly no bridge with a real First Seen date from over 27 years ago.)
_______________________________________________
network-health mailing list -- network-health@lists.torproject.org
To unsubscribe send an email to network-health-leave@lists.torproject.org