View Relay "ageinghacker"

Fingerprint: 26AD3C1C18F1CD2B357A33FA7652A906DB13A8CC | Family: 1 relay | Luca Saiu <positron AT gnu dot org> | AS50613 | Iceland | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
6/6 BW Auths Measured 224 bit/s Median
Stability
Not Overloaded | UP 3w 4d 1h ago | UP 81% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
9y 6mo 3w ago
BW Weight
0.00% of Network | 600 Kbit/s Observed By Relay
Version
0.4.8.21 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 0.1 MB/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: WFU below threshold : Weighted Fractional Uptime 85.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 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: WFU below threshold : WFU 85.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.

Connectivity and Location

Addresses
OR Address
tor-and-gnunet-readme.ageinghacker.net
82.221.139.190:9001
Exit Address
82.221.139.190
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Iceland Iceland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS50613
AS Name
Advania Island ehf (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% 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: 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
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) 600.1 Kbit/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: 0.4d (1/9 DA above threshold)
Min/Max: 0.4d / 19700.8d (9/9 DA, Voting / Total Eligible)		 ≥17.9d - 58.6d (varies) (≥5/9 DA)
Uptime Meets (9/9 DA) 25.1d (R) ≥3.3d - 3.4d (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 (1/9 DA) 1/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 85.7% (0/9 DA above threshold)
Min/Max: 83.9% / 89.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 12.5d (9/9 DA above threshold)
Min/Max: 9.8d / 12.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
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 (1/9 DA) 1/9 DA assigned Stable ≥17.9d - 58.6d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 85.7% (0/9 DA above threshold)
Min/Max: 83.9% / 89.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.5d (9/9 DA above threshold)
Min/Max: 9.8d / 12.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 600.1 Kbit/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-29 09:45:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
600.14 Kbit/s
Advertised Bandwidth
368.64 Kbit/s
Rate Limit
368.64 Kbit/s
Burst Limit
614.40 Kbit/s
Total Data
3.4 TB (5 years)
1mo: 71 GB | 6mo: 452 GB | 1y: 1.1 TB | 5y: 3.4 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 09:45:08

Measured By
6/6 Bandwidth Authorities
Median Measurement
224 bit/s
Min / Max
8 bit/s / 368 bit/s
Deviation
360 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 3w 4d 1h ago
Overall Uptime (1M/6M/1Y/5Y)
81.5%/74.1%/87.0%/87.7%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (81.5%/74.1%/87.0%/87.7%)
Hibernating
No
Timestamps
First Seen
9y 6mo 3w ago (2016-09-11 00:00:00)
Last Seen
2h 46m 39s ago (2026-03-29 08:00:00)
Last Restarted
3w 4d 1h ago (2026-03-04 09:26:26)
Last Changed Address
2024-01-29 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-29 02:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Luca Saiu <positron AT gnu dot org>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
26AD3C1C18F1CD2B357A33FA7652A906DB13A8CC (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.8.21 on Linux
Version
0.4.8.21 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
IPv6 Exit Policy Summary
None
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 82.221.139.190:*
reject 82.221.139.216:*
reject *:25
accept *:*

Last fetch was at Sun, 29 Mar 2026 10:46:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 09:45:08).

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 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 Running, Valid, V2Dir, Exit 600.1 Kbit/s | 816.0 Kbit/s 600.1 Kbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 85.3% | 98% 12.6d | 8d 0.4d | 63.4d 25.1d | 3.3d 85.3% | 98.0% 12.6d | 1.0d 2026-03-28 23:58:08 344 bit/s
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Exit 600.1 Kbit/s | 816.0 Kbit/s 600.1 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 87.2% | 98% 12.0d | 8d 0.4d | 17.9d 25.1d | 3.3d 87.2% | 98.0% 12.0d | 1.0d 2026-03-28 23:58:08 368 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Exit 600.1 Kbit/s | 816.0 Kbit/s 600.1 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 85.3% | 98% 11.7d | 8d 0.4d | 42.9d 25.1d | 3.4d 85.3% | 98.0% 11.7d | 1.0d 2026-03-28 23:58:08 368 bit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Exit 600.1 Kbit/s | 816.0 Kbit/s 600.1 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 85.7% | 98% 12.5d | 8d 0.4d | 56.4d 25.1d | 3.4d 85.7% | 98.0% 12.5d | 1.0d 2026-03-28 23:58:08 368 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 600.1 Kbit/s | 816.0 Kbit/s 600.1 Kbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 89.0% | 98% 12.7d | 8d 0.5d | 62.1d 25.1d | 3.4d 89.0% | 98.0% 12.7d | 1.0d 2026-03-28 23:58:08 144 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 600.1 Kbit/s | 816.0 Kbit/s 600.1 Kbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 85.6% | 98% 12.1d | 8d 0.4d | 62.6d 25.1d | 3.3d 85.6% | 98.0% 12.1d | 1.0d 2026-03-28 23:58:08 8 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 600.1 Kbit/s | 816.0 Kbit/s 600.1 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 86.1% | 98% 12.7d | 8d 0.4d | 50.7d 25.1d | 3.3d 86.1% | 98.0% 12.7d | 1.0d 2026-03-28 23:58:08 208 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 600.1 Kbit/s | 8.4 Mbit/s 600.1 Kbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 83.9% | 98% 9.8d | 8d 19700.8d | 291.4d 25.1d | 4.1d 83.9% | 98.0% 9.8d | 9.9d 2026-03-28 23:58:08 224 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 600.1 Kbit/s | 816.0 Kbit/s 600.1 Kbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 87.3% | 98% 12.5d | 8d 0.4d | 58.6d 25.1d | 3.9d 87.3% | 98.0% 12.5d | 1.0d 2026-03-28 23:58:08 136 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.