Tor Relays :: charon

View Relay "charon"

Fingerprint: `BBB9DF20A00397E2C1FD4901C709230B14DD5743` | Family: 4 relays | gleepdorf AT proton DOT me | AS64245 | United States of America | Linux

Health Status

Consensus: In Consensus (8/8 Directory Auths)
Flags: Running, Valid, Fast, Stable (4)
BW Verified: 5/5 BW Auths Measured 15 Kbit/s Median
Stability: Not Overloaded | UP 4d 8h 58m ago | UP 100% (1M)

Reachability: IPv4: 8/9 | v6: 7/8 (Directory Auths)
First Seen: 5d 7h 45m ago
BW Weight: 0.00% of Network | 15 Mbit/s Observed By Relay
Version: 0.4.9.6 Recommended

Issues Detected:

Guard: bandwidth below threshold : Observed bandwidth 2.0 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: Time Known below threshold : Time Known 5.3 days is below 8 days requirement (2.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.
HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
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.

Notes:

Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses

OR Address: 104.250.109.49:9001
[2602:ffb0:38:31::a]:9001

Reachability (Directory Authorities)

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

Location

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

Autonomous System

AS Number: AS64245
AS Name: DigitalFyre Internet Solutions, LLC. (BGP.tools)
AS Rarity: Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, Fast, Stable

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (8/8 DA)	8/8 authorities reached relay	≥5/8 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 (8/8 DA)	8/8 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir	DirPort Available	Below (0/8 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast	Speed	Meets (8/8 DA)	15.8 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below (0/8 DA)	Median: 5.3d (0/8 DA above threshold) Min/Max: 5.2d / 5.3d (8/8 DA, Voting / Total Eligible)	≥32.5d - 59.1d (varies) (≥5/8 DA) [Stricter] moria1: ≥313.0d
Stable	Uptime	Below (0/8 DA)	4.4d (R)	≥7.0d - 7.1d (varies) (≥5/8 DA)
HSDir	Prereq: Fast	Meets (8/8 DA)	8/8 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (8/8 DA)	8/8 DA assigned Stable	≥32.5d - 59.1d (varies) (≥5/8 DA) [Stricter] moria1: ≥313.0d
	Prereq: V2Dir	Below (0/8 DA)	0/8 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
	WFU	Meets (8/8 DA)	Majority: 100.0% (8/8 DA)	≥98.0% (≥5/8 DA)
	Time Known	Meets (7/8 DA)	Median: 5.3d (0/8 DA above threshold) Min/Max: 4.1d / 5.3d (8/8 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/8 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (8/8 DA)	8/8 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (8/8 DA)	8/8 DA assigned Stable	≥32.5d - 59.1d (varies) (≥5/8 DA) [Stricter] moria1: ≥313.0d
	Prereq: V2Dir	Below (0/8 DA)	0/8 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/8 DA)
	WFU	Meets (8/8 DA)	Majority: 100.0% (8/8 DA)	≥98% (≥5/8 DA)
	Time Known	Below (0/8 DA) (need 2.7 more days)	Median: 5.3d (0/8 DA above threshold) Min/Max: 4.1d / 5.3d (8/8 DA, Voting / Total Eligible)	≥8 days (≥5/8 DA)
	Bandwidth	Below (0/8 DA)	15.8 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/8 DA)
Exit	Exit Policy	Below (0/8 DA)	Port 80: No \| Port 443: No (R)	Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

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

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 15.75 Mbit/s
Advertised Bandwidth: 15.75 Mbit/s
Rate Limit: 41.94 Mbit/s
Burst Limit: 83.89 Mbit/s
Total Data: 3.7 GB (1 month)

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-15 01:45:03

Measured By: 5/5 Bandwidth Authorities
Median Measurement: 15.5 Kbit/s
Min / Max: 2800 bit/s / 17.6 Kbit/s
Deviation: 14.8 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0006% of network (15th pctl) | Guard: N/A | Middle: 0.0017% (27th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 4d 8h 58m ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 5d 7h 45m ago (2026-04-09 19:00:00)
Last Seen: 4h 45m 46s ago (2026-04-14 22:00:00)
Last Restarted: 4d 8h 58m ago (2026-04-10 17:46:51)
Last Changed Address: 2026-04-09 19:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-14 18:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: gleepdorf AT proton DOT me

Family Configuration

Family Support: MyFamily Only (4) — Legacy only. Consider migrating to Happy Families. | View Full Family (4)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 4

28742D1302E350F0BA4E6117C751B16110DA4359
5924E03FD96E6A4A16DC49F110F442EC055BB366
8FCFA9A2EFBF4D4BBE0BB32F2346A78DFA9B8C49
BBB9DF20A00397E2C1FD4901C709230B14DD5743 (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 Wed, 15 Apr 2026 02:45:45 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-15 01:45:03).

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	—	—	—	N	No	—	—	—	—	—	—	—	—	—	—	—	—
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast, Stable	15.8 Mbit/s \| 816.0 Kbit/s	15.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	5.3d \| 8d	5.3d \| 32.5d	4.4d \| 7.0d	100.0% \| 98.0%	5.3d \| 1.0d	2026-04-14 14:32:57	15.8 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast, Stable	15.8 Mbit/s \| 816.0 Kbit/s	15.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	5.3d \| 8d	5.3d \| 41.4d	4.4d \| 7.0d	100.0% \| 98.0%	5.3d \| 1.0d	2026-04-14 14:32:57	15.8 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast, Stable	15.8 Mbit/s \| 816.0 Kbit/s	15.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	5.3d \| 8d	5.3d \| 59.3d	4.4d \| 7.1d	100.0% \| 98.0%	5.3d \| 1.0d	2026-04-14 14:32:57	15.8 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	15.8 Mbit/s \| 816.0 Kbit/s	15.8 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	5.2d \| 8d	5.2d \| 59.0d	4.4d \| 7.2d	100.0% \| 98.0%	5.2d \| 1.0d	2026-04-14 14:32:57	2800 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	—	Running, Valid, Fast, Stable	15.8 Mbit/s \| 816.0 Kbit/s	15.8 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	5.3d \| 8d	5.3d \| 59.1d	4.4d \| 7.1d	100.0% \| 98.0%	5.3d \| 1.0d	2026-04-14 14:32:57	17.6 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	15.8 Mbit/s \| 816.0 Kbit/s	15.8 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	5.3d \| 8d	5.3d \| 59.1d	4.4d \| 7.0d	100.0% \| 98.0%	5.3d \| 1.0d	2026-04-14 14:32:57	4320 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	15.8 Mbit/s \| 8.4 Mbit/s	15.8 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	4.1d \| 8d	5.3d \| 313.0d	4.4d \| 8.0d	100.0% \| 98.0%	4.1d \| 9.8d	2026-04-14 14:32:57	15.2 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast, Stable	15.8 Mbit/s \| 816.0 Kbit/s	15.8 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	5.2d \| 8d	5.2d \| 59.3d	4.4d \| 7.5d	100.0% \| 98.0%	5.2d \| 1.0d	2026-04-14 14:32:57	8.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.