View Relay "eapRelay"

Family: 1 relay | ActivityPub: @hpf@misskey.io, WWW:... | AS58791 | Japan | FreeBSD

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, Stable, V2Dir, Valid (5)
BW Verified
5/6 BW Auths Measured 4720 bit/s Median
Stability
Not Overloaded | UP 3h 59m 19s ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
1y 7mo 3w ago
BW Weight
0.00% of Network | 10 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 1.3 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.
  • 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
v160-251-184-10.c5n5.static.cnode.jp
160.251.184.10:443
[2400:8500:2002:3169:160:251:184:10]:443
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
AS58791
AS Name
Unknown

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Stable
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 8/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) 10.2 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (7/9) Median: 367.0d (7/9 DA above threshold)
Min/Max: 4.7d / 368.1d (9/9 DA, Voting / Total Eligible)		 ≥22.0d - 54.1d (varies)
[Stricter] moria1: ≥405.3d
Uptime Below 0.2d (R) ≥9.3d - 10.0d (varies)
HSDir Prereq: Stable Meets 8/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 5/9 authorities assigned Fast flag ≥5/9 authorities
WFU Meets Majority: 100.0% (7/9 DA)
Min/Med/Max: 99.5% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 359.0d (9/9 DA above threshold)
Min/Max: 9.6d / 368.0d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets 5/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Meets 8/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Meets Majority: 100.0% (7/9 DA)
Min/Med/Max: 99.5% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 359.0d (9/9 DA above threshold)
Min/Max: 9.6d / 368.0d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 10.2 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:45:35 GMT.

Nickname
eapRelay
Fingerprint
3A4E426160E9BA8636AE53A0AECF0F837C78D81E
AROI (?)
none
Contact
ActivityPub: @hpf@misskey.io, WWW: https://eap.vg/profile/, Onion: http://p6o5e4o47q6k26grnp7bi2mphmkkv5mg7yas57dkgxycqrjqaldjqnqd.onion/profile/
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
3A4E426160E9BA8636AE53A0AECF0F837C78D81E
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
10.19 Mbit/s | 10.19 Mbit/s| 67.11 Mbit/s| 67.11 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
v160-251-184-10.c5n5.static.cnode.jp | 160.251.184.10:443, [2400:8500:2002:3169:160:251:184:10]:443
Exit Address
none
Dir Address
none
Country
Japan Japan
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS58791 | unknown
Flags: 5
Fast Fast Running Running Stable Stable V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
98.2%/99.2%/99.6%/99.4%
Uptime (1M/6M/1Y/5Y)
100.0%/100.0%/100.0%/99.7%
Uptime / Downtime
UP 3h 59m 19s ago
Seen (First | Last)
1y 7mo 3w ago (2024-06-12 06:00:00) | 1h 47m 7s ago (2026-01-29 15:00:00)
Last Restarted
4h 49s ago (2026-01-29 12:46:18)
Last Changed Address or Port
2024-06-12 06:00:00
Hibernating
No
Platform (Short | Long)
FreeBSD | Tor 0.4.8.21 on FreeBSD
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: 5/9 | Stable: 8/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 4720 bit/s | Min: 488 bit/s | Max: 10.2 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 1.3 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.
    • 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.) 4720 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 100.0% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 359.0 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 10.2 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.2d ≥9.3d - 10.0d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 367 days ≥22.0d - 54.1d (typical)
[Stricter] moria1: ≥405.3d 		PARTIAL - 7/9
Fast Speed (Relay Reported) 10.2 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) 100.0% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 359.0 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/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, Stable 10.2 Mbit/s | 816.0 Kbit/s 10.2 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 367.3d | 8d 367.3d | 49.8d 0.2d | 10.2d 100.0% | 98.0% 367.3d | 1.0d 2026-01-29 12:46:20 4720 bit/s
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 10.2 Mbit/s | 816.0 Kbit/s 10.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.5% | 98% 14.9d | 8d 4.7d | 22.0d 0.2d | 10.0d 99.5% | 98.0% 14.9d | 1.0d 2026-01-29 12:46:20 10.2 Kbit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast, Stable 10.2 Mbit/s | 816.0 Kbit/s 10.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 47.6d | 8d 47.2d | 34.7d 0.2d | 10.0d 100.0% | 98.0% 47.6d | 1.0d 2026-01-29 12:46:20 10.2 Kbit/s
faravahar (US) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Stable 10.2 Mbit/s | 816.0 Kbit/s 10.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 359.0d | 8d 359.0d | 47.2d 0.2d | 9.3d 100.0% | 98.0% 359.0d | 1.0d 2026-01-29 12:46:20 10.2 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Stable 10.2 Mbit/s | 816.0 Kbit/s 10.2 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 368.0d | 8d 368.0d | 54.1d 0.2d | 10.0d 100.0% | 98.0% 368.0d | 1.0d 2026-01-29 12:46:20 488 bit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast, Stable 10.2 Mbit/s | 816.0 Kbit/s 10.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 367.0d | 8d 367.0d | 54.7d 0.2d | 9.6d 100.0% | 98.0% 367.0d | 1.0d 2026-01-29 12:46:20 10.2 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Stable 10.2 Mbit/s | 816.0 Kbit/s 10.2 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 93.7d | 8d 93.7d | 54.9d 0.2d | 9.5d 100.0% | 98.0% 93.7d | 1.0d 2026-01-29 12:46:20 760 bit/s
moria1 (US) Yes Yes Y Yes Yes Running, Valid, V2Dir, Stable 10.2 Mbit/s | 8.4 Mbit/s 10.2 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.6d | 8d 368.1d | 405.3d 0.2d | 9.9d 100.0% | 98.0% 9.6d | 9.9d 2026-01-29 12:46:20 2880 bit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Stable 10.2 Mbit/s | 816.0 Kbit/s 10.2 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 368.0d | 8d 368.0d | 55.9d 0.2d | 10.8d 100.0% | 98.0% 368.0d | 1.0d 2026-01-29 12:46:20 776 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.