View Relay "dutchtrouble"

Family: 23 relays | D.O Bronk <tor-relay@bronk-ict.nl> | AS215659 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Fast, Running, V2Dir, Valid (5)
BW Verified
5/6 BW Auths Measured 39 Kbit/s Median
Stability
Not Overloaded | UP 23h 47m 38s ago | UP 90% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2w 3d 21h ago
BW Weight
0.00% of Network | 38 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 93.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).
  • 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 93.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
tor-exit-usa.bronk-ict.nl
66.78.40.91:9443
[2a0f:85c1:356:5d3a::1984]:9443
Exit Address
66.78.40.91
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS215659
AS Name
Aokigahara SRL (BGP.tools)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/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) 39.0 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 3.0d (1/9 DA above threshold)
Min/Max: 0.0d / 14190.3d (9/9 DA, Voting / Total Eligible)		 ≥22.2d - 53.9d (varies)
[Stricter] moria1: ≥405.2d
Uptime Below 1.0d (R) ≥9.9d - 10.6d (varies)
HSDir Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 9/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 93.3% (0/9 DA above threshold)
Min/Max: 74.5% / 93.6% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 10.4d (9/9 DA above threshold)
Min/Max: 8.3d / 10.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets 9/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 93.3% (0/9 DA above threshold)
Min/Max: 74.5% / 93.6% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 10.4d (9/9 DA above threshold)
Min/Max: 8.3d / 10.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 39.0 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 13:15:03).

Last fetch was at Thu, 29 Jan 2026 13:15:47 GMT.

Nickname
dutchtrouble
Fingerprint
0EE0A4DF9523099BE744506D45AAE3046481BAD0
AROI (?)
none
Contact
D.O Bronk <tor-relay@bronk-ict.nl>
IPv4 Exit Policy Summary 
reject: 
  22-25
  119
  135-139
  445
  563
  1214
  3306
  3389
  4661-4666
  5900
  6346-6429
  6699
  6881-6999
  33060
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 66.78.40.91:*
reject *:22-25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:3306
reject *:3389
reject *:4661-4666
reject *:5900
reject *:6346-6429
reject *:6699
reject *:6881-6999
reject *:33060
accept *:*
Effective Family Members: 23 (View) 
0EE0A4DF9523099BE744506D45AAE3046481BAD0
13D372C40E2186DE32BFCE90662FB5CB37E740B9
47B85F0CF3CDAEB06AB0038F9783C159E0E3E318
4AF90104F3FE4556BB01B92F6E19F46B3B390906
50C94FC6730FEACAC04CF08B94A971FF7AEBD266
5197F04BADD2C9B2E6E80AA4F07DC2341B5D9D16
5CAC411922316646A8F9CEB26B38E136258DBCD7
6055A518F03989F867DF7C435B61D5776D768B10
6584688F1A0132BF1AB79E91EDF6F9602C7336C1
6AA3EF04938AB10CA388C965224CFDC58918F7B0
6D7635ACD41651216B2E739D152EE6B606297383
6E0FAD76D6996BA6ECB0BC6F617A46B527D7156F
75F2C6C7DA73AD09BF36005FEFAF0384E63349B7
7EE0B657BBCFCCA447F271480A7C64FDEB9627A9
99A9B6E348C140C9D0B7F8D6B0550DF40F1C4768
A99414EC158C971F56BE76DA8903C3C7264AD00A
B7B68BF561714F795D32F7B6B8AAD37DDBE7EDAA
BAFD8B5B746D866B17CAB6E67D36D60C120C10C3
C2E34F3DB534B6D15E4CCF372B01B9A70375237E
CB058D8235C4513271A403C45A344D10460F3F62
CB6EBAEE415FAA3715DD0114586859184B08E775
CC3670CCE6A2A363F25E5CA72F9F3B6D79B48B46
DDD0D2C89663C0A0AB1D042B965F7403CC8E147B
Alleged Family Members: 0 
none
Indirect Family Member: 1 
647B96D975DE80D42640EFA278EE320785E589B8
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
38.97 Mbit/s | 38.97 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
tor-exit-usa.bronk-ict.nl | 66.78.40.91:9443, [2a0f:85c1:356:5d3a::1984]:9443
Exit Address
none
Dir Address
none
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS215659 | Aokigahara SRL (BGP.tools)
Flags: 5
Exit Exit Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (90.9%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
90.9%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 23h 47m 38s ago
Seen (First | Last)
2w 3d 21h ago (2026-01-11 16:00:00) | 1h 17m 14s ago (2026-01-29 12:00:00)
Last Restarted
23h 49m 4s ago (2026-01-28 13:28:10)
Last Changed Address or Port
2026-01-11 16: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 13:15:03).

  • 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: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9 | IPv6: 6/0
  • Consensus Weight (Dir. Auth.): Median: 39.0 Kbit/s | Min: 12.0 Kbit/s | Max: 53.6 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 93.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).
    • 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 93.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.) 39.0 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 93.3% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 10.4 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 39.0 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 1.0d ≥9.9d - 10.6d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 3 days ≥22.2d - 53.9d (typical)
[Stricter] moria1: ≥405.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 39.0 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) 93.3% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 10.4 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.8d 		BELOW - 0/9
IPv6 Reachable (Dir. Auth.) 6/6 tested ≥4/6 (majority) REACHABLE

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 v6 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 Yes Running, Valid, V2Dir, Fast, Exit 39.0 Mbit/s | 816.0 Kbit/s 39.0 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 93.3% | 98% 10.0d | 8d 2.9d | 49.8d 1.0d | 11.0d 93.3% | 98.0% 10.0d | 1.0d 2026-01-29 07:28:14 41.6 Kbit/s
dannenberg (DE) Yes Yes N Yes — Valid, V2Dir, Fast, Exit 39.0 Mbit/s | 816.0 Kbit/s 39.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 74.5% | 98% 8.4d | 8d 0.0d | 22.2d 1.0d | 10.7d 74.5% | 98.0% 8.4d | 1.0d 2026-01-29 07:28:14 39.0 Kbit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast, Exit 39.0 Mbit/s | 816.0 Kbit/s 39.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.5% | 98% 10.6d | 8d 4.9d | 34.8d 1.0d | 10.6d 93.5% | 98.0% 10.6d | 1.0d 2026-01-29 07:28:14 39.0 Kbit/s
faravahar (US) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Exit 39.0 Mbit/s | 816.0 Kbit/s 39.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.3% | 98% 10.6d | 8d 3.0d | 47.5d 1.0d | 9.9d 93.3% | 98.0% 10.6d | 1.0d 2026-01-29 07:28:14 39.0 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 39.0 Mbit/s | 816.0 Kbit/s 39.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 93.1% | 98% 10.4d | 8d 1.9d | 53.9d 1.0d | 10.6d 93.1% | 98.0% 10.4d | 1.0d 2026-01-29 07:28:14 20.0 Kbit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast, Exit 39.0 Mbit/s | 816.0 Kbit/s 39.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.3% | 98% 10.6d | 8d 3.7d | 55.1d 1.0d | 10.0d 93.3% | 98.0% 10.6d | 1.0d 2026-01-29 07:28:14 39.0 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 39.0 Mbit/s | 816.0 Kbit/s 39.0 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 93.1% | 98% 10.4d | 8d 1.6d | 55.3d 1.0d | 10.0d 93.1% | 98.0% 10.4d | 1.0d 2026-01-29 07:28:14 12.0 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Exit 39.0 Mbit/s | 8.4 Mbit/s 39.0 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 91.9% | 98% 8.3d | 8d 14190.3d | 405.2d 1.0d | 10.1d 91.9% | 98.0% 8.3d | 9.8d 2026-01-29 07:28:14 53.6 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 39.0 Mbit/s | 816.0 Kbit/s 39.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 93.6% | 98% 10.6d | 8d 3.0d | 55.8d 1.0d | 11.3d 93.6% | 98.0% 10.6d | 1.0d 2026-01-29 07:28:14 24.8 Kbit/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.