View Relay "NadekoNet"

Fingerprint: B1FC3C405C1CDAED4B4E8EA5B7C814D6ECC7C6E7 | Family: 2 relays | tor (at) nadeko (dot) net | AS270013 | Chile | Linux

Health Status

Consensus
In Consensus (7/7 Directory Auths)
Flags
Running, Valid, Fast, Exit (4)
DNS Health
Healthy (11.2s, 3rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 67 Kbit/s Median
Stability
Not Overloaded | UP 2d 20h 2m ago | UP 97% (1M)
Reachability
IPv4: 7/7 | v6: 7/7 (Directory Auths)
First Seen
4mo 3w 6d ago
BW Weight
0.00% of Network | 170 Mbit/s Observed By Relay
Version
0.4.9.11 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 97.0% 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: 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
  • HSDir: WFU below threshold : WFU 97.0% 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.45:9001
[2803:29e0:10:953::1]:9001
Exit Address
151.242.242.45
Reachability (Directory Authorities)
IPv4
7/7
IPv6
7/7
Location
Country
Chile 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 (4): Running, Valid, Fast, Exit
Eligible Flags (5): Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 7/7 | Stable: 1/7 | HSDir: 0/7 | Guard: 0/7 | Exit: 7/7
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
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Meets (7/7 DA) 7/7 authorities assigned Valid Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir DirPort Available Below (0/7 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast Speed Meets (7/7 DA) 170.8 Mbit/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.7d (1/7 DA above threshold)
Min/Max: 3.6d / 15517.8d (7/7 DA, Voting / Total Eligible)		 ≥8.2d - 14.9d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9062.0d
Uptime Below (0/7 DA) 2.8d (R) ≥8.4d - 8.6d (varies) (≥4/7 DA)
HSDir Prereq: Fast Meets (7/7 DA) 7/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 (1/7 DA) 1/7 DA assigned Stable ≥8.2d - 14.9d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9062.0d
Prereq: V2Dir Below (0/7 DA) 0/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Below (0/7 DA) Median: 96.8% (0/7 DA above threshold)
Min/Max: 94.2% / 97.1% (7/7 DA, Voting / Total Eligible)		 ≥98.0% (≥4/7 DA)
Time Known Meets (7/7 DA) Median: 17.3d (7/7 DA above threshold)
Min/Max: 9.8d / 19.9d (7/7 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥4/7 DA)
[Stricter] moria1: ≥9.7d
Guard Prereq: Fast Meets (7/7 DA) 7/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 (1/7 DA) 1/7 DA assigned Stable ≥8.2d - 14.9d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9062.0d
Prereq: V2Dir Below (0/7 DA) 0/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Below (0/7 DA) Median: 96.8% (0/7 DA above threshold)
Min/Max: 94.2% / 97.1% (7/7 DA, Voting / Total Eligible)		 ≥98% (≥4/7 DA)
Time Known Meets (7/7 DA) Median: 17.3d (7/7 DA above threshold)
Min/Max: 9.8d / 19.9d (7/7 DA, Voting / Total Eligible)		 ≥8 days (≥4/7 DA)
Bandwidth Meets (7/7 DA) 170.8 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Meets (7/7 DA) Port 80: Yes | Port 443: Yes (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-07-20 00:00:25).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
170.82 Mbit/s
Advertised Bandwidth
125.83 Mbit/s
Rate Limit
125.83 Mbit/s
Burst Limit
167.77 Mbit/s
Total Data
103 TB (6 months)
1mo: 26 TB | 6mo: 103 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-20 00:00:25

Measured By
5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement
67.2 Kbit/s
Min / Max
30.4 Kbit/s / 80.0 Kbit/s
Deviation
49.6 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0039% of network (48th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0116% (43th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 20h 2m ago
Overall Uptime (1M/6M/1Y/5Y)
97.1%/99.3%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (97.1%/99.3%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
4mo 3w 6d ago (2026-02-22 20:00:00)
Last Seen
2h 2m 24s ago (2026-07-19 22:00:00)
Last Restarted
2d 20h 2m ago (2026-07-17 03:59:59)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-19 16:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
tor (at) nadeko (dot) net
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
7D69912249CBA7B8E2F3F1D3D3B0DFE55BA328D9
B1FC3C405C1CDAED4B4E8EA5B7C814D6ECC7C6E7 (this relay)
Alleged Members: 2
(they don't list you back) 
87A6FAEAFF324DDF43879EFD844C34E7C31A8D38
A6361A095847092ECFA24F5603DEB6F7CD56783B
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Healthy (avg. 11.2s, 3rd percentile)
Query Domain
c419bce998c7497c897e2a254aeb087c.b1fc3c40.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
2/2 instances succeeded
First Hop
F3Netze (DE) 50AA9FEA6A3A609686276C4CF0C2A1AFB2ECCA1B
Exit Address Used
151.242.242.45
Per-Instance Results
Cross Validation Attempt 1: Success, 14.2s (cv1_w3)
Cross Validation Attempt 2: Success, 8.3s (cv4_w3)
Tested: 2026-07-19 07:17:28 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  80
  443
  8443
  25565
IPv6 Exit Policy Summary
accept: 
  80
  443
  8443
  25565
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.45:*
accept *:80
accept *:443
accept *:8443
accept *:25565
reject *:*

Last fetch was at Mon, 20 Jul 2026 00:02:22 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-20 00:00:25).

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, Fast, Exit 170.8 Mbit/s | 816.0 Kbit/s 170.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.0% | 98% 19.9d | 8d 4.7d | 21.1d 2.8d | 8.4d 97.0% | 98.0% 19.9d | 1.0d 2026-07-19 10:01:03 80.0 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 170.8 Mbit/s | 816.0 Kbit/s 170.8 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 97.0% | 98% 19.9d | 8d 4.7d | 8.2d 2.8d | 8.6d 97.0% | 98.0% 19.9d | 1.0d 2026-07-19 10:01:03 67.2 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, Fast, Exit 170.8 Mbit/s | 816.0 Kbit/s 170.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.8% | 98% 17.3d | 8d 4.2d | 13.2d 2.8d | 8.6d 96.8% | 98.0% 17.3d | 1.0d 2026-07-19 10:01:03 80.0 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 170.8 Mbit/s | 816.0 Kbit/s 170.8 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 95.2% | 98% 16.0d | 8d 3.6d | 14.4d 2.8d | 8.6d 95.2% | 98.0% 16.0d | 1.0d 2026-07-19 10:01:03 30.4 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 170.8 Mbit/s | 816.0 Kbit/s 170.8 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 96.8% | 98% 17.2d | 8d 4.1d | 14.9d 2.8d | 8.6d 96.8% | 98.0% 17.2d | 1.0d 2026-07-19 10:01:03 32.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 170.8 Mbit/s | 8.4 Mbit/s 170.8 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 94.2% | 98% 9.8d | 8d 15517.8d | 9062.0d 2.8d | 8.6d 94.2% | 98.0% 9.8d | 9.7d 2026-07-19 10:01:03 73.6 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 170.8 Mbit/s | 816.0 Kbit/s 170.8 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 97.1% | 98% 19.8d | 8d 4.7d | 21.0d 2.8d | 8.6d 97.1% | 98.0% 19.8d | 1.0d 2026-07-19 10:01:03 60.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.