Tor Relays :: HiMom

View Relay "HiMom"

Fingerprint: `BA2AB4075B2D1F431DE74B2C22D23D430E1B2688` | Family: 1 relay | E5D3A99B2AC5B90EA5DB735767A71BE36A62F... | AS53667 | United States of America | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Exit (5)
DNS Health: Healthy (22.6s, 97th percentile) (via exitdnshealth.1aeo.com)
BW Verified: 5/6 BW Auths Measured 41 Kbit/s Median
Stability: Not Overloaded | UP 1w 2d 20h ago | UP 99% (1M)

Reachability: IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen: 4y 1mo 3w ago
BW Weight: 0.00% of Network | 94 Mbit/s Observed By Relay
Version: 0.4.9.5 Recommended

Issues Detected:

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: WFU below threshold : Weighted Fractional Uptime 97.9% is below 98% requirement
Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
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 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: WFU below threshold : WFU 97.9% below 98% required for HSDir
Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
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: tor-exit.cyberjake.xyz
198.98.50.199:9001
[2605:6400:10:1008:1111:1111:1111:1111]:9001
Exit Address: 198.98.50.199

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 7/7 (2 don't test)

Location

Country: United States of America
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS53667
AS Name: FranTech Solutions (BGP.tools)
AS Rarity: Emerging (score: 1/5, 2.17% consensus weight, 74 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit

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
Running	IPv6 Reachability	Meets (7/7 DA)	7/7 tested authorities reached relay	≥4/7 tested (majority) (≥4/7 DA)
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)	94.3 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 (1/9 DA)	Median: 2.6d (1/9 DA above threshold) Min/Max: 1.5d / 16981.2d (9/9 DA, Voting / Total Eligible)	≥11.4d - 53.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥353.6d
Stable	Uptime	Below (1/9 DA)	9.9d (R)	≥9.6d - 12.6d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/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 (1/9 DA)	1/9 DA assigned Stable	≥11.4d - 53.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥353.6d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (7/9 DA)	Median: 98.6% (7/9 DA above threshold) Min/Max: 97.5% / 99.3% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 14.0d (9/9 DA above threshold) Min/Max: 9.5d / 15.1d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (9/9 DA)	9/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 (1/9 DA)	1/9 DA assigned Stable	≥11.4d - 53.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥353.6d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (7/9 DA)	Median: 98.6% (7/9 DA above threshold) Min/Max: 97.5% / 99.3% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 14.0d (9/9 DA above threshold) Min/Max: 9.5d / 15.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	94.3 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	Meets (9/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-03-15 23:45:07).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 94.33 Mbit/s
Advertised Bandwidth: 41.94 Mbit/s
Rate Limit: 41.94 Mbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 361 TB (5 years)
1mo: 3.5 TB | 6mo: 13 TB | 1y: 46 TB | 5y: 361 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 23:45:07

Measured By: 5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement: 41.9 Kbit/s
Min / Max: 24.0 Kbit/s / 280.0 Kbit/s
Deviation: 256.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0026% of network (35th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0077% (14th pctl)

Uptime and Stability

Uptime Metrics

Current Status: UP 1w 2d 20h ago
Overall Uptime (1M/6M/1Y/5Y): 99.1%/57.9%/78.6%/89.4%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (99.1%/57.9%/78.6%/89.4%)
Hibernating: No

Timestamps

First Seen: 4y 1mo 3w ago (2022-01-23 00:00:00)
Last Seen: 1h 45m 49s ago (2026-03-15 23:00:00)
Last Restarted: 1w 2d 20h ago (2026-03-06 03:55:53)
Last Changed Address: 2026-03-05 14:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: E5D3A99B2AC5B90EA5DB735767A71BE36A62FF0F tor(at)cyberjake(dot)xyz

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

BA2AB4075B2D1F431DE74B2C22D23D430E1B2688 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.5 on Linux
Version: 0.4.9.5 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Status

Healthy (avg. 22.6s, 97th percentile)

Query Domain

b5b412458a664661b7e53b6ca6faf4e9.ba2ab407.tor.exit.validator.1aeo.com

DNS Result

Resolved to 64.65.4.1

Cross-Validation

4/4 instances succeeded

First Hop

DFRI13 (SE) 0D967EACE42448A08E244366DF753BBFF611EB37

Exit Address Used

198.98.50.199

Per-Instance Results

Cross Validation Attempt 1:	Success, 24.2s	(cv1_w3)
Cross Validation Attempt 2:	Success, 19.0s	(cv2_w3)
Cross Validation Attempt 3:	Success, 25.2s	(cv3_w3)
Cross Validation Attempt 4:	Success, 21.8s	(cv4_w3)

Tested: 2026-03-15 19:16:35 UTC

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

reject: 
  25
  465
  587

IPv6 Exit Policy Summary

reject: 
  25
  465
  587

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 198.98.50.199:*
reject *:25
reject *:465
reject *:587
accept *:*

Last fetch was at Mon, 16 Mar 2026 00:45:48 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-15 23:45: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	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	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	94.3 Mbit/s \| 816.0 Kbit/s	94.3 Mbit/s \| 208.0 Mbit/s OR 16.0 Mbit/s	97.9% \| 98%	14.2d \| 8d	1.9d \| 57.1d	9.9d \| 11.9d	97.9% \| 98.0%	14.2d \| 1.0d	2026-03-15 20:33:50	53.6 Kbit/s
dannenberg (DE)	Yes	Yes	Yes	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	94.3 Mbit/s \| 816.0 Kbit/s	94.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	97.5% \| 98%	12.0d \| 8d	1.5d \| 11.4d	9.9d \| 12.6d	97.5% \| 98.0%	12.0d \| 1.0d	2026-03-15 20:33:50	41.9 Kbit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	—	Valid, V2Dir, Fast, Exit	94.3 Mbit/s \| 816.0 Kbit/s	94.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.6% \| 98%	15.1d \| 8d	3.8d \| 43.1d	9.9d \| 9.6d	98.6% \| 98.0%	15.1d \| 1.0d	2026-03-15 20:33:50	41.9 Kbit/s
faravahar (US)	Yes	Yes	Yes	—	N	Yes	Yes	Valid, V2Dir, Fast, Exit	94.3 Mbit/s \| 816.0 Kbit/s	94.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.0% \| 98%	14.0d \| 8d	1.9d \| 53.2d	9.9d \| 12.8d	98.0% \| 98.0%	14.0d \| 1.0d	2026-03-15 20:33:50	41.9 Kbit/s
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	94.3 Mbit/s \| 816.0 Kbit/s	94.3 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	98.8% \| 98%	14.3d \| 8d	2.9d \| 58.2d	9.9d \| 12.5d	98.8% \| 98.0%	14.3d \| 1.0d	2026-03-15 20:33:50	38.4 Kbit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	—	Running, Valid, V2Dir, Fast, Exit	94.3 Mbit/s \| 816.0 Kbit/s	94.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.3% \| 98%	13.9d \| 8d	4.1d \| 61.2d	9.9d \| 12.8d	99.3% \| 98.0%	13.9d \| 1.0d	2026-03-15 20:33:50	41.9 Kbit/s
maatuska (SE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	94.3 Mbit/s \| 816.0 Kbit/s	94.3 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	99.0% \| 98%	13.8d \| 8d	2.5d \| 40.9d	9.9d \| 12.6d	99.0% \| 98.0%	13.8d \| 1.0d	2026-03-15 20:33:50	24.0 Kbit/s
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard, Exit	94.3 Mbit/s \| 8.4 Mbit/s	94.3 Mbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	98.6% \| 98%	9.5d \| 8d	16981.2d \| 353.6d	9.9d \| 15.3d	98.6% \| 98.0%	9.5d \| 9.8d	2026-03-15 20:33:50	280.0 Kbit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	94.3 Mbit/s \| 816.0 Kbit/s	94.3 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	98.8% \| 98%	15.0d \| 8d	2.6d \| 53.9d	9.9d \| 12.8d	98.8% \| 98.0%	15.0d \| 1.0d	2026-03-15 20:33:50	40.0 Kbit/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.