View Relay "dureichstsogut"

Family: 1 relay | b9a3174g @ proton.me | AS44486 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Running, Stable, V2Dir, Valid (5)
BW Verified
5/6 BW Auths Measured 96 bit/s Median
Stability
Not Overloaded | UP 2w 2d 21h ago | UP 54% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2y 5mo 1w ago
BW Weight
0.00% of Network | 1 Mbit/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 80.0% 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 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.
  • HSDir: WFU below threshold : WFU 80.0% 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
176.118.193.33:9001
Exit Address
176.118.193.33
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS44486
AS Name
Oliver Horscht is trading as "SYNLINQ" (BGP.tools)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Stable, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 9/9 | HSDir: 4/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) 1.1 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 20.0d (1/9 DA above threshold)
Min/Max: 8.4d / 206.9d (9/9 DA, Voting / Total Eligible)		 ≥22.0d - 54.1d (varies)
[Stricter] moria1: ≥405.3d
Uptime Meets 16.9d (R) ≥9.3d - 10.0d (varies)
HSDir Prereq: Stable Meets 9/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 4/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 80.4% (0/9 DA above threshold)
Min/Max: 75.3% / 83.6% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 25.1d (9/9 DA above threshold)
Min/Max: 9.8d / 29.8d (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 Meets 9/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 80.4% (0/9 DA above threshold)
Min/Max: 75.3% / 83.6% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 25.1d (9/9 DA above threshold)
Min/Max: 9.8d / 29.8d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 1.1 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-01-29 16:15:07).

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

Nickname
dureichstsogut
Fingerprint
C5C7BC6C2CE769A1055AE3FC6A06878260CF314B
AROI (?)
none
Contact
b9a3174g @ proton.me
IPv4 Exit Policy Summary 
accept: 
  20-23
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8232-8233
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
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 176.118.193.33:*
accept *:20-21
accept *:22
accept *:23
accept *:43
accept *:53
accept *:79
accept *:80-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:464
accept *:465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:587
accept *:636
accept *:706
accept *:749
accept *:853
accept *:873
accept *:902-904
accept *:981
accept *:989-990
accept *:991
accept *:992
accept *:993
accept *:994
accept *:995
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:1755
accept *:1863
accept *:2082
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3389
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8232-8233
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999
accept *:10000
accept *:11371
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*
Effective Family Member: 1 
C5C7BC6C2CE769A1055AE3FC6A06878260CF314B
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
1.10 Mbit/s | 1.10 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | 0.00%
OR Address
176.118.193.33:9001
Exit Address
none
Dir Address
none
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS44486 | Oliver Horscht is trading as "SYNLINQ" (BGP.tools)
Flags: 5
Exit Exit Running Running Stable Stable V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (54.4%/84.4%/92.2%/94.4%)
Uptime (1M/6M/1Y/5Y)
54.4%/84.4%/92.2%/94.4%
Uptime / Downtime
UP 2w 2d 21h ago
Seen (First | Last)
2y 5mo 1w ago (2023-08-20 00:00:00) | 1h 17m 13s ago (2026-01-29 15:00:00)
Last Restarted
2w 2d 21h ago (2026-01-12 18:23:18)
Last Changed Address or Port
2026-01-12 19: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: 4/9 | Stable: 9/9 | HSDir: 4/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 96 bit/s | Min: 24 bit/s | Max: 1096 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 80.0% 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 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.
    • HSDir: WFU below threshold: WFU 80.0% 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.) 96 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 80.4% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 25.1 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 1.1 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 16.9d ≥9.3d - 10.0d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 20 days ≥22.0d - 54.1d (typical)
[Stricter] moria1: ≥405.3d 		BELOW - 0/9
Fast Speed (Relay Reported) 1.1 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) 80.4% ≥98.0% (from all auths) BELOW - 4/9
HSDir TK (Dir. Auth., tk) 25.1 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 4/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, Stable, Exit 1.1 Mbit/s | 816.0 Kbit/s 1.1 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 80.0% | 98% 25.1d | 8d 19.9d | 49.8d 16.9d | 10.2d 80.0% | 98.0% 25.1d | 1.0d 2026-01-29 14:30:08 96 bit/s
dannenberg (DE) Yes Yes N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.1 Mbit/s | 816.0 Kbit/s 1.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 75.3% | 98% 20.0d | 8d 8.4d | 22.0d 16.9d | 10.0d 75.3% | 98.0% 20.0d | 1.0d 2026-01-29 14:30:08 1096 bit/s
dizum (NL) Yes Yes N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.1 Mbit/s | 816.0 Kbit/s 1.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 78.0% | 98% 22.8d | 8d 17.5d | 34.7d 16.9d | 10.0d 78.0% | 98.0% 22.8d | 1.0d 2026-01-29 14:30:08 1096 bit/s
faravahar (US) Yes Yes N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.1 Mbit/s | 816.0 Kbit/s 1.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 80.4% | 98% 25.2d | 8d 20.0d | 47.2d 16.9d | 9.3d 80.4% | 98.0% 25.2d | 1.0d 2026-01-29 14:30:08 1096 bit/s
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir, Stable, Exit 1.1 Mbit/s | 816.0 Kbit/s 1.1 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 83.0% | 98% 29.6d | 8d 24.3d | 54.1d 16.9d | 10.0d 83.0% | 98.0% 29.6d | 1.0d 2026-01-29 14:30:08 32 bit/s
longclaw (US) Yes Yes Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.1 Mbit/s | 816.0 Kbit/s 1.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 82.3% | 98% 29.8d | 8d 24.3d | 54.7d 16.9d | 9.6d 82.3% | 98.0% 29.8d | 1.0d 2026-01-29 14:30:08 1096 bit/s
maatuska (SE) Yes Yes Y Yes Running, Valid, V2Dir, Stable, Exit 1.1 Mbit/s | 816.0 Kbit/s 1.1 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 77.5% | 98% 22.3d | 8d 17.1d | 54.9d 16.9d | 9.5d 77.5% | 98.0% 22.3d | 1.0d 2026-01-29 14:30:08 24 bit/s
moria1 (US) Yes Yes Y Yes Running, Valid, V2Dir, Stable, Exit 1.1 Mbit/s | 8.4 Mbit/s 1.1 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 83.6% | 98% 9.8d | 8d 206.9d | 405.3d 16.9d | 9.9d 83.6% | 98.0% 9.8d | 9.9d 2026-01-29 14:30:08 88 bit/s
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir, Stable, Exit 1.1 Mbit/s | 816.0 Kbit/s 1.1 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 81.0% | 98% 27.9d | 8d 22.4d | 55.9d 16.9d | 10.8d 81.0% | 98.0% 27.9d | 1.0d 2026-01-29 14:30:08 32 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.