View Relay "noack12i0"

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

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
BW Verified
5/6 BW Auths Measured 8 bit/s Median
Stability
Not Overloaded | UP 14h 25m 2s ago | UP 1% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
1y 4w 1d ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.8.19 Not 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: Time Known below threshold : Time Known 0.5 days is below 8 days requirement (7.5 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: Time Known below threshold : Time Known 11.0 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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:443
[2a0c:5700:3133:4000:be24:11ff:fe51:a829]:443
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
Legendary (score: 4/5, 0.06% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/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 Below (0/9 DA) 8 bit/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: 0.5d (0/9 DA above threshold)
Min/Max: 0.5d / 0.5d (9/9 DA, Voting / Total Eligible)		 ≥15.6d - 51.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥468.1d
Uptime Below (0/9 DA) 0.6d (R) ≥7.5d - 9.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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 ≥15.6d - 51.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥468.1d
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 Below (0/9 DA) Median: 0.5d (0/9 DA above threshold)
Min/Max: 0.5d / 0.5d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (0/9 DA) 0/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 ≥15.6d - 51.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥468.1d
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 7.5 more days) Median: 0.5d (0/9 DA above threshold)
Min/Max: 0.5d / 0.5d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8 bit/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-03 14:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
8.59 Gbit/s
Burst Limit
10.74 Gbit/s
Total Data
320 TB (1 year)
1mo: 34 TB | 6mo: 220 TB | 1y: 320 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-03 14:45:07

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
8 bit/s
Min / Max
0 bit/s / 8 bit/s
Deviation
8 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 and Stability

Uptime Metrics
Current Status
UP 14h 25m 2s ago
Overall Uptime (1M/6M/1Y/5Y)
1.5%/30.2%/65.7%/68.6%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (1.5%/30.2%/65.7%/68.6%)
Hibernating
No
Timestamps
First Seen
1y 4w 1d ago (2025-02-01 23:00:00)
Last Seen
1h 15m 40s ago (2026-03-03 14:00:00)
Last Restarted
14h 25m 2s ago (2026-03-03 00:50:38)
Last Changed Address
2025-02-01 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-03 06: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 
83FCF76FD9BA070BDB23B2C49FCE650D992DDEAC (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 Policy

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 Tue, 03 Mar 2026 15:15:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-03 14:45: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, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 53.9d 0.6d | 8.9d 100.0% | 98.0% 0.5d | 1.0d 2026-03-03 00:51:05 8 bit/s
dannenberg (DE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 15.6d 0.6d | 7.8d 100.0% | 98.0% 0.5d | 1.0d 2026-03-03 00:51:05 —
dizum (NL) Yes Yes Yes — N Yes — Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 42.0d 0.6d | 7.5d 100.0% | 98.0% 0.5d | 1.0d 2026-03-03 00:51:05 —
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 47.7d 0.6d | 9.2d 100.0% | 98.0% 0.5d | 1.0d 2026-03-03 00:51:05 —
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 55.2d 0.6d | 9.2d 100.0% | 98.0% 0.5d | 1.0d 2026-03-03 00:51:05 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 58.4d 0.6d | 9.2d 100.0% | 98.0% 0.5d | 1.0d 2026-03-03 00:51:05 —
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 36.7d 0.6d | 9.2d 100.0% | 98.0% 0.5d | 1.0d 2026-03-03 00:51:05 8 bit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 468.1d 0.6d | 10.0d 100.0% | 98.0% 0.5d | 9.8d 2026-03-03 00:51:05 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 51.1d 0.6d | 9.2d 100.0% | 98.0% 0.5d | 1.0d 2026-03-03 00:51:05 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.
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.