View Relay "DonationFromHERMES"

Family: 1 relay | Random Person jack06loveyou@protonmail.com | AS212477 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 10 Kbit/s Median
Stability
Not Overloaded | UP 1d 8h 5s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
4d 5h 47m ago
BW Weight
0.00% of Network | 15 Mbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 2.0 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • Guard: Time Known below threshold : Time Known 4.2 days is below 8 days requirement (3.8 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).
  • 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.
  • High consensus weight deviation : Large variation in Consensus Weight values across authorities (see 'Cons Wt' column in Per-Authority Details below)
    Suggestion: Consensus weight measurements vary significantly between authorities. This can affect traffic distribution. Ensure stable network connection and consistent bandwidth availability.

Connectivity and Location

Addresses
OR Address
89.125.187.93:443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS212477
AS Name
RoyaleHosting BV (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.17% consensus weight, 12 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/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 Meets (≥100 KB/s) 15.8 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 2.5d (0/9 DA above threshold)
Min/Max: 2.3d / 2.5d (9/9 DA, Voting / Total Eligible)		 ≥22.3d - 52.0d (varies)
[Stricter] moria1: ≥442.5d
Uptime Below 1.3d (R) ≥6.4d - 7.6d (varies)
HSDir Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 8/9 authorities assigned Fast flag ≥5/9 authorities
WFU Meets Majority: 98.7% (5/9 DA)
Min/Med/Max: 98.4% / 98.7% / 98.7% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Below Median: 4.2d (0/9 DA above threshold)
Min/Max: 3.3d / 4.2d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets 8/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: 98.7% (5/9 DA)
Min/Med/Max: 98.4% / 98.7% / 98.7% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Below (need 3.8 more days) Median: 4.2d (0/9 DA above threshold)
Min/Max: 3.3d / 4.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 15.8 Mbit/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-02-11 22:45:07).

Last fetch was at Wed, 11 Feb 2026 23:45:42 GMT.

Nickname
DonationFromHERMES
Fingerprint
247089BBE9E1734DBEDB49A1FA0FC0627114E538
AROI (?)
none
Contact
Random Person jack06loveyou@protonmail.com
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
247089BBE9E1734DBEDB49A1FA0FC0627114E538
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
15.84 Mbit/s | 10.91 Mbit/s| 10.91 Mbit/s| 16.78 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
89.125.187.93:443
Exit Address
none
Dir Address
none
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS212477 | RoyaleHosting BV (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 1d 8h 5s ago
Seen (First | Last)
4d 5h 47m ago (2026-02-07 18:00:00) | 1h 47m 16s ago (2026-02-11 22:00:00)
Last Restarted
1d 8h 1m ago (2026-02-10 15:45:39)
Last Changed Address or Port
2026-02-07 20:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.22 on Linux
Version (Running | Recommended | Status)
0.4.8.22 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-02-11 22:45: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: 8/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 10.9 Kbit/s | Min: 8 bit/s | Max: 21.6 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 2.0 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
      • Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
    • Guard: Time Known below threshold: Time Known 4.2 days is below 8 days requirement (3.8 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).
    • 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.
    • High consensus weight deviation: Large variation in Consensus Weight values across authorities (see 'Cons Wt' column in Per-Authority Details below)
      • Suggestion: Consensus weight measurements vary significantly between authorities. This can affect traffic distribution. Ensure stable network connection and consistent bandwidth availability.

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.) 10.9 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 98.7% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 4.2 days ≥8 days (all authorities) BELOW - need 3.8 more days
Guard BW (Relay Reported) 15.8 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 1.3d ≥6.4d - 7.6d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 2 days ≥22.3d - 52.0d (typical)
[Stricter] moria1: ≥442.5d 		BELOW - 0/9
Fast Speed (Relay Reported) 15.8 Mbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 98.7% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 4.2 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.8d 		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 15.8 Mbit/s | 816.0 Kbit/s 15.8 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 4.2d | 8d 2.5d | 52.0d 1.3d | 7.6d 98.7% | 98.0% 4.2d | 1.0d 2026-02-11 09:45:44 8 bit/s
dannenberg (DE) Yes Yes N Yes Running, Valid, V2Dir, Fast 15.8 Mbit/s | 712.0 Kbit/s 15.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 4.2d | 6d 2.5d | 22.3d 1.3d | 6.4d 98.7% | 98.0% 4.2d | 1.0d 2026-02-11 09:45:44 10.9 Kbit/s
dizum (NL) Yes Yes N Yes Running, Valid, V2Dir, Fast 15.8 Mbit/s | 704.0 Kbit/s 15.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 4.2d | 6d 2.5d | 27.8d 1.3d | 6.4d 98.7% | 98.0% 4.2d | 1.0d 2026-02-11 09:45:44 10.9 Kbit/s
faravahar (US) Yes Yes N Yes Running, Valid, V2Dir, Fast 15.8 Mbit/s | 816.0 Kbit/s 15.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 4.2d | 8d 2.5d | 48.0d 1.3d | 7.6d 98.7% | 98.0% 4.2d | 1.0d 2026-02-11 09:45:44 10.9 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir, Fast 15.8 Mbit/s | 816.0 Kbit/s 15.8 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 4.2d | 8d 2.5d | 60.5d 1.3d | 7.6d 98.7% | 98.0% 4.2d | 1.0d 2026-02-11 09:45:44 5760 bit/s
longclaw (US) Yes Yes Y Yes Valid, V2Dir, Fast 15.8 Mbit/s | 816.0 Kbit/s 15.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.6% | 98% 3.9d | 8d 2.3d | 62.0d 1.3d | 7.6d 98.6% | 98.0% 3.9d | 1.0d 2026-02-11 09:45:44 10.9 Kbit/s
maatuska (SE) Yes Yes Y Yes Running, Valid, V2Dir, Fast 15.8 Mbit/s | 816.0 Kbit/s 15.8 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 3.9d | 8d 2.4d | 41.9d 1.3d | 7.6d 98.7% | 98.0% 3.9d | 1.0d 2026-02-11 09:45:44 7920 bit/s
moria1 (US) Yes Yes Y Yes Running, Valid, V2Dir, Fast 15.8 Mbit/s | 8.4 Mbit/s 15.8 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 98.4% | 98% 3.3d | 8d 2.5d | 442.5d 1.3d | 7.6d 98.4% | 98.0% 3.3d | 9.8d 2026-02-11 09:45:44 21.6 Kbit/s
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir, Fast 15.8 Mbit/s | 816.0 Kbit/s 15.8 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 4.1d | 8d 2.5d | 57.7d 1.3d | 7.6d 98.7% | 98.0% 4.1d | 1.0d 2026-02-11 09:45:44 5360 bit/s

— = 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.