View Relay "ShinobiKenshin"

Operator: relays.brokenbotnet.com (11 relays) ✓ Validated | Family: 11 relays | email:r3bo0tbx1[]brokenbotnet.com... | AS63949 | Japan | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Fast, Running, V2Dir, Valid (5)
BW Verified
5/6 BW Auths Measured 10 Kbit/s Median
Stability
Not Overloaded | UP 1w 3d 9h ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
2mo 3d 22h ago
BW Weight
0.00% of Network | 20 Mbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • 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
tor-exit.brokenbotnet.com
172.234.92.148:1984
[2400:8905:e001:10f::1337:c0de]:1984
Exit Address
172.234.92.148
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Japan Japan
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS63949
AS Name
Akamai Technologies, Inc. (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.17% consensus weight, 73 operators)

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: 3/9 | HSDir: 2/9 | Guard: 2/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Meets (≥100 KB/s) 20.7 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 4.3d (1/9 DA above threshold)
Min/Max: 2.7d / 14415.1d (9/9 DA, Voting / Total Eligible)		 ≥21.8d - 51.6d (varies)
[Stricter] moria1: ≥459.7d
Uptime Meets 10.4d (R) ≥6.4d - 7.5d (varies)
HSDir Prereq: Stable Below 3/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 9/9 authorities assigned Fast flag ≥5/9 authorities
WFU Meets Median: 99.4% (9/9 DA above threshold)
Min/Max: 98.2% / 99.8% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 12.7d (9/9 DA above threshold)
Min/Max: 9.8d / 14.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets 9/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 3/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Meets Median: 99.4% (9/9 DA above threshold)
Min/Max: 98.2% / 99.8% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 12.7d (9/9 DA above threshold)
Min/Max: 9.8d / 14.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 20.7 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-304.0 Mbit/s

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

Last fetch was at Wed, 11 Feb 2026 19:15:44 GMT.

Nickname
ShinobiKenshin
Fingerprint
64CE119D87F0A28F31D74280FB9675D880CA4BFA
AROI (?)
relays.brokenbotnet.com
Contact
email:r3bo0tbx1[]brokenbotnet.com url:https://relays.brokenbotnet.com proof:uri-rsa pgp:33727F5377D296C320AF704AB3BD6196E1CFBFB4 abuse:abuse[]brokenbotnet.com mastodon:https://infosec.exchange/@r3bo0tbx1 ciissversion:2
IPv4 Exit Policy Summary 
accept: 
  20-21
  43
  53
  80-81
  443
  5222-5223
  6667-7000
  8008
  8082
  8332-8333
  8888
  9418
  18080-18081
  50002
  64738
IPv6 Exit Policy Summary 
accept: 
  20-21
  43
  53
  80-81
  443
  5222-5223
  6667-7000
  8008
  8082
  8332-8333
  8888
  9418
  18080-18081
  50002
  64738
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 172.234.92.148:*
reject 172.233.64.37:*
reject 172.233.64.38:*
reject 172.233.64.39:*
reject 172.233.64.40:*
reject 172.233.64.41:*
reject 172.233.64.42:*
reject 172.233.64.43:*
reject 172.233.64.44:*
reject 172.233.64.45:*
reject 172.233.64.46:*
accept *:20-21
accept *:43
accept *:53
accept *:80-81
accept *:443
accept *:5222-5223
accept *:6667-7000
accept *:8008
accept *:8082
accept *:8332-8333
accept *:8888
accept *:9418
accept *:18080-18081
accept *:50002
accept *:64738
reject *:*
Effective Family Members: 11 (View) 
0EEE0B1EED5E35E1E3F2575CD0AFF160925FA63F
38FF19F5014E110F196D4AEB81189B375EDA4530
576E77EE584906041FF504592E5C51EE471707A2
586AD06CB8BCE3625D6CC88772CDE4FE56477EE2
5F926760730D0229C2F2D16D0DE0E8A3C2682ED1
64CE119D87F0A28F31D74280FB9675D880CA4BFA
7F28C3E41DA9FD4A2B8143CB6038304634EDC396
A24D263E817AA29F4E1F210AC519EF590DB443CD
A6A2A807338167A5E58F4DD2D4CD0817AF3DD562
CA7E23C44E6D6F1D8A52A4E1F6CAA11F18108A02
D184F8140F3357F84E64BCF51094EA13B18FDD25
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
20.68 Mbit/s | 16.78 Mbit/s| 16.78 Mbit/s| 46.14 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | 0.00%
OR Address
tor-exit.brokenbotnet.com | 172.234.92.148:1984, [2400:8905:e001:10f::1337:c0de]:1984
Exit Address
none
Dir Address
none
Country
Japan Japan
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS63949 | Akamai Technologies, Inc. (BGP.tools)
Flags: 5
Exit Exit Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (99.3%/99.4%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
99.3%/99.4%/0.0%/0.0%
Uptime / Downtime
UP 1w 3d 9h ago
Seen (First | Last)
2mo 3d 22h ago (2025-12-09 21:00:00) | 1h 17m 31s ago (2026-02-11 18:00:00)
Last Restarted
1w 3d 9h ago (2026-02-01 10:13:05)
Last Changed Address or Port
2025-12-26 15: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 18: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: 9/9 | Stable: 3/9 | HSDir: 2/9 | Guard: 2/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 10.4 Kbit/s | Min: 2080 bit/s | Max: 16.8 Kbit/s [Warning] High deviation
  • Identified Issues:
    • 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.4 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 99.4% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 12.7 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 20.7 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-304.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 10.4d ≥6.4d - 7.5d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 4 days ≥21.8d - 51.6d (typical)
[Stricter] moria1: ≥459.7d 		BELOW - 1/9
Fast Speed (Relay Reported) 20.7 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) 99.4% ≥98.0% (from all auths) BELOW - 2/9
HSDir TK (Dir. Auth., tk) 12.7 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 2/9
IPv6 Reachable (Dir. Auth.) 7/7 tested ≥4/7 (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 20.7 Mbit/s | 816.0 Kbit/s 20.7 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 99.4% | 98% 12.7d | 8d 4.5d | 51.6d 10.4d | 7.5d 99.4% | 98.0% 12.7d | 1.0d 2026-02-11 09:13:25 10.4 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Exit 20.7 Mbit/s | 704.0 Kbit/s 20.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.2% | 98% 12.6d | 5d 2.7d | 21.8d 10.4d | 6.4d 98.2% | 98.0% 12.6d | 1.0d 2026-02-11 09:13:25 16.8 Kbit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 20.7 Mbit/s | 696.0 Kbit/s 20.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 14.4d | 6d 7.2d | 27.6d 10.4d | 6.4d 99.6% | 98.0% 14.4d | 1.0d 2026-02-11 09:13:25 16.8 Kbit/s
faravahar (US) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Exit 20.7 Mbit/s | 816.0 Kbit/s 20.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 13.7d | 8d 3.4d | 47.8d 10.4d | 7.5d 99.0% | 98.0% 13.7d | 1.0d 2026-02-11 09:13:25 16.8 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 20.7 Mbit/s | 816.0 Kbit/s 20.7 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 12.4d | 8d 3.1d | 59.9d 10.4d | 7.5d 99.2% | 98.0% 12.4d | 1.0d 2026-02-11 09:13:25 4640 bit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 20.7 Mbit/s | 816.0 Kbit/s 20.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.8% | 98% 14.7d | 8d 7.8d | 61.0d 10.4d | 7.3d 99.8% | 98.0% 14.7d | 1.0d 2026-02-11 09:13:25 16.8 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 20.7 Mbit/s | 816.0 Kbit/s 20.7 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.4% | 98% 14.0d | 8d 4.3d | 41.3d 10.4d | 7.5d 99.4% | 98.0% 14.0d | 1.0d 2026-02-11 09:13:25 2080 bit/s
moria1 (US) Yes Yes Y Yes Yes Valid, V2Dir, Fast, Stable, Exit 20.7 Mbit/s | 8.4 Mbit/s 20.7 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 99.5% | 98% 9.8d | 8d 14415.1d | 459.7d 10.4d | 7.5d 99.5% | 98.0% 9.8d | 9.9d 2026-02-11 09:13:25 8.8 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Exit 20.7 Mbit/s | 816.0 Kbit/s 20.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 99.4% | 98% 12.6d | 8d 3.7d | 57.4d 10.4d | 7.5d 99.4% | 98.0% 12.6d | 1.0d 2026-02-11 09:13:25 5040 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.