View Relay "mynode19"

Fingerprint: FF562296DCFE6AF337AECDDD61DCD5320CECE35A | Family: 5 relays | intel@the-hunters-ledger.com | AS14061 | United Kingdom of Great Britain and Northern Ireland | Linux

Health Status

Consensus
In Consensus (5/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Healthy (0.3s, 0th percentile) (via exitdnshealth.1aeo.com)
BW Verified
2/7 BW Auths Measured 57 Kbit/s Median
Stability
Not Overloaded | UP 2d 9h 28m ago
Reachability
IPv4: 5/9 | v6: 4/8 (Directory Auths)
First Seen
2d 9h 2m ago
BW Weight
0.00% of Network | 57 Mbit/s Observed By Relay
Version
0.4.9.12 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 2.3 days is below 8 days requirement (5.7 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.
Notes:
  • Partial IPv4 reachability: 5/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
167.99.204.37:9001
[2a03:b0c0:1:e0:0:1:bdad:c001]:9001
Exit Address
167.99.204.37
Reachability (Directory Authorities)
IPv4
5/9
IPv6
4/8 (1 don't test)
Location
Country
United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14061
AS Name
DigitalOcean, LLC (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.13% consensus weight, 39 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 5/9 | Valid: 5/9 | V2Dir: 5/9 | Fast: 3/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 5/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (5/9 DA) 5/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Partial (4/8 DA) 4/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (5/9 DA) 5/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (5/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 57.9 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.3d (0/9 DA above threshold)
Min/Max: 2.3d / 2.3d (5/9 DA, Voting / Total Eligible)		 ≥3.0d - 12.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8403.5d
Uptime Below (0/9 DA) 2.4d (R) ≥8.3d - 8.6d (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.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8403.5d
Prereq: V2Dir Meets (5/9 DA) 5/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (5/9 DA) Majority: 100.0% (5/9 DA) ≥98.0% (≥5/9 DA)
Time Known Below (4/9 DA) Median: 2.3d (0/9 DA above threshold)
Min/Max: 2.1d / 2.3d (5/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.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8403.5d
Prereq: V2Dir Meets (5/9 DA) 5/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (5/9 DA) Majority: 100.0% (5/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.7 more days) Median: 2.3d (0/9 DA above threshold)
Min/Max: 2.1d / 2.3d (5/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 57.9 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 Meets (5/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 13:00:43).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
57.94 Mbit/s
Advertised Bandwidth
57.94 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 13:00:43

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

Uptime and Stability

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

Operator and Family

Operator Identity

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

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
intel@the-hunters-ledger.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

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 0.3s, 0th percentile)
Query Domain
e93bf3bd1e2e478a9d0acc728ef9c8a2.ff562296.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
Quintex516 (US) 6843984A50ABE26232C38BDF51B48C0AA7F04ECD
Exit Address Used
167.99.204.37
Per-Instance Results
Cross Validation Attempt 1: Success, 0.2s (cv1_w5)
Cross Validation Attempt 2: Success, 0.2s (cv2_w5)
Cross Validation Attempt 3: Success, 0.4s (cv3_w5)
Cross Validation Attempt 4: Success, 0.2s (cv4_w5)
Tested: 2026-09-19 19:27:20 UTC
Source: exitdnshealth.1aeo.com
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 167.99.204.37:*
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 14:02:29 GMT.

Consensus Evaluation

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

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) No — — — Y No — — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 57.9 Mbit/s | 816.0 Kbit/s 57.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.3d | 8d 2.3d | 3.0d 2.4d | 8.6d 100.0% | 98.0% 2.3d | 1.0d 2026-09-20 08:03:26 8 bit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 57.9 Mbit/s | 816.0 Kbit/s 57.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.3d | 8d 2.3d | 11.6d 2.4d | 8.4d 100.0% | 98.0% 2.3d | 1.0d 2026-09-20 08:03:26 57.9 Kbit/s
faravahar (US) No — — — Y No — — — — — — — — — — — —
gabelmoo (DE) No — — — Y No — — — — — — — — — — — —
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit 57.9 Mbit/s | 816.0 Kbit/s 57.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.3d | 8d 2.3d | 13.2d 2.4d | 8.4d 100.0% | 98.0% 2.3d | 1.0d 2026-09-20 08:03:26 57.9 Kbit/s
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 57.9 Mbit/s | 816.0 Kbit/s 57.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.3d | 8d 2.3d | 11.1d 2.4d | 8.4d 100.0% | 98.0% 2.3d | 1.0d 2026-09-20 08:03:26 57.9 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 57.9 Mbit/s | 8.4 Mbit/s 57.9 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.1d | 8d 2.3d | 8403.5d 2.4d | 8.8d 100.0% | 98.0% 2.1d | 9.8d 2026-09-20 08:03:26 8 bit/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.