Tor Relays :: Weaponized2

View Relay "Weaponized2"

Fingerprint: `E6272D9DC1D39FDB4C1DAC2F206127448A640752` | Family: 1 relay | danvondra (at) protonmail (dot) com | AS10796 | United States of America | Linux

Health Status

Consensus: In Consensus (7/7 Directory Auths)
Flags: Running, Valid, V2Dir (3)
BW Verified: 5/5 BW Auths Measured 48 bit/s Median
Stability: Overloaded | UP 2d 6h 59m ago | UP 97% (1M)

Reachability: IPv4: 7/9 (Directory Auths)
First Seen: 3w 6d 9h ago
BW Weight: 0.00% of Network | 860 Kbit/s Observed By Relay
Version: 0.4.9.6 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.1 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: WFU below threshold : Weighted Fractional Uptime 95.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 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.
HSDir: WFU below threshold : WFU 95.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.
Read Bandwidth Limit Hit : Read rate limit (4 Mbit/s) was hit 12 times. Relay is throttling inbound traffic.
Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.

Notes:

Partial IPv4 reachability: 7/9 authorities can reach this relay
Rate Limit Configuration: Configured limits: Rate=4 Mbit/s, Burst=4 Mbit/s. Limits hit: Write=0, Read=12.

Connectivity and Location

Addresses

OR Address: 98.31.36.230:10001

Reachability (Directory Authorities)

IPv4: 7/9

Location

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

Autonomous System

AS Number: AS10796
AS Name: Charter Communications Inc (BGP.tools)
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (7/7 DA)	7/7 authorities reached relay	≥4/7 DA ORPort reachable
Valid	Descriptor	Meets (7/7 DA)	7/7 authorities assigned Valid	Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir	DirPort Available	Meets (7/7 DA)	Tunnelled: Yes (no DirPort) (R)	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast	Speed	Meets (7/7 DA)	860.2 Kbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below (1/7 DA)	Median: 4.2d (1/7 DA above threshold) Min/Max: 3.0d / 14169.8d (7/7 DA, Voting / Total Eligible)	≥16.3d - 52.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥366.6d
Stable	Uptime	Below (0/7 DA)	2.3d (R)	≥7.5d - 8.3d (varies) (≥4/7 DA)
HSDir	Prereq: Fast	Below (2/7 DA)	2/7 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (3/7 DA)	3/7 DA assigned Stable	≥16.3d - 52.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥366.6d
	Prereq: V2Dir	Meets (7/7 DA)	7/7 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
	WFU	Below (0/7 DA)	Median: 96.1% (0/7 DA above threshold) Min/Max: 93.1% / 97.4% (7/7 DA, Voting / Total Eligible)	≥98.0% (≥4/7 DA)
	Time Known	Meets (6/7 DA)	Median: 14.1d (7/7 DA above threshold) Min/Max: 9.9d / 21.0d (7/7 DA, Voting / Total Eligible)	≥1.0d (most) (≥4/7 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Below (2/7 DA)	2/7 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (3/7 DA)	3/7 DA assigned Stable	≥16.3d - 52.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥366.6d
	Prereq: V2Dir	Meets (7/7 DA)	7/7 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
	WFU	Below (0/7 DA)	Median: 96.1% (0/7 DA above threshold) Min/Max: 93.1% / 97.4% (7/7 DA, Voting / Total Eligible)	≥98% (≥4/7 DA)
	Time Known	Meets (7/7 DA)	Median: 14.1d (7/7 DA above threshold) Min/Max: 9.9d / 21.0d (7/7 DA, Voting / Total Eligible)	≥8 days (≥4/7 DA)
	Bandwidth	Below (0/7 DA)	860.2 Kbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.0 Mbit/s (≥4/7 DA)
Exit	Exit Policy	Below (0/7 DA)	Port 80: No \| Port 443: No (R)	Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-05-04 08:45:08).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 860.16 Kbit/s
Advertised Bandwidth: 860.16 Kbit/s
Rate Limit: 4.10 Mbit/s
Burst Limit: 4.10 Mbit/s
Total Data: 707 GB (5 years)
1mo: 9.8 GB | 6mo: 119 GB | 1y: 442 GB | 5y: 707 GB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-04 08:45:08

Measured By: 5/5 Bandwidth Authorities
Median Measurement: 48 bit/s
Min / Max: 24 bit/s / 856 bit/s
Deviation: 832 bit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0000% of network (1th pctl) | Guard: N/A | Middle: 0.0000% (1th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 6h 59m ago
Overall Uptime (1M/6M/1Y/5Y): 97.7%/90.7%/93.3%/92.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (97.7%/90.7%/93.3%/92.0%)
Hibernating: No

Timestamps

First Seen: 3w 6d 9h ago (2026-04-06 23:00:00)
Last Seen: 1h 45m 43s ago (2026-05-04 07:00:00)
Last Restarted: 2d 6h 59m ago (2026-05-02 01:46:12)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — Rate limits hit W:0 R:12 (limit: 4 Mbit/s)

General Overload (from /details)

Status: Not Reported

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)

Status: Not Reported

Rate Limits (from /bandwidth)

Rate Limit: 4.10 Mbit/s
Burst Limit: 4.10 Mbit/s
Write Limit Hit: 0 times
Read Limit Hit: 12 times
Last Reported: 17 hours ago

Recommendations

Consider increasing RelayBandwidthRate
Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-04 01:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: danvondra (at) protonmail (dot) com

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

E6272D9DC1D39FDB4C1DAC2F206127448A640752 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.6 on Linux
Version: 0.4.9.6 — 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

Full Exit Policy

reject *:*

Last fetch was at Mon, 04 May 2026 08:45:42 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-04 08:45:08).

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)	No	—	—	—	N	No	—	—	—	—	—	—	—	—	—	—	—
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	860.2 Kbit/s \| 816.0 Kbit/s	860.2 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	95.9% \| 98%	13.5d \| 8d	3.7d \| 49.6d	2.3d \| 8.3d	95.9% \| 98.0%	13.5d \| 1.0d	2026-05-03 15:21:01	856 bit/s
dizum (NL)	No	—	—	—	N	No	—	—	—	—	—	—	—	—	—	—	—
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	860.2 Kbit/s \| 816.0 Kbit/s	860.2 Kbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	96.1% \| 98%	14.1d \| 8d	4.0d \| 53.5d	2.3d \| 8.5d	96.1% \| 98.0%	14.1d \| 1.0d	2026-05-03 15:21:01	856 bit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	860.2 Kbit/s \| 816.0 Kbit/s	860.2 Kbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	97.4% \| 98%	21.0d \| 8d	6.4d \| 52.1d	2.3d \| 7.6d	97.4% \| 98.0%	21.0d \| 1.0d	2026-05-03 15:21:01	24 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	860.2 Kbit/s \| 816.0 Kbit/s	860.2 Kbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	96.2% \| 98%	14.5d \| 8d	4.2d \| 55.7d	2.3d \| 7.6d	96.2% \| 98.0%	14.5d \| 1.0d	2026-05-03 15:21:01	48 bit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	860.2 Kbit/s \| 816.0 Kbit/s	860.2 Kbit/s \| 320.0 Mbit/s OR 16.0 Mbit/s	93.1% \| 98%	12.7d \| 8d	3.0d \| 16.3d	2.3d \| 7.5d	93.1% \| 98.0%	12.7d \| 1.0d	2026-05-03 15:21:01	24 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	860.2 Kbit/s \| 8.4 Mbit/s	860.2 Kbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	94.4% \| 98%	9.9d \| 8d	14169.8d \| 366.6d	2.3d \| 11.0d	94.4% \| 98.0%	9.85d \| 9.90d	2026-05-03 15:21:01	64 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	860.2 Kbit/s \| 816.0 Kbit/s	860.2 Kbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	97.3% \| 98%	20.3d \| 8d	6.3d \| 52.1d	2.3d \| 8.8d	97.3% \| 98.0%	20.3d \| 1.0d	2026-05-03 15:21:01	24 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.