Incorrect First Seen metadata for two relays on Metrics / Onionoo

Support Relay Operator
,
1

**Hi, I think I may be seeing incorrect “First Seen” metadata again for two public relays.

Fingerprints:

  • 7C9D75BC8D0A9280C3C444F015C9007623B6C369 (GhostHopWarden)
  • 7B69D1B64DA534A86343B4E1D97DD099E96F30F6 (GhostHopShield)

What I checked:

  • Local `tor --list-fingerprint` matches Onionoo for both relays.
  • `/etc/tor/torrc` nicknames and MyFamily are correct on both hosts.
  • Onionoo `details?lookup=` returns both relays as running and with the expected fingerprints.
  • However, Onionoo / Metrics shows `first_seen` around 2026-04-06 for both.
  • The Metrics history graphs for both relays clearly show months of prior bandwidth / probability history, so the displayed `first_seen` appears inconsistent with the historical data.

This looks similar to earlier reports about incorrect First Seen metadata, but I’m seeing it in April 2026 for public relays rather than bridges.

I can provide full command output and screenshots if useful.**

2

Hi

Maybe this one helps.

Cheers!

3

Looking up all relays by “First Seen” date only returns 5 before 2026-04-06 23:00:00.
Every other relay before The Incident™ is set to “First Seen 2026-04-06 23:00:00” or later.

image
image1467×597 78.8 KB