View Relay "kn3mg8ct7g"
Fingerprint: 443AD353E27DDD8EE338413069DA7D721EAC751C |
Family: 1 relay
|
AS149440
|
United States of America
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (18.0s, 85th percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 6/7 BW Auths Measured 8 bit/s Median
- Stability
- Not Overloaded | UP 2d 3h 43m ago
- Reachability
- IPv4: 9/9 (Directory Auths)
- BW Weight
- 0.00% of Network | 5 Mbit/s Observed By Relay
- Version
- 0.4.9.17 Recommended
Issues Detected:
-
Guard: requires Fast flag
: Guard flag requires having the Fast flag first
Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily. -
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: bandwidth below threshold
: Observed bandwidth 6 Mbit/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: Time Known below threshold
: Time Known 2.0 days is below 8 days requirement (6.0 more days needed)
Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably. -
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 Fast flag
: HSDir flag requires having the Fast flag first
Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily. -
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 -
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
-
23-27-169-42.ip.evoxt.io
23.27.169.42:9001 - Exit Address
- 23.27.169.42
Reachability (Directory Authorities)
- IPv4
- 9/9
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 0/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 |
| 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) | 5.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 (0/9 DA) | Median: 2.1d (0/9 DA above threshold) Min/Max: 2.0d / 2.1d (9/9 DA, Voting / Total Eligible) |
≥2.7d - 8.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥11610.2d |
| Uptime | Below (0/9 DA) | 2.2d (R) | ≥6.2d - 6.2d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (3/9 DA) | 3/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 (0/9 DA) | 0/9 DA assigned Stable | ≥2.7d - 8.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥11610.2d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (9/9 DA) | Majority: 100.0% (9/9 DA) | ≥98.0% (≥5/9 DA) | |
| Time Known | Meets (8/9 DA) | Median: 2.1d (0/9 DA above threshold) Min/Max: 1.8d / 2.1d (9/9 DA, Voting / Total Eligible) |
≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.4d |
|
| Guard | Prereq: Fast | Below (3/9 DA) | 3/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 (0/9 DA) | 0/9 DA assigned Stable | ≥2.7d - 8.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥11610.2d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (9/9 DA) | Majority: 100.0% (9/9 DA) | ≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) (need 5.9 more days) | Median: 2.1d (0/9 DA above threshold) Min/Max: 1.8d / 2.1d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 5.6 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.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-11-22 12:00:48).
Capacity (Relay Reported)
- Observed Bandwidth
- 5.56 Mbit/s
- Advertised Bandwidth
- 5.24 Mbit/s
- Rate Limit
- 5.24 Mbit/s
- Burst Limit
- 10.49 Mbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-22 12:00:48
- Measured By
-
6/7
Bandwidth Authorities
Not measured by: faravahar - Median Measurement
- 8 bit/s
- Min / Max
- 8 bit/s / 5240 bit/s
- Deviation
- 5232 bit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0000% of network
(0th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0000% (0th pctl)
Uptime Metrics
- Current Status
- UP 2d 3h 43m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 0.0%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 2d 3h 2m ago (2026-11-20 10:00:00)
- Last Seen
- 2h 2m 32s ago (2026-11-22 11:00:00)
- Last Restarted
- 2d 3h 43m ago (2026-11-20 09:19:11)
- Last Changed Address
- 2026-11-20 10:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-11-22 05:00 UTC
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
443AD353E27DDD8EE338413069DA7D721EAC751C (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
- Status
- Healthy (avg. 18.0s, 85th percentile)
- Query Domain
0ddb29739b464f03924f8b0bf87608b2.443ad353.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Cross-Validation
- 4/4 instances succeeded
- First Hop
- DFRI51 (SE) F7AD55D44B10C13BDA43BE6578FC65C00FC07575
- Exit Address Used
23.27.169.42- Per-Instance Results
-
Cross Validation Attempt 1: Success, 15.0s (cv1_w1) Cross Validation Attempt 2: Success, 25.7s (cv2_w1) Cross Validation Attempt 3: Success, 19.3s (cv3_w1) Cross Validation Attempt 4: Success, 11.9s (cv4_w1)
Tested: 2026-11-22 08:05:48 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 21 25 110 143 465 587 993 995 1214 6346-6429 6881-6999 51413
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 23.27.169.42:* reject *:21 reject *:25 reject *:465 reject *:587 reject *:110 reject *:995 reject *:143 reject *:993 reject *:1214 reject *:6346-6429 reject *:6881-6999 reject *:51413 accept *:*
Last fetch was at Sun, 22 Nov 2026 13:02:10 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-22 12:00:48).
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 | 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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| E30CF7B3 | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Exit | 5.6 Mbit/s | 816.0 Kbit/s | 5.6 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 2.0d | 7d | 2.0d | 5.3d | 2.2d | 6.2d | 100.0% | 98.0% | 2.0d | 1.0d | 2026-11-21 21:19:48 | 8 bit/s |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Exit | 5.6 Mbit/s | 816.0 Kbit/s | 5.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 2.1d | 8d | 2.1d | 9.0d | 2.2d | 6.2d | 100.0% | 98.0% | 2.1d | 1.0d | 2026-11-21 21:19:48 | 8 bit/s |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Running, Valid, Fast, Exit | 5.6 Mbit/s | 816.0 Kbit/s | 5.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 2.1d | 8d | 2.1d | 7.6d | 2.2d | 6.2d | 100.0% | 98.0% | 2.1d | 1.0d | 2026-11-21 21:19:48 | 5240 bit/s |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Fast, Exit | 5.6 Mbit/s | 816.0 Kbit/s | 5.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 2.1d | 8d | 2.1d | 7.9d | 2.2d | 6.2d | 100.0% | 98.0% | 2.1d | 1.0d | 2026-11-21 21:19:48 | 5240 bit/s |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Exit | 5.6 Mbit/s | 816.0 Kbit/s | 5.6 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 2.1d | 8d | 2.1d | 9.0d | 2.2d | 6.2d | 100.0% | 98.0% | 2.1d | 1.0d | 2026-11-21 21:19:48 | 8 bit/s |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Exit | 5.6 Mbit/s | 816.0 Kbit/s | 5.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 2.1d | 8d | 2.1d | 9.9d | 2.2d | 6.2d | 100.0% | 98.0% | 2.1d | 1.0d | 2026-11-21 21:19:48 | 8 bit/s |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Running, Valid, Fast, Exit | 5.6 Mbit/s | 816.0 Kbit/s | 5.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 2.1d | 8d | 2.1d | 2.7d | 2.2d | 6.2d | 100.0% | 98.0% | 2.1d | 1.0d | 2026-11-21 21:19:48 | 5240 bit/s |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Exit | 5.6 Mbit/s | 8.4 Mbit/s | 5.6 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 1.8d | 8d | 2.1d | 11610.2d | 2.2d | 6.2d | 100.0% | 98.0% | 1.8d | 9.4d | 2026-11-21 21:19:48 | 8 bit/s |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, Exit | 5.6 Mbit/s | 816.0 Kbit/s | 5.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 2.1d | 8d | 2.1d | 8.9d | 2.2d | 6.2d | 100.0% | 98.0% | 2.1d | 1.0d | 2026-11-21 21:19:48 | 8 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.
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.