View Relay "ShinobiKaede"

Fingerprint: B05A4E4AEB2E5AD92CF882D57162F9EDAAA51815 | Operator: relays.brokenbotnet.com v3 (12 relays) ✓ Validated | Family: 1 relay | email:r3bo0tbx1[]brokenbotnet.com... | AS26832 | Canada | Linux

Health Status

Consensus
In Consensus (8/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
3/7 BW Auths Measured
Stability
Not Overloaded | UP 11h 49m 4s ago
Reachability
IPv4: 8/9 | v6: 6/7 (Directory Auths)
First Seen
10h 45m 50s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.11 Recommended
Issues Detected:
  • 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.
  • 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: Time Known below threshold : Time Known 0.5 days is below 8 days requirement (7.5 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.
  • 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: requires Fast flag : HSDir 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: requires Stable flag : HSDir 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). Avoid restarts.
  • HSDir: Time Known below threshold : Time Known 10.9 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay
  • Bandwidth authority measurements below majority: 3/7 bandwidth authorities measured this relay (majority is 4).

Connectivity and Location

Addresses
OR Address
ca-relay.brokenbotnet.com
38.49.219.113:443
[2001:470:1d:4a1::1337:c0de]:443
Reachability (Directory Authorities)
IPv4
8/9
IPv6
6/7 (2 don't test)
Location
Country
Canada Canada
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS26832
AS Name
Rica Web Services (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.09% consensus weight, 13 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/9 DA) 8/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Meets (6/7 DA) 6/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Meets (8/9 DA) 8/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (8/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Below (0/9 DA) 0 bit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 0.5d (0/9 DA above threshold)
Min/Max: 0.0d / 0.5d (8/9 DA, Voting / Total Eligible)		 ≥20.6d - 57.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥949.4d
Uptime Below (0/9 DA) 0.5d (R) ≥4.3d - 4.6d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥20.6d - 57.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥949.4d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (6/9 DA) Majority: 100.0% (6/9 DA)
Min/Med/Max: 83.8% / 100.0% / 100.0% (8/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.5d (0/9 DA above threshold)
Min/Max: 0.3d / 0.5d (8/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥20.6d - 57.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥949.4d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (6/9 DA) Majority: 100.0% (6/9 DA)
Min/Med/Max: 83.8% / 100.0% / 100.0% (8/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.5 more days) Median: 0.5d (0/9 DA above threshold)
Min/Max: 0.3d / 0.5d (8/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-01 20:45:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-01 20:45:08

Measured By
3/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, gabelmoo, moria1
Median Measurement
0.0 bit/s
Min / Max
0 bit/s / 8 bit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 11h 49m 4s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
10h 45m 50s ago (2026-07-01 10:00:00)
Last Seen
1h 45m 50s ago (2026-07-01 19:00:00)
Last Restarted
11h 49m 4s ago (2026-07-01 08:56:46)
Last Changed Address
2026-07-01 10:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-01 13:00 UTC

AROI Domain (?)
relays.brokenbotnet.com
Operator Validation
Validated (12/12 relays)
This Relay
Validated (uri-familyid-ed25519)
Contact
email:r3bo0tbx1[]brokenbotnet.com url:https://relays.brokenbotnet.com proof:uri-familyid-ed25519 pgp:33727F5377D296C320AF704AB3BD6196E1CFBFB4 abuse:abuse[]brokenbotnet.com mastodon:https://infosec.exchange/@r3bo0tbx1 ciissversion:3
Family Configuration
Family Support
Happy Families (12) — Has family-cert in server descriptor (guide)

Software and Version

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 01 Jul 2026 20:45:49 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-01 20:45:08).

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 Exit MiddleOnly 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 No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 55.9d 0.5d | 4.6d 100.0% | 98.0% 0.5d | 1.0d 2026-07-01 08:57:09 —
dannenberg (DE) Yes Yes No — Y Yes — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 83.8% | 98% 0.4d | 8d 0.0d | 20.6d 0.5d | 4.6d 83.8% | 98.0% 0.4d | 1.0d 2026-07-01 08:57:09 —
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 0.5d | 8d 0.1d | 35.8d 0.5d | 4.6d 97.8% | 98.0% 0.5d | 1.0d 2026-07-01 08:57:09 —
faravahar (US) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.3d | 8d 0.3d | 57.6d 0.5d | 4.5d 100.0% | 98.0% 0.3d | 1.0d 2026-07-01 08:57:09 —
gabelmoo (DE) No — — — Y No — — — — — — — — — — — —
longclaw (US) Yes Yes No — Y Yes — Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 59.4d 0.5d | 4.6d 100.0% | 98.0% 0.5d | 1.0d 2026-07-01 08:57:09 8 bit/s
maatuska (SE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 34.2d 0.5d | 4.6d 100.0% | 98.0% 0.5d | 1.0d 2026-07-01 08:57:09 8 bit/s
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 8.4 Mbit/s 0 bit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 949.4d 0.5d | 4.6d 100.0% | 98.0% 0.5d | 9.9d 2026-07-01 08:57:09 —
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 59.8d 0.5d | 4.7d 100.0% | 98.0% 0.5d | 1.0d 2026-07-01 08:57:09 8 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). Self-reported uptime from 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.