View Relay "lilynetnrt1"

Family: 1 relay | noc@dayli.ly | AS401736 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 6288 bit/s Median
Stability
Not Overloaded | UP 5d 22h 44m ago | UP 96% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
6mo 1w 5d ago
BW Weight
0.00% of Network | 6 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.8 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 97.2% 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.
  • 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).
  • 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: WFU below threshold : WFU 97.2% 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
tyo1.daylily.network
23.142.212.252:9001
[2620:d7:6003::1]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS401736
AS Name
Project Daylily (BGP.tools)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 2/9 | HSDir: 1/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Meets (≥100 KB/s) 6.3 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 2.0d (2/9 DA above threshold)
Min/Max: 1.5d / 17492.7d (9/9 DA, Voting / Total Eligible)		 ≥22.0d - 54.1d (varies)
[Stricter] moria1: ≥405.3d
Uptime Below 5.9d (R) ≥9.3d - 10.0d (varies)
HSDir Prereq: Stable Below 2/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 8/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 97.4% (3/9 DA above threshold)
Min/Max: 96.8% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 12.3d (9/9 DA above threshold)
Min/Max: 9.6d / 108.4d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets 8/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 2/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 97.4% (3/9 DA above threshold)
Min/Max: 96.8% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 12.3d (9/9 DA above threshold)
Min/Max: 9.6d / 108.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 6.3 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

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

Last fetch was at Thu, 29 Jan 2026 16:45:35 GMT.

Nickname
lilynetnrt1
Fingerprint
4557D189B9D6AF5E68521F21E75A150BAB5304D1
AROI (?)
none
Contact
noc@dayli.ly
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
4557D189B9D6AF5E68521F21E75A150BAB5304D1
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
6.29 Mbit/s | 6.29 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
tyo1.daylily.network | 23.142.212.252:9001, [2620:d7:6003::1]:9001
Exit Address
none
Dir Address
none
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS401736 | Project Daylily (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
—/86.7%/85.5%/—
Uptime (1M/6M/1Y/5Y)
96.2%/87.8%/86.5%/0.0%
Uptime / Downtime
UP 5d 22h 44m ago
Seen (First | Last)
6mo 1w 5d ago (2025-07-21 02:00:00) | 1h 47m 7s ago (2026-01-29 15:00:00)
Last Restarted
5d 22h 45m ago (2026-01-23 18:01:16)
Last Changed Address or Port
2025-08-08 23:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status)
0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-29 16:15:07).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 2/9 | HSDir: 1/9 | Guard: 0/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 6288 bit/s | Min: 880 bit/s | Max: 6640 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.8 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 97.2% 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.
    • 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).
    • 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: WFU below threshold: WFU 97.2% 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.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 6288 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 97.4% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 12.3 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 6.3 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 5.9d ≥9.3d - 10.0d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 2 days ≥22.0d - 54.1d (typical)
[Stricter] moria1: ≥405.3d 		BELOW - 2/9
Fast Speed (Relay Reported) 6.3 Mbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 97.4% ≥98.0% (from all auths) BELOW - 1/9
HSDir TK (Dir. Auth., tk) 12.3 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 1/9
IPv6 Reachable (Dir. Auth.) 7/7 tested ≥4/7 (majority) REACHABLE

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 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 Y Yes Yes Running, Valid, V2Dir, Fast 6.3 Mbit/s | 816.0 Kbit/s 6.3 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 97.2% | 98% 11.8d | 8d 2.0d | 49.8d 5.9d | 10.2d 97.2% | 98.0% 11.8d | 1.0d 2026-01-29 12:18:36 6640 bit/s
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 6.3 Mbit/s | 816.0 Kbit/s 6.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.1% | 98% 12.2d | 8d 1.7d | 22.0d 5.9d | 10.0d 97.1% | 98.0% 12.2d | 1.0d 2026-01-29 12:18:36 6288 bit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast 6.3 Mbit/s | 816.0 Kbit/s 6.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 13.3d | 8d 3.5d | 34.7d 5.9d | 10.0d 98.7% | 98.0% 13.3d | 1.0d 2026-01-29 12:18:36 6288 bit/s
faravahar (US) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir 6.3 Mbit/s | 816.0 Kbit/s 6.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 108.4d | 8d 108.4d | 47.2d 5.9d | 9.3d 100.0% | 98.0% 108.4d | 1.0d 2026-01-29 12:18:36 6288 bit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 6.3 Mbit/s | 816.0 Kbit/s 6.3 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 12.3d | 8d 2.0d | 54.1d 5.9d | 10.0d 97.8% | 98.0% 12.3d | 1.0d 2026-01-29 12:18:36 1520 bit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast 6.3 Mbit/s | 816.0 Kbit/s 6.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.2% | 98% 13.2d | 8d 2.4d | 54.7d 5.9d | 9.6d 98.2% | 98.0% 13.2d | 1.0d 2026-01-29 12:18:36 6288 bit/s
maatuska (SE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 6.3 Mbit/s | 816.0 Kbit/s 6.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 96.8% | 98% 12.2d | 8d 1.5d | 54.9d 5.9d | 9.5d 96.8% | 98.0% 12.2d | 1.0d 2026-01-29 12:18:36 880 bit/s
moria1 (US) Yes Yes Y Yes Yes Running, Valid, V2Dir, Stable 6.3 Mbit/s | 8.4 Mbit/s 6.3 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 97.4% | 98% 9.6d | 8d 17492.7d | 405.3d 5.9d | 9.9d 97.4% | 98.0% 9.6d | 9.9d 2026-01-29 12:18:36 2720 bit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 6.3 Mbit/s | 816.0 Kbit/s 6.3 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 97.2% | 98% 13.0d | 8d 1.7d | 55.9d 5.9d | 10.8d 97.2% | 98.0% 13.0d | 1.0d 2026-01-29 12:18:36 2320 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). This is your relay's self-reported uptime from its 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.