View Relay "LHiroshima"

Fingerprint: 4362AB00D0C008E724AF14A2294D4F08A220A8C0 | Family: 1 relay | a6-dy<removeme>@protonmail.com | AS10013 | Japan | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
1/6 BW Auths Measured 1832 bit/s Median
Stability
Not Overloaded | UP 1d 13h 5m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2d 3h 16m ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.8.22 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: bandwidth below threshold : Observed bandwidth 0.2 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: Time Known below threshold : Time Known 2.1 days is below 8 days requirement (5.9 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.
  • 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.
  • Low bandwidth authority measurements : Only 1/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

Connectivity and Location

Addresses
OR Address
94.104.44.61.ap.yournet.ne.jp
61.44.104.94:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Japan Japan
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS10013
AS Name
FreeBit Co,Ltd. (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/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 (9/9 DA) 9/9 authorities reached relay ≥5/9 DA ORPort reachable
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 1.8 Mbit/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: 2.1d (0/9 DA above threshold)
Min/Max: 2.0d / 2.1d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥373.6d
Uptime Below (0/9 DA) 1.5d (R) ≥13.6d - 14.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 ≥11.3d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥373.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 2.1d (0/9 DA above threshold)
Min/Max: 1.8d / 2.1d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (4/9 DA) 4/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 ≥11.3d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥373.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.9 more days) Median: 2.1d (0/9 DA above threshold)
Min/Max: 1.8d / 2.1d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.8 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-13 22:15:07).

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-03-13 22:15:07

Measured By
1/6 Bandwidth Authorities
Not measured by: bastet, gabelmoo, longclaw, moria1, tor26
Median Measurement
1832 bit/s
Min / Max
192 bit/s / 1832 bit/s
Deviation
1640 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0000% (2th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 13h 5m 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
2d 3h 16m ago (2026-03-11 19:00:00)
Last Seen
4h 16m 38s ago (2026-03-13 18:00:00)
Last Restarted
1d 13h 5m ago (2026-03-12 09:11:23)
Last Changed Address
2026-03-11 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-13 15:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
a6-dy<removeme>@protonmail.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
4362AB00D0C008E724AF14A2294D4F08A220A8C0 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.8.22 on Linux
Version
0.4.8.22 — 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 Fri, 13 Mar 2026 22:16:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-13 22:15:07).

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 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 Running, Valid, V2Dir 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.1d | 8d 2.1d | 56.1d 1.5d | 14.5d 100.0% | 98.0% 2.1d | 1.0d 2026-03-13 11:50:06 1832 bit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.1d | 8d 2.1d | 11.3d 1.5d | 14.8d 100.0% | 98.0% 2.1d | 1.0d 2026-03-13 11:50:06 1832 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.1d | 8d 2.1d | 44.2d 1.5d | 13.6d 100.0% | 98.0% 2.1d | 1.0d 2026-03-13 11:50:06 1832 bit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.1d | 8d 2.1d | 51.9d 1.5d | 14.9d 100.0% | 98.0% 2.1d | 1.0d 2026-03-13 11:50:06 1832 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.0d | 58.0d 1.5d | 14.9d 100.0% | 98.0% 2.0d | 1.0d 2026-03-13 11:50:06 1832 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.1d | 8d 2.1d | 59.1d 1.5d | 14.6d 100.0% | 98.0% 2.1d | 1.0d 2026-03-13 11:50:06 1832 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.1d | 8d 2.1d | 39.1d 1.5d | 14.7d 100.0% | 98.0% 2.1d | 1.0d 2026-03-13 11:50:06 192 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir 1.8 Mbit/s | 8.4 Mbit/s 1.8 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.8d | 8d 2.0d | 373.6d 1.5d | 16.7d 100.0% | 98.0% 1.8d | 9.9d 2026-03-13 11:50:06 1832 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir 1.8 Mbit/s | 816.0 Kbit/s 1.8 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.1d | 8d 2.1d | 54.7d 1.5d | 15.3d 100.0% | 98.0% 2.1d | 1.0d 2026-03-13 11:50:06 1832 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.