View Relay "noack12i1"

Fingerprint: BC8E6EEBD86DAE41D142FF56DA90398558E76479 | Family: 1 relay | mikael[]datanerd.se | AS30893 | Sweden | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (18.1s, 90th percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/6 BW Auths Measured 80 Kbit/s Median
Stability
Not Overloaded | UP 2d 22h 25m ago | UP 9% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
1y 1mo 2d ago
BW Weight
0.01% of Network | 102 Mbit/s Observed By Relay
Version
0.4.8.19 Not 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: Time Known below threshold : Time Known 2.4 days is below 8 days requirement (5.6 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 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.
  • 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.
  • Tor version not recommended : Running Tor version 0.4.8.19 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Connectivity and Location

Addresses
OR Address
tor-12.no-ack.net
195.47.238.176:993
[2a0c:5700:3133:4000:be24:11ff:fe51:a829]:993
Exit Address
195.47.238.176
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Sweden Sweden
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS30893
AS Name
No ACK Group Holding AB (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.10% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/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
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 102.1 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.4d (0/9 DA above threshold)
Min/Max: 2.4d / 2.4d (9/9 DA, Voting / Total Eligible)		 ≥13.8d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥476.5d
Uptime Below (0/9 DA) 2.9d (R) ≥9.1d - 9.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (7/9 DA) 7/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 ≥13.8d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥476.5d
Prereq: V2Dir Meets (9/9 DA) 9/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.4d (0/9 DA above threshold)
Min/Max: 2.2d / 2.4d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (7/9 DA) 7/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 ≥13.8d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥476.5d
Prereq: V2Dir Meets (9/9 DA) 9/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.6 more days) Median: 2.4d (0/9 DA above threshold)
Min/Max: 2.2d / 2.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 102.1 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-03-05 22:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
102.13 Mbit/s
Advertised Bandwidth
102.13 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
10.74 Gbit/s
Total Data
318 TB (5 years)
1mo: 5.0 GB | 6mo: 65 TB | 1y: 277 TB | 5y: 318 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-05 22:15:07

Measured By
4/6 Bandwidth Authorities
Not measured by: longclaw, tor26
Median Measurement
80.0 Kbit/s
Min / Max
8 bit/s / 344.0 Kbit/s
Deviation
344.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0063% of network (54th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0188% (38th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 22h 25m ago
Overall Uptime (1M/6M/1Y/5Y)
9.8%/30.2%/65.4%/68.6%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (9.8%/30.2%/65.4%/68.6%)
Hibernating
No
Timestamps
First Seen
1y 1mo 2d ago (2025-02-01 23:00:00)
Last Seen
2h 15m 44s ago (2026-03-05 21:00:00)
Last Restarted
2d 22h 25m ago (2026-03-03 00:50:13)
Last Changed Address
2025-02-03 11:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-05 14:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
mikael[]datanerd.se
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
BC8E6EEBD86DAE41D142FF56DA90398558E76479 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.8.19 on Linux
Version
0.4.8.19 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Status
Healthy (avg. 18.1s, 90th percentile)
Query Domain
e81a151da9a64dcd909dfbe9cc0ea7ab.bc8e6eeb.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
prsv (FR) 4134CDC6B5AEFDE875FA1212DA380201D9BFA286
Exit Address Used
195.47.238.176
Per-Instance Results
Cross Validation Attempt 1: Success, 17.6s (cv1_w3)
Cross Validation Attempt 2: Success, 18.7s (cv2_w3)
Cross Validation Attempt 3: Success, 17.5s (cv3_w3)
Cross Validation Attempt 4: Success, 18.4s (cv4_w3)
Tested: 2026-03-05 20:16:32 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  22
  25
  465
  587
  2525
IPv6 Exit Policy Summary
reject: 
  22
  25
  465
  587
  2525
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 195.47.238.176:*
reject *:22
reject *:25
reject *:465
reject *:587
reject *:2525
accept *:*

Last fetch was at Thu, 05 Mar 2026 23:15:42 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-05 22:15:07).

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, V2Dir, Fast, Exit 102.1 Mbit/s | 816.0 Kbit/s 102.1 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 54.1d 2.9d | 9.3d 100.0% | 98.0% 2.4d | 1.0d 2026-03-04 18:49:28 104.0 Kbit/s
dannenberg (DE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 102.1 Mbit/s | 816.0 Kbit/s 102.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 13.8d 2.9d | 9.7d 100.0% | 98.0% 2.4d | 1.0d 2026-03-04 18:49:28 80.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes — Running, Valid, V2Dir, Fast, Exit 102.1 Mbit/s | 816.0 Kbit/s 102.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 42.7d 2.9d | 9.1d 100.0% | 98.0% 2.4d | 1.0d 2026-03-04 18:49:28 80.0 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 102.1 Mbit/s | 816.0 Kbit/s 102.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 48.5d 2.9d | 9.8d 100.0% | 98.0% 2.4d | 1.0d 2026-03-04 18:49:28 80.0 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 102.1 Mbit/s | 816.0 Kbit/s 102.1 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 56.1d 2.9d | 9.8d 100.0% | 98.0% 2.4d | 1.0d 2026-03-04 18:49:28 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit 102.1 Mbit/s | 816.0 Kbit/s 102.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 59.6d 2.9d | 9.9d 100.0% | 98.0% 2.4d | 1.0d 2026-03-04 18:49:28 80.0 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 102.1 Mbit/s | 816.0 Kbit/s 102.1 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 36.4d 2.9d | 9.8d 100.0% | 98.0% 2.4d | 1.0d 2026-03-04 18:49:28 344.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 102.1 Mbit/s | 8.4 Mbit/s 102.1 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.4d | 476.5d 2.9d | 11.2d 100.0% | 98.0% 2.2d | 9.8d 2026-03-04 18:49:28 120.0 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 102.1 Mbit/s | 816.0 Kbit/s 102.1 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 51.7d 2.9d | 9.8d 100.0% | 98.0% 2.4d | 1.0d 2026-03-04 18:49:28 80.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.