View Relay "NadekoNet"
Fingerprint: 7D69912249CBA7B8E2F3F1D3D3B0DFE55BA328D9 |
Family: 4 relays
|
tor@nadeko.net |
AS214677
|
Netherlands
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (18.2s, 87th percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/6 BW Auths Measured 128 Kbit/s Median
- Stability
- Not Overloaded | UP 3d 15h 15m ago | UP 94% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8 (Directory Auths)
- BW Weight
- 0.02% of Network | 170 Mbit/s Observed By Relay
- Version
- 0.4.9.5 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.3% 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 becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-dir-server. You can check with:grep tunnelled-dir-server /var/lib/tor/cached-descriptors -
HSDir: WFU below threshold
: WFU 97.3% 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.
Addresses
- OR Address
-
95.135.208.24:9001
[2a12:bec4:1821:631::a]:9001 - Exit Address
- 95.135.208.24
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Netherlands
- Interactive Map
- View in RouteFluxMap
Eligible Flags (5):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/9
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 |
| 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) | 170.6 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: 4.4d (1/9 DA above threshold) Min/Max: 1.1d / 13482.6d (9/9 DA, Voting / Total Eligible) |
≥11.3d - 55.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥347.6d |
| Uptime | Below (0/9 DA) | 3.6d (R) | ≥12.0d - 14.4d (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 | Below (1/9 DA) | 1/9 DA assigned Stable | ≥11.3d - 55.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥347.6d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 97.2% (0/9 DA above threshold) Min/Max: 91.4% / 97.3% (9/9 DA, Voting / Total Eligible) |
≥98.0% (≥5/9 DA) | |
| Time Known | Meets (8/9 DA) | Median: 13.2d (9/9 DA above threshold) Min/Max: 9.7d / 13.7d (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 | Below (1/9 DA) | 1/9 DA assigned Stable | ≥11.3d - 55.7d (varies) (≥5/9 DA) [Stricter] moria1: ≥347.6d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 97.2% (0/9 DA above threshold) Min/Max: 91.4% / 97.3% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 13.2d (9/9 DA above threshold) Min/Max: 9.7d / 13.7d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 170.6 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-15 17:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 170.61 Mbit/s
- Advertised Bandwidth
- 125.83 Mbit/s
- Rate Limit
- 125.83 Mbit/s
- Burst Limit
- 167.77 Mbit/s
- Total Data
-
21 TB
(6 months)
1mo: 18 TB | 6mo: 21 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-03-15 17:45:06
- Measured By
-
5/6
Bandwidth Authorities
Not measured by: longclaw - Median Measurement
- 128.0 Kbit/s
- Min / Max
- 80.0 Kbit/s / 328.0 Kbit/s
- Deviation
- 248.0 Kbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0152% of network
(74th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0457% (70th pctl)
Uptime Metrics
- Current Status
- UP 3d 15h 15m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 94.9%/93.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (94.9%/93.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 1mo 2w 1d ago (2026-01-29 01:00:00)
- Last Seen
- 1h 15m 37s ago (2026-03-15 17:00:00)
- Last Restarted
- 3d 15h 15m ago (2026-03-12 03:00:00)
- Last Changed Address
- 2026-01-29 01:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-03-15 10:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- tor@nadeko.net
Family Configuration
- Family Support
- MyFamily Only (4) — Legacy only. Consider migrating to Happy Families. | View Full Family (4)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 4
7D69912249CBA7B8E2F3F1D3D3B0DFE55BA328D9 (this relay) 87A6FAEAFF324DDF43879EFD844C34E7C31A8D38 A6361A095847092ECFA24F5603DEB6F7CD56783B B1FC3C405C1CDAED4B4E8EA5B7C814D6ECC7C6E7
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
- Status
- Healthy (avg. 18.2s, 87th percentile)
- Query Domain
25b44eb3a04f473bb59fe75f319dff41.7d699122.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Cross-Validation
- 3/3 instances succeeded
- First Hop
- bauruine (NO) 7A59487693C59EEF4CF4D49BF0C820064EE91730
- Exit Address Used
95.135.208.24- Per-Instance Results
-
Cross Validation Attempt 1: Success, 14.8s (cv1_w2) Cross Validation Attempt 2: Success, 21.7s (cv2_w2) Cross Validation Attempt 3: Success, 18.1s (cv4_w2)
Tested: 2026-03-15 07:12:41 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 80 443 8443 25565
IPv6 Exit Policy Summary
NoneFull 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 95.135.208.24:* accept *:80 accept *:443 accept *:8443 accept *:25565 reject *:*
Last fetch was at Sun, 15 Mar 2026 18:15:37 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-03-15 17:45:06).
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.6 Mbit/s | 816.0 Kbit/s | 170.6 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s | 97.3% | 98% | 13.2d | 8d | 4.4d | 59.7d | 3.6d | 13.6d | 97.3% | 98.0% | 13.2d | 1.0d | 2026-03-14 09:14:02 | 128.0 Kbit/s |
| dannenberg (DE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, Fast, Exit | 170.6 Mbit/s | 816.0 Kbit/s | 170.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 97.2% | 98% | 13.1d | 8d | 4.4d | 11.3d | 3.6d | 14.3d | 97.2% | 98.0% | 13.1d | 1.0d | 2026-03-14 09:14:02 | 80.0 Kbit/s |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, Fast, Exit | 170.6 Mbit/s | 816.0 Kbit/s | 170.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 97.3% | 98% | 13.2d | 8d | 4.4d | 45.8d | 3.6d | 12.0d | 97.3% | 98.0% | 13.2d | 1.0d | 2026-03-14 09:14:02 | 80.0 Kbit/s |
| faravahar (US) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, Fast, Exit | 170.6 Mbit/s | 816.0 Kbit/s | 170.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 97.3% | 98% | 13.7d | 8d | 4.5d | 55.1d | 3.6d | 14.5d | 97.3% | 98.0% | 13.7d | 1.0d | 2026-03-14 09:14:02 | 80.0 Kbit/s |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Exit | 170.6 Mbit/s | 816.0 Kbit/s | 170.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s | 97.2% | 98% | 13.2d | 8d | 4.4d | 61.4d | 3.6d | 14.4d | 97.2% | 98.0% | 13.2d | 1.0d | 2026-03-14 09:14:02 | 240.0 Kbit/s |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | — | Running, Valid, Fast, Exit | 170.6 Mbit/s | 816.0 Kbit/s | 170.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 97.1% | 98% | 12.2d | 8d | 4.0d | 62.0d | 3.6d | 14.5d | 97.1% | 98.0% | 12.2d | 1.0d | 2026-03-14 09:14:02 | 80.0 Kbit/s |
| maatuska (SE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Exit | 170.6 Mbit/s | 816.0 Kbit/s | 170.6 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s | 91.4% | 98% | 12.6d | 8d | 1.1d | 40.2d | 3.6d | 14.3d | 91.4% | 98.0% | 12.6d | 1.0d | 2026-03-14 09:14:02 | 328.0 Kbit/s |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Stable, Exit | 170.6 Mbit/s | 8.4 Mbit/s | 170.6 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s | 96.2% | 98% | 9.7d | 8d | 13482.6d | 347.6d | 3.6d | 15.5d | 96.2% | 98.0% | 9.7d | 9.8d | 2026-03-14 09:14:02 | 152.0 Kbit/s |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, Fast, Exit | 170.6 Mbit/s | 816.0 Kbit/s | 170.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s | 97.3% | 98% | 13.5d | 8d | 4.5d | 55.7d | 3.6d | 14.5d | 97.3% | 98.0% | 13.5d | 1.0d | 2026-03-14 09:14:02 | 256.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.
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.
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.