Tor Relays :: mileirelay

View Relay "mileirelay"

Fingerprint: `5386EE7C770A785CFAD26E803C0146F9BCA62BD7` | Family: 1 relay | julianocarlson@proton.me | AS20115 | United States of America | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir (3)
BW Verified: 4/6 BW Auths Measured
Stability: Not Overloaded | UP 12h 55m 59s ago | UP 1% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 2y 3w 1d ago
BW Weight: 0.00% of Network | 0 Kbit/s Observed By Relay
Version: 0.4.9.5 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 0.3 days is below 8 days requirement (7.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.
HSDir: Time Known below threshold : Time Known 7.4 hours below 25 hours (dir-spec default)
Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.

Connectivity and Location

Addresses

OR Address: 66.169.194.135:500

Reachability (Directory Authorities)

IPv4: 9/9

Location

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

Autonomous System

AS Number: AS20115
AS Name: Charter Communications LLC (BGP.tools)
AS Rarity: Epic (score: 3/5, <0.05% consensus weight, 18 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 (9/9 DA)	9/9 authorities reached relay	≥5/9 DA ORPort reachable
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	Below (0/9 DA)	0 bit/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)	Majority: 0.3d (6/9 DA) Min/Med/Max: 0.3d / 0.3d / 0.3d (9/9 DA, Voting / Total Eligible)	≥11.3d - 55.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥347.6d
Stable	Uptime	Below (0/9 DA)	0.5d (R)	≥12.0d - 14.4d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (0/9 DA)	0/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	≥11.3d - 55.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥347.6d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (9/9 DA)	Majority: 100.0% (9/9 DA)	≥98.0% (≥5/9 DA)
	Time Known	Below (0/9 DA)	Majority: 0.3d (6/9 DA) Min/Med/Max: 0.3d / 0.3d / 0.3d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below (0/9 DA)	0/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	≥11.3d - 55.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥347.6d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (9/9 DA)	Majority: 100.0% (9/9 DA)	≥98% (≥5/9 DA)
	Time Known	Below (0/9 DA) (need 7.7 more days)	Majority: 0.3d (6/9 DA) Min/Med/Max: 0.3d / 0.3d / 0.3d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	0 bit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.0 Mbit/s (≥5/9 DA)
Exit	Exit Policy	Below (0/9 DA)	Port 80: No \| Port 443: No (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 08:45:07).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 0.00 Kbit/s
Advertised Bandwidth: Unknown
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 36 TB (5 years)
1mo: 767 GB | 6mo: 3.6 TB | 1y: 24 TB | 5y: 36 TB

Measurement (Directory Authority Verified)

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

Measured By: 4/6 Bandwidth Authorities
Not measured by: bastet, longclaw
Median Measurement: 0 bit/s
Min / Max: 0 bit/s / 8 bit/s

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

Uptime and Stability

Uptime Metrics

Current Status: UP 12h 55m 59s ago
Overall Uptime (1M/6M/1Y/5Y): 1.9%/0.0%/9.3%/30.9%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (1.9%/0.0%/9.3%/30.9%)
Hibernating: No

Timestamps

First Seen: 2y 3w 1d ago (2024-02-21 20:00:00)
Last Seen: 2h 45m 53s ago (2026-03-15 07:00:00)
Last Restarted: 12h 55m 59s ago (2026-03-14 20:49:54)
Last Changed Address: 2024-02-21 20:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: julianocarlson@proton.me

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

5386EE7C770A785CFAD26E803C0146F9BCA62BD7 (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

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 Sun, 15 Mar 2026 09:45:51 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-15 08: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	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	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 208.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 59.7d	0.5d \| 13.6d	100.0% \| 98.0%	0.3d \| 1.0d	2026-03-14 20:50:58	—
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 11.3d	0.5d \| 14.3d	100.0% \| 98.0%	0.3d \| 1.0d	2026-03-14 20:50:58	—
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 45.8d	0.5d \| 12.0d	100.0% \| 98.0%	0.3d \| 1.0d	2026-03-14 20:50:58	—
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 55.1d	0.5d \| 14.5d	100.0% \| 98.0%	0.3d \| 1.0d	2026-03-14 20:50:58	—
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 61.4d	0.5d \| 14.4d	100.0% \| 98.0%	0.3d \| 1.0d	2026-03-14 20:50:58	8 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 62.0d	0.5d \| 14.5d	100.0% \| 98.0%	0.3d \| 1.0d	2026-03-14 20:50:58	—
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 40.2d	0.5d \| 14.3d	100.0% \| 98.0%	0.3d \| 1.0d	2026-03-14 20:50:58	8 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s \| 8.4 Mbit/s	0 bit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 347.6d	0.5d \| 15.5d	100.0% \| 98.0%	0.3d \| 9.8d	2026-03-14 20:50:58	8 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s \| 816.0 Kbit/s	0 bit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	0.3d \| 8d	0.3d \| 55.7d	0.5d \| 14.5d	100.0% \| 98.0%	0.3d \| 1.0d	2026-03-14 20:50:58	8 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.