View Relay "7861388051409175"

Family: 13 relays | john_rt291141(at)proton(dot)me | AS60404 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Running, V2Dir, Valid (4)
BW Verified
0/6 BW Auths Measured
Stability
Not Overloaded | UP 5h 14m 44s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3h 17m 18s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: Time Known below threshold : Time Known 0.0 days is below 8 days requirement (8.0 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • Guard: requires Stable flag : Guard flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • Not eligible for Stable flag : Uptime or MTBF below network median for most authorities
    Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
  • HSDir: Time Known below threshold : Time Known 1.1 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • Low bandwidth authority measurements : Only 0/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

Connectivity and Location

Addresses
OR Address
5.255.97.184:9001
Exit Address
5.255.97.184
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS60404
AS Name
The Infrastructure Group B.V. (BGP.tools)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Below 0 bit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 0.0d (0/9 DA above threshold)
Min/Max: 0.0d / 0.0d (9/9 DA, Voting / Total Eligible)		 ≥22.0d - 54.1d (varies)
[Stricter] moria1: ≥405.3d
Uptime Below 0.2d (R) ≥9.3d - 10.0d (varies)
HSDir Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 0/9 authorities assigned Fast flag ≥5/9 authorities
WFU Meets Majority: 100.0% (9/9 DA) ≥98.0%
Time Known Below Median: 0.0d (0/9 DA above threshold)
Min/Max: 0.0d / 0.0d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below 0/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Meets Majority: 100.0% (9/9 DA) ≥98% (all authorities)
Time Known Below (need 8.0 more days) Median: 0.0d (0/9 DA above threshold)
Min/Max: 0.0d / 0.0d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 0 bit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 16:15:07).

Last fetch was at Thu, 29 Jan 2026 17:15:44 GMT.

Nickname
7861388051409175
Fingerprint
C8997C4BD3BE77D820EBD382766E70DFC150E34E
AROI (?)
none
Contact
john_rt291141(at)proton(dot)me
IPv4 Exit Policy Summary 
accept: 
  80
  443
  8080
  8443
IPv6 Exit Policy Summary 
none
Exit Policy 
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 5.255.97.184:*
accept *:80
accept *:443
accept *:8080
accept *:8443
reject *:*
Effective Family Members: 13 (View) 
1EF5EABE2FD572F4C0AEBAB6993B6DD4A29FC897
2739C3580FE65466FE93721EADA1D47478EE718C
285B3195256DEA66C7F58C0596B17D923788056C
3117B3808524C537EC8C866D6F2A0C2E790051C9
5847D5A01C47166143F738C7703344517B39EB10
5C0433FD8F7C30FB8BF99AB7CA63F3DB43226935
80BFA9FB374B691641D9E76DF961D31DB94DE083
8D5BA8BDD806A4A8E9A6A2CB24A4790A7E65F76E
A22F6515E4ABA5A5B9D280F9296530A2198C6E22
A46C00331868D067D77934EEDED51EBA7B70DFED
C8997C4BD3BE77D820EBD382766E70DFC150E34E
F0414FB9520E5DB41E156C1B7EEF7300BDD41CF3
F6EB1D746A67E28AE775249FFD0CBBBFB94C3E45
Alleged Family Members: 2 
01E44F7EE449B38FA95236791E67A39786CDBDB6
87E1475430F00544872D7D83D191CF7EB6752660
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
0.00 Kbit/s | unknown| 24.58 Mbit/s| 8.59 Gbit/s  Not Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
N/A | N/A | N/A | N/A
OR Address
5.255.97.184:9001
Exit Address
none
Dir Address
none
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS60404 | The Infrastructure Group B.V. (BGP.tools)
Flags: 4
Exit Exit Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
N/A
Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 5h 14m 44s ago
Seen (First | Last)
3h 17m 18s ago (2026-01-29 14:00:00) | 1h 17m 18s ago (2026-01-29 16:00:00)
Last Restarted
5h 16m 17s ago (2026-01-29 12:01:01)
Last Changed Address or Port
2026-01-29 14:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status)
0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-29 16:15:07).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 0 bit/s | Min: 0 bit/s | Max: 0 bit/s
  • Identified Issues:
    • Guard: Time Known below threshold: Time Known 0.0 days is below 8 days requirement (8.0 more days needed)
      • Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
    • Guard: requires Stable flag: Guard flag requires having the Stable flag first
      • Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
    • Guard: requires Fast flag: Guard flag requires having the Fast flag first
      • Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
    • Not eligible for Stable flag: Uptime or MTBF below network median for most authorities
      • Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
    • HSDir: Time Known below threshold: Time Known 1.1 hours below 25 hours (dir-spec default)
      • Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
    • Low bandwidth authority measurements: Only 0/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
      • Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 0 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 100.0% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 0.0 days ≥8 days (all authorities) BELOW - need 8.0 more days
Guard BW (Relay Reported) 0 bit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.2d ≥9.3d - 10.0d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 0 days ≥22.0d - 54.1d (typical)
[Stricter] moria1: ≥405.3d 		BELOW - 0/9
Fast Speed (Relay Reported) 0 bit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		BELOW - need ≥100 KB/s
HSDir WFU (Dir. Auth., wfu) 100.0% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 0.0 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/9

Per-Authority Details

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority Running Valid BW Scan (Authority) v4 Flags Fast (Relay|T) Guard BW (Relay|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) HSDir WFU (M|T) HSDir TK (M|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 49.8d 0.2d | 10.2d 100.0% | 98.0% 0.0d | 1.0d 2026-01-29 13:43:04 —
dannenberg (DE) Yes Yes N Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 22.0d 0.2d | 10.0d 100.0% | 98.0% 0.0d | 1.0d 2026-01-29 13:43:04 —
dizum (NL) Yes Yes N Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 34.7d 0.2d | 10.0d 100.0% | 98.0% 0.0d | 1.0d 2026-01-29 13:43:04 —
faravahar (US) Yes Yes N Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 47.2d 0.2d | 9.3d 100.0% | 98.0% 0.0d | 1.0d 2026-01-29 13:43:04 —
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 54.1d 0.2d | 10.0d 100.0% | 98.0% 0.0d | 1.0d 2026-01-29 13:43:04 —
longclaw (US) Yes Yes Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 54.7d 0.2d | 9.6d 100.0% | 98.0% 0.0d | 1.0d 2026-01-29 13:43:04 —
maatuska (SE) Yes Yes Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 54.9d 0.2d | 9.5d 100.0% | 98.0% 0.0d | 1.0d 2026-01-29 13:43:04 —
moria1 (US) Yes Yes Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 405.3d 0.2d | 9.9d 100.0% | 98.0% 0.0d | 9.9d 2026-01-29 13:43:04 —
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 55.9d 0.2d | 10.8d 100.0% | 98.0% 0.0d | 1.0d 2026-01-29 13:43:04 —

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). This is your relay's self-reported uptime from its descriptor. Same value for all authorities.
Authority Threshold = From CollecTor vote files (flag-thresholds stable-uptime). Each authority may have different thresholds.
Why two sources? Vote files contain authority thresholds but not per-relay uptime values. Onionoo aggregates relay descriptors which include uptime.