Tor Relays :: LillyCL

View Relay "LillyCL"

Fingerprint: `6EB89BEC0CF927F50AE76699F42A60BE6EFD0C77` | Family: 15 relays | nashepro [at] proton [dot] me | AS270013 | Chile | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Exit (5)
DNS Health: Not Tested (via exitdnshealth.1aeo.com)
BW Verified: 5/6 BW Auths Measured 6800 bit/s Median
Stability: Not Overloaded | UP 3d 6h 33m ago | UP 78% (1M)

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 7mo 3w 3d ago
BW Weight: 0.00% of Network | 19 Mbit/s Observed By Relay
Version: 0.4.9.6 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 70.8% 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 70.8% 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: 151.242.242.16:9001
[2803:29e0:10:3296::1]:9001
Exit Address: 151.242.242.16

Reachability (Directory Authorities)

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

Location

Country: Chile
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS270013
AS Name: Unknown
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 4 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 (8/8 DA)	8/8 tested authorities reached relay	≥5/8 tested (majority) (≥5/8 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)	19.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: 3.1d (1/9 DA above threshold) Min/Max: 2.2d / 14161.6d (9/9 DA, Voting / Total Eligible)	≥17.9d - 58.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥293.7d
Stable	Uptime	Below (0/9 DA)	3.3d (R)	≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/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	≥17.9d - 58.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥293.7d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 71.0% (0/9 DA above threshold) Min/Max: 68.5% / 72.0% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 13.9d (9/9 DA above threshold) Min/Max: 10.0d / 14.3d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets (8/9 DA)	8/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	≥17.9d - 58.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥293.7d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 71.0% (0/9 DA above threshold) Min/Max: 68.5% / 72.0% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 13.9d (9/9 DA above threshold) Min/Max: 10.0d / 14.3d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	19.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-29 12:45:07).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 19.29 Mbit/s
Advertised Bandwidth: 19.29 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 995 GB (1 year)
1mo: 144 GB | 6mo: 605 GB | 1y: 995 GB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 12:45:07

Measured By: 5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement: 6800 bit/s
Min / Max: 2640 bit/s / 19.3 Kbit/s
Deviation: 16.6 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0003% of network (12th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0008% (2th pctl)

Uptime and Stability

Uptime Metrics

Current Status: UP 3d 6h 33m ago
Overall Uptime (1M/6M/1Y/5Y): 78.4%/72.5%/78.7%/0.0%
Flag Uptime (1M/6M/1Y/5Y): 14.8%/2.2%/1.2%/—
Hibernating: No

Timestamps

First Seen: 7mo 3w 3d ago (2025-08-07 03:00:00)
Last Seen: 2h 45m 55s ago (2026-03-29 10:00:00)
Last Restarted: 3d 6h 33m ago (2026-03-26 06:12:48)
Last Changed Address: 2026-03-15 02:00:00

Overload Status: Not Overloaded — No overload conditions reported.

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

Status: Not Tested

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

accept: 
  53
  80
  443

IPv6 Exit Policy Summary

accept: 
  53
  80
  443

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 151.242.242.16:*
accept *:53
accept *:80
accept *:443
reject *:*

Last fetch was at Sun, 29 Mar 2026 12:45:53 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 12: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	19.3 Mbit/s \| 816.0 Kbit/s	19.3 Mbit/s \| 200.0 Mbit/s OR 16.0 Mbit/s	70.8% \| 98%	14.2d \| 8d	2.9d \| 63.5d	3.3d \| 3.3d	70.8% \| 98.0%	14.2d \| 1.0d	2026-03-29 06:13:16	19.3 Kbit/s
dannenberg (DE)	Yes	Yes	Yes	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	19.3 Mbit/s \| 816.0 Kbit/s	19.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	69.6% \| 98%	13.9d \| 8d	2.2d \| 17.9d	3.3d \| 3.4d	69.6% \| 98.0%	13.9d \| 1.0d	2026-03-29 06:13:16	19.3 Kbit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	19.3 Mbit/s \| 816.0 Kbit/s	19.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	68.5% \| 98%	13.2d \| 8d	3.1d \| 42.9d	3.3d \| 3.4d	68.5% \| 98.0%	13.2d \| 1.0d	2026-03-29 06:13:16	19.3 Kbit/s
faravahar (US)	Yes	Yes	Yes	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	19.3 Mbit/s \| 816.0 Kbit/s	19.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	71.5% \| 98%	14.0d \| 8d	2.5d \| 56.6d	3.3d \| 3.4d	71.5% \| 98.0%	14.0d \| 1.0d	2026-03-29 06:13:16	19.3 Kbit/s
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	19.3 Mbit/s \| 816.0 Kbit/s	19.3 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	71.0% \| 98%	14.3d \| 8d	3.4d \| 62.1d	3.3d \| 3.4d	71.0% \| 98.0%	14.3d \| 1.0d	2026-03-29 06:13:16	3840 bit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	—	Running, Valid, V2Dir, Fast, Exit	19.3 Mbit/s \| 816.0 Kbit/s	19.3 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	71.0% \| 98%	13.5d \| 8d	4.9d \| 62.6d	3.3d \| 3.4d	71.0% \| 98.0%	13.5d \| 1.0d	2026-03-29 06:13:16	5600 bit/s
maatuska (SE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	19.3 Mbit/s \| 816.0 Kbit/s	19.3 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	71.5% \| 98%	13.8d \| 8d	3.1d \| 50.7d	3.3d \| 3.4d	71.5% \| 98.0%	13.8d \| 1.0d	2026-03-29 06:13:16	2640 bit/s
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Stable, Exit	19.3 Mbit/s \| 8.4 Mbit/s	19.3 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	69.0% \| 98%	10.0d \| 8d	14161.6d \| 293.7d	3.3d \| 4.1d	69.0% \| 98.0%	10.0d \| 9.9d	2026-03-29 06:13:16	6800 bit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Exit	19.3 Mbit/s \| 816.0 Kbit/s	19.3 Mbit/s \| 264.0 Mbit/s OR 16.0 Mbit/s	72.0% \| 98%	14.1d \| 8d	3.0d \| 58.7d	3.3d \| 3.8d	72.0% \| 98.0%	14.1d \| 1.0d	2026-03-29 06:13:16	4400 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.

View Relay "LillyCL"

Fingerprint: `6EB89BEC0CF927F50AE76699F42A60BE6EFD0C77` | Family: 15 relays | nashepro [at] proton [dot] me | AS270013 | Chile | Linux

Health Status

Connectivity and Location

Addresses

Reachability (Directory Authorities)

Location

Autonomous System

Flags and Eligibility

Eligibility Flag Vote Details

Bandwidth Metrics

Capacity (Relay Reported)

Measurement (Directory Authority Verified)

Uptime and Stability

Uptime Metrics

Timestamps

Operator and Family

Operator Identity

Family Configuration

Software and Version

Exit Health & Policy

DNS Health

IPv4 Exit Policy Summary

IPv6 Exit Policy Summary

Full Exit Policy

Consensus Evaluation

Per-Authority Details

View Relay "LillyCL"

Fingerprint: 6EB89BEC0CF927F50AE76699F42A60BE6EFD0C77 | Family: 15 relays | nashepro [at] proton [dot] me | AS270013 | Chile | Linux

Addresses

Reachability (Directory Authorities)

Location

Autonomous System

Eligibility Flag Vote Details

Capacity (Relay Reported)

Measurement (Directory Authority Verified)

Uptime Metrics

Timestamps

Operator Identity

Family Configuration

Full Exit Policy

Fingerprint: `6EB89BEC0CF927F50AE76699F42A60BE6EFD0C77` | Family: 15 relays | nashepro [at] proton [dot] me | AS270013 | Chile | Linux