View Relay "simpletorrelay"

Family: 1 relay | Random Person <[email protected]> | AS6805 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid (2)
BW Verified
5/6 BW Auths Measured 88 bit/s Median
Stability
Not Overloaded | UP 7h 42m 2s ago | UP 63% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
6y 11mo 2w ago
BW Weight
0.00% of Network | 876 Kbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.1 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: WFU below threshold : Weighted Fractional Uptime 70.3% is below 98% requirement
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • 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: WFU below threshold : WFU 70.3% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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
dynamic-002-243-172-120.2.243.pool.telefonica.de
2.243.172.120:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS6805
AS Name
Telefonica Germany GmbH & Co.OHG (BGP.tools)

Flags and Eligibility

Current Flags (2): Running, Valid
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 1/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) 876.5 Kbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 0.7d (1/9 DA above threshold)
Min/Max: 0.7d / 18615.2d (9/9 DA, Voting / Total Eligible)		 ≥22.1d - 53.8d (varies)
[Stricter] moria1: ≥406.0d
Uptime Below 0.3d (R) ≥10.5d - 11.3d (varies)
HSDir Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 4/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 71.2% (0/9 DA above threshold)
Min/Max: 70.3% / 72.6% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 10.2d (9/9 DA above threshold)
Min/Max: 10.2d / 10.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below 4/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Below 0/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 71.2% (0/9 DA above threshold)
Min/Max: 70.3% / 72.6% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 10.2d (9/9 DA above threshold)
Min/Max: 10.2d / 10.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 876.5 Kbit/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 08:45:07).

Last fetch was at Thu, 29 Jan 2026 08:45:42 GMT.

Nickname
simpletorrelay
Fingerprint
B679C6B8846FEE5369CDC19A0D2D036F4100F5FA
AROI (?)
none
Contact
Random Person <[email protected]>
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
B679C6B8846FEE5369CDC19A0D2D036F4100F5FA
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
876.46 Kbit/s | 819.20 Kbit/s| 819.20 Kbit/s| 1.64 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
dynamic-002-243-172-120.2.243.pool.telefonica.de | 2.243.172.120:9001
Exit Address
none
Dir Address
none
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS6805 | Telefonica Germany GmbH & Co.OHG (BGP.tools)
Flags: 2
Running Running Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (63.3%/45.4%/47.8%/60.7%)
Uptime (1M/6M/1Y/5Y)
63.3%/45.4%/47.8%/60.7%
Uptime / Downtime
UP 7h 42m 2s ago
Seen (First | Last)
6y 11mo 2w ago (2019-02-18 00:00:00) | 1h 47m 12s ago (2026-01-29 07:00:00)
Last Restarted
7h 43m 31s ago (2026-01-29 01:03:41)
Last Changed Address or Port
2026-01-29 02: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 08: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: 4/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 88 bit/s | Min: 24 bit/s | Max: 816 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.1 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: WFU below threshold: Weighted Fractional Uptime 70.3% is below 98% requirement
      • Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
    • 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: WFU below threshold: WFU 70.3% below 98% required for HSDir
      • Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
    • 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.) 88 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 71.2% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 10.2 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 876.5 Kbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.3d ≥10.5d - 11.3d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 1 days ≥22.1d - 53.8d (typical)
[Stricter] moria1: ≥406.0d 		BELOW - 1/9
Fast Speed (Relay Reported) 876.5 Kbit/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) 71.2% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 10.2 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 876.5 Kbit/s | 816.0 Kbit/s 876.5 Kbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 70.3% | 98% 10.2d | 8d 0.7d | 50.2d 0.3d | 12.0d 70.3% | 98.0% 10.2d | 1.0d 2026-01-29 01:21:39 88 bit/s
dannenberg (DE) Yes Yes N Yes Running, Valid, Fast 876.5 Kbit/s | 816.0 Kbit/s 876.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 71.4% | 98% 10.3d | 8d 0.7d | 22.1d 0.3d | 11.4d 71.4% | 98.0% 10.3d | 1.0d 2026-01-29 01:21:39 816 bit/s
dizum (NL) Yes Yes N Yes Running, Valid, Fast 876.5 Kbit/s | 816.0 Kbit/s 876.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 71.2% | 98% 10.7d | 8d 0.7d | 34.4d 0.3d | 11.3d 71.2% | 98.0% 10.7d | 1.0d 2026-01-29 01:21:39 816 bit/s
faravahar (US) Yes Yes N Yes Running, Valid, Fast 876.5 Kbit/s | 816.0 Kbit/s 876.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 71.4% | 98% 10.2d | 8d 0.7d | 47.2d 0.3d | 10.5d 71.4% | 98.0% 10.2d | 1.0d 2026-01-29 01:21:39 816 bit/s
gabelmoo (DE) Yes Yes Y Yes Running, Valid 876.5 Kbit/s | 816.0 Kbit/s 876.5 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 71.2% | 98% 10.7d | 8d 0.7d | 53.8d 0.3d | 11.4d 71.2% | 98.0% 10.7d | 1.0d 2026-01-29 01:21:39 24 bit/s
longclaw (US) Yes Yes Y Yes Running, Valid, Fast 876.5 Kbit/s | 816.0 Kbit/s 876.5 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 71.2% | 98% 10.2d | 8d 0.7d | 54.5d 0.3d | 10.7d 71.2% | 98.0% 10.2d | 1.0d 2026-01-29 01:21:39 816 bit/s
maatuska (SE) Yes Yes Y Yes Running, Valid 876.5 Kbit/s | 816.0 Kbit/s 876.5 Kbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 71.3% | 98% 10.7d | 8d 0.7d | 54.6d 0.3d | 10.6d 71.3% | 98.0% 10.7d | 1.0d 2026-01-29 01:21:39 24 bit/s
moria1 (US) Yes Yes Y Yes Running, Valid, Stable 876.5 Kbit/s | 8.4 Mbit/s 876.5 Kbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 72.6% | 98% 10.2d | 8d 18615.2d | 406.0d 0.3d | 10.8d 72.6% | 98.0% 10.2d | 9.9d 2026-01-29 01:21:39 72 bit/s
tor26 (AT) Yes Yes Y Yes Running, Valid 876.5 Kbit/s | 816.0 Kbit/s 876.5 Kbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 71.1% | 98% 10.2d | 8d 0.7d | 55.6d 0.3d | 12.0d 71.1% | 98.0% 10.2d | 1.0d 2026-01-29 01:21:39 24 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.