View Relay "mynode14"

Fingerprint: 81F716337733BD6B2E1B044D129392E6D71434EC | Family: 5 relays | the.hunters.ledger@gmail.com | AS20473 | United States of America | Linux

Consensus
Not In Consensus (4/9 Directory Auths, need 5)
DNS Health
Healthy (17.6s, 80th percentile) (via exitdnshealth.1aeo.com)
BW Verified
2/7 BW Auths Measured 19 Kbit/s Median
Stability
Not Overloaded | DOWN 3h 2m 55s ago
Reachability
IPv4: 4/9 (Directory Auths)
BW Weight
0.00% of Network | 19 Mbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • Not in consensus : Only 4/9 authorities voted for this relay (need 5)
    Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
  • IPv4 reachability issues : Only 4/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, faravahar, gabelmoo, maatuska, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
  • 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 2.4 days is below 8 days requirement (5.6 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 2/7 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.
  • Tor version not recommended : Running Tor version 0.4.9.11 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Addresses
OR Address
45.76.234.136.vultrusercontent.com
45.76.234.136:9001
Exit Address
45.76.234.136
Reachability (Directory Authorities)
IPv4
4/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS20473
AS Name
The Constant Company, LLC (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.17% consensus weight, 27 operators)

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (0): Running: 4/9 | Valid: 4/9 | V2Dir: 4/9 | Fast: 3/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 4/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Below (4/9 DA) 4/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Below (0/5 DA) 0/5 tested authorities reached relay ≥3/5 tested (majority) (≥3/5 DA)
Valid Descriptor Partial (4/9 DA) 4/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (4/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 19.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.4d (0/9 DA above threshold)
Min/Max: 2.4d / 2.4d (4/9 DA, Voting / Total Eligible)
≥3.0d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8429.7d
Uptime Below (0/9 DA) 2.5d (R) ≥8.3d - 8.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/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 ≥3.0d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8429.7d
Prereq: V2Dir Below (4/9 DA) 4/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (4/9 DA) Median: 100.0% (4/9 DA above threshold) ≥98.0% (≥5/9 DA)
Time Known Below (3/9 DA) Median: 2.4d (0/9 DA above threshold)
Min/Max: 2.2d / 2.4d (4/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (3/9 DA) 3/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 ≥3.0d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8429.7d
Prereq: V2Dir Below (4/9 DA) 4/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (4/9 DA) Median: 100.0% (4/9 DA above threshold) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.6 more days) Median: 2.4d (0/9 DA above threshold)
Min/Max: 2.2d / 2.4d (4/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 19.8 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Partial (4/9 DA) Port 80: Yes | Port 443: Yes (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-09-20 15:00:35).

Capacity (Relay Reported)
Observed Bandwidth
19.83 Mbit/s
Advertised Bandwidth
19.83 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-09-20 15:00:35

Measured By
2/7 Bandwidth Authorities
Not measured by: bastet, faravahar, gabelmoo, longclaw, tor26
Median Measurement
19.8 Kbit/s
Min / Max
8 bit/s / 31.2 Kbit/s
Deviation
31.2 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 3h 2m 55s 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 11h 2m ago (2026-09-18 04:00:00)
Last Seen
3h 2m 55s ago (2026-09-20 12:00:00)
Last Restarted
2d 11h 57m ago (2026-09-18 03:05:44)
Last Changed Address
2026-09-18 04:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-09-20 07:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
the.hunters.ledger@gmail.com
Family Configuration
Family Support
MyFamily Only (5) — Legacy only. Consider migrating to Happy Families. | View Full Family (5)
Happy Families (family-cert)
Effective Members: 0
none

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

DNS Health
Status
Healthy (avg. 17.6s, 80th percentile)
Query Domain
311a89315491470a9c2c359b3ab9b2dd.81f71633.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
prsv (FR) E49E700B5048292F2FF786697C6BD4C07EE91A3C
Exit Address Used
45.76.234.136
Per-Instance Results
Cross Validation Attempt 1: Success, 15.8s (cv1_w3)
Cross Validation Attempt 2: Success, 21.5s (cv2_w3)
Cross Validation Attempt 3: Success, 15.5s (cv4_w3)
Tested: 2026-09-19 19:17:02 UTC
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
None
Full 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 45.76.234.136:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Sun, 20 Sep 2026 15:02:34 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-09-20 15:00:35).

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) No Y No
dannenberg (DE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Exit 19.8 Mbit/s | 816.0 Kbit/s 19.8 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 3.0d 2.5d | 8.5d 100.0% | 98.0% 2.4d | 1.0d 2026-09-20 13:08:04 8 bit/s
dizum (NL) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 19.8 Mbit/s | 816.0 Kbit/s 19.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 11.6d 2.5d | 8.3d 100.0% | 98.0% 2.4d | 1.0d 2026-09-20 13:08:04 19.8 Kbit/s
faravahar (US) No Y No
gabelmoo (DE) No Y No
longclaw (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 19.8 Mbit/s | 816.0 Kbit/s 19.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 13.3d 2.5d | 8.4d 100.0% | 98.0% 2.4d | 1.0d 2026-09-20 13:08:04 19.8 Kbit/s
maatuska (SE) No N No
moria1 (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 19.8 Mbit/s | 8.4 Mbit/s 19.8 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.4d | 8429.7d 2.5d | 8.8d 100.0% | 98.0% 2.2d | 9.8d 2026-09-20 13:08:04 31.2 Kbit/s
tor26 (AT) No Y No

— = 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.