Tor Relays :: NadekoNet

View Relay "NadekoNet"

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

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Fast, Stable, Exit (5)
DNS Health: Healthy (15.8s, 43rd percentile) (via exitdnshealth.1aeo.com)
BW Verified: 5/7 BW Auths Measured 49 Kbit/s Median
Stability: Not Overloaded | UP 1w 5d 23h ago | UP 99% (1M)

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 4mo 1w 3d ago
BW Weight: 0.00% of Network | 86 Mbit/s Observed By Relay
Version: 0.4.9.8 Recommended

Issues Detected:

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.

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: 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, Fast, Stable, 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	Below (0/9 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Meets (9/9 DA)	86.4 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 (2/9 DA)	Median: 26.3d (1/9 DA above threshold) Min/Max: 14.7d / 4314.5d (9/9 DA, Voting / Total Eligible)	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
Stable	Uptime	Meets (9/9 DA)	13.0d (R)	≥4.3d - 5.2d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/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	Meets (9/9 DA)	9/9 DA assigned Stable	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (8/9 DA)	Median: 99.9% (8/9 DA above threshold) Min/Max: 96.8% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 33.2d (9/9 DA above threshold) Min/Max: 9.9d / 37.3d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (9/9 DA)	9/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	Meets (9/9 DA)	9/9 DA assigned Stable	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (8/9 DA)	Median: 99.9% (8/9 DA above threshold) Min/Max: 96.8% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 33.2d (9/9 DA above threshold) Min/Max: 9.9d / 37.3d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	86.4 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-07-03 03:02:32).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 86.38 Mbit/s
Advertised Bandwidth: 86.38 Mbit/s
Rate Limit: 125.83 Mbit/s
Burst Limit: 167.77 Mbit/s
Total Data: 89 TB (6 months)
1mo: 25 TB | 6mo: 89 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-03 03:02:32

Measured By: 5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement: 49.6 Kbit/s
Min / Max: 17.6 Kbit/s / 80.0 Kbit/s
Deviation: 62.4 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0026% of network (35th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0083% (17th pctl)

Uptime and Stability

Uptime Metrics

Current Status: UP 1w 5d 23h ago
Overall Uptime (1M/6M/1Y/5Y): 99.9%/99.8%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (99.9%/99.8%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 4mo 1w 3d ago (2026-02-22 20:00:00)
Last Seen: 2h 11m 25s ago (2026-07-03 01:00:00)
Last Restarted: 1w 5d 23h ago (2026-06-20 03:59:59)
Last Changed Address: 2026-04-06 23:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Software and Version

Platform: Linux — Tor 0.4.9.8 on Linux
Version: 0.4.9.8 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Status

Healthy (avg. 15.8s, 43rd percentile)

Query Domain

ea2c77d53302480182290408059dc51e.b1fc3c40.tor.exit.validator.1aeo.com

DNS Result

Resolved to 64.65.4.1

Cross-Validation

4/4 instances succeeded

First Hop

ForPrivacyNET (DE) 547B98B764B0CC7EE454DF1BEE517D2C50B6223B

Exit Address Used

151.242.242.45

Per-Instance Results

Cross Validation Attempt 1:	Success, 17.3s	(cv1_w3)
Cross Validation Attempt 2:	Success, 21.0s	(cv2_w3)
Cross Validation Attempt 3:	Success, 10.0s	(cv3_w3)
Cross Validation Attempt 4:	Success, 15.0s	(cv4_w3)

Tested: 2026-07-02 19:15:46 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 Fri, 03 Jul 2026 03:11:23 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-03 03:02:32).

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, Stable, Exit	86.4 Mbit/s \| 816.0 Kbit/s	86.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	33.2d \| 8d	26.3d \| 48.4d	13.0d \| 5.1d	100.0% \| 98.0%	33.2d \| 1.0d	2026-07-02 22:14:21	80.0 Kbit/s
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, Fast, Stable, Exit	86.4 Mbit/s \| 816.0 Kbit/s	86.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	33.2d \| 8d	26.3d \| 10.1d	13.0d \| 5.2d	100.0% \| 98.0%	33.2d \| 1.0d	2026-07-02 22:14:21	80.0 Kbit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Yes	Running, Valid, Fast, Stable, Exit	86.4 Mbit/s \| 816.0 Kbit/s	86.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	23.4d \| 8d	18.4d \| 25.9d	13.0d \| 5.2d	99.9% \| 98.0%	23.4d \| 1.0d	2026-07-02 22:14:21	80.0 Kbit/s
faravahar (US)	Yes	Yes	Yes	—	N	Yes	Yes	Running, Valid, Fast, Stable, Exit	86.4 Mbit/s \| 816.0 Kbit/s	86.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	96.8% \| 98%	33.1d \| 8d	14.7d \| 28.4d	13.0d \| 5.2d	96.8% \| 98.0%	33.1d \| 1.0d	2026-07-02 22:14:21	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, Fast, Stable, Exit	86.4 Mbit/s \| 816.0 Kbit/s	86.4 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	37.3d \| 8d	27.4d \| 60.1d	13.0d \| 4.3d	99.9% \| 98.0%	37.3d \| 1.0d	2026-06-29 22:14:16	40.0 Kbit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	—	Running, Valid, Fast, Stable, Exit	86.4 Mbit/s \| 816.0 Kbit/s	86.4 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	33.9d \| 8d	26.5d \| 57.2d	13.0d \| 5.4d	100.0% \| 98.0%	33.9d \| 1.0d	2026-07-02 22:14:21	41.6 Kbit/s
maatuska (SE)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, Fast, Stable, Exit	86.4 Mbit/s \| 816.0 Kbit/s	86.4 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	22.5d \| 8d	17.4d \| 30.6d	13.0d \| 5.3d	99.9% \| 98.0%	22.5d \| 1.0d	2026-07-02 22:14:21	17.6 Kbit/s
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, Fast, Stable, Exit	86.4 Mbit/s \| 8.4 Mbit/s	86.4 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	99.8% \| 98%	9.9d \| 8d	4314.5d \| 1364.1d	13.0d \| 5.4d	99.8% \| 98.0%	9.9d \| 9.8d	2026-07-02 22:14:21	49.6 Kbit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Yes	Running, Valid, Fast, Stable, Exit	86.4 Mbit/s \| 816.0 Kbit/s	86.4 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	34.1d \| 8d	26.7d \| 53.1d	13.0d \| 5.4d	100.0% \| 98.0%	34.1d \| 1.0d	2026-07-02 22:14:21	38.4 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.

View Relay "NadekoNet"

Fingerprint: `B1FC3C405C1CDAED4B4E8EA5B7C814D6ECC7C6E7` | Family: 3 relays | tor (at) nadeko (dot) net | 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 "NadekoNet"

Fingerprint: B1FC3C405C1CDAED4B4E8EA5B7C814D6ECC7C6E7 | Family: 3 relays | tor (at) nadeko (dot) net | 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: `B1FC3C405C1CDAED4B4E8EA5B7C814D6ECC7C6E7` | Family: 3 relays | tor (at) nadeko (dot) net | AS270013 | Chile | Linux