View Relay "imaddictedtoweed"

Fingerprint: 23633C338E05AD016D14010B8988D2CA6883B8F4 | Family: 2 relays | ContactInfo... | AS210558 | Netherlands | Linux

Health Status

Consensus
In Consensus (8/8 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (9.5s, 1st percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/5 BW Auths Measured 136 Kbit/s Median
Stability
Not Overloaded | UP 2d 3h 11m ago
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
5d 2h 15m ago
BW Weight
0.01% of Network | 96 Mbit/s Observed By Relay
Version
0.4.9.6 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 5.1 days is below 8 days requirement (2.9 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.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
tor.linke.pizza
45.92.1.70:443
Exit Address
45.92.1.70
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS210558
AS Name
1337 Services GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 5.80% consensus weight, 11 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (6): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 8/8 | Stable: 8/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 8/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/8 DA) 8/8 authorities reached relay ≥5/8 DA ORPort reachable
Valid Descriptor Meets (8/8 DA) 8/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (8/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 96.2 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/8 DA) Median: 5.1d (1/8 DA above threshold)
Min/Max: 5.0d / 20557.4d (8/8 DA, Voting / Total Eligible)		 ≥32.5d - 59.1d (varies) (≥5/8 DA)
[Stricter] moria1: ≥312.2d
Uptime Below (0/8 DA) 2.1d (R) ≥7.0d - 7.1d (varies) (≥5/8 DA)
HSDir Prereq: Fast Meets (8/8 DA) 8/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (8/8 DA) 8/8 DA assigned Stable ≥32.5d - 59.1d (varies) (≥5/8 DA)
[Stricter] moria1: ≥312.2d
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (7/8 DA) Majority: 100.0% (7/8 DA)
Min/Med/Max: 62.7% / 100.0% / 100.0% (8/8 DA, Voting / Total Eligible)		 ≥98.0% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 5.1d (0/8 DA above threshold)
Min/Max: 1.5d / 5.1d (8/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (8/8 DA) 8/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (8/8 DA) 8/8 DA assigned Stable ≥32.5d - 59.1d (varies) (≥5/8 DA)
[Stricter] moria1: ≥312.2d
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (7/8 DA) Majority: 100.0% (7/8 DA)
Min/Med/Max: 62.7% / 100.0% / 100.0% (8/8 DA, Voting / Total Eligible)		 ≥98% (≥5/8 DA)
Time Known Below (0/8 DA) (need 2.9 more days) Median: 5.1d (0/8 DA above threshold)
Min/Max: 1.5d / 5.1d (8/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Meets (8/8 DA) 96.2 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Meets (8/8 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-04-15 00:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
96.24 Mbit/s
Advertised Bandwidth
96.24 Mbit/s
Rate Limit
1.67 Gbit/s
Burst Limit
2.00 Gbit/s
Total Data
314 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-15 00:15:08

Measured By
5/5 Bandwidth Authorities
Median Measurement
136.0 Kbit/s
Min / Max
80.0 Kbit/s / 224.0 Kbit/s
Deviation
144.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0088% of network (61th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0265% (52th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 3h 11m 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
5d 2h 15m ago (2026-04-09 23:00:00)
Last Seen
7h 15m 56s ago (2026-04-14 18:00:00)
Last Restarted
2d 3h 11m ago (2026-04-12 22:04:00)
Last Changed Address
2026-04-12 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-14 17:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
ContactInfo mail:tor[at]linke[dort]pizza matrix:@tor:matrix.iloveblahaj.org btc:bc1pkahvz5yfk4tr66d4p5pv0tnv48fyup2jha4dw6ewl4z9f0dzeu5q395lj4 xmr:89kUjgJK1Bbamhq9h5t7v9EsS1gdUx9w5Z4ASpH1zWnQ5DUh2j3th9v5ZWjForcX3mFiU25tKK1gGJEbLXknhzuA1qTthr2
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
23633C338E05AD016D14010B8988D2CA6883B8F4 (this relay)
2554D8E61CF85B16F141C2073CFC545205BD0B77
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 9.5s, 1st percentile)
Query Domain
42ca1adbc04b4a6fad3a54448e0aae2b.23633c33.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
prsv (NL) 2687D8EFFD87C588956B9AC82781D2E8B1EC8327
Exit Address Used
45.92.1.70
Per-Instance Results
Cross Validation Attempt 1: Success, 8.7s (cv2_w1)
Cross Validation Attempt 2: Success, 11.5s (cv3_w1)
Cross Validation Attempt 3: Success, 8.4s (cv4_w1)
Tested: 2026-04-14 07:05:44 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  53
  80
  443
  9001
IPv6 Exit Policy Summary
accept: 
  53
  80
  443
  9001
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 45.92.1.70:*
accept *:53
accept *:80
accept *:443
accept *:9001
reject *:*

Last fetch was at Wed, 15 Apr 2026 01:15:55 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-15 00:15: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) No — — — N No — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, Exit 96.2 Mbit/s | 816.0 Kbit/s 96.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 32.5d 2.1d | 7.1d 100.0% | 98.0% 5.1d | 1.0d 2026-04-14 23:43:32 80.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, Exit 96.2 Mbit/s | 816.0 Kbit/s 96.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 41.6d 2.1d | 7.0d 100.0% | 98.0% 5.1d | 1.0d 2026-04-14 23:43:32 80.0 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, Exit 96.2 Mbit/s | 816.0 Kbit/s 96.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.0d | 8d 5.0d | 59.3d 2.1d | 7.1d 100.0% | 98.0% 5.0d | 1.0d 2026-04-14 23:43:32 80.0 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 96.2 Mbit/s | 816.0 Kbit/s 96.2 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.0d | 8d 5.0d | 59.1d 2.1d | 7.3d 100.0% | 98.0% 5.0d | 1.0d 2026-04-14 23:43:32 152.0 Kbit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 96.2 Mbit/s | 816.0 Kbit/s 96.2 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 59.0d 2.1d | 7.1d 100.0% | 98.0% 5.1d | 1.0d 2026-04-14 23:43:32 176.0 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 96.2 Mbit/s | 816.0 Kbit/s 96.2 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.1d | 8d 5.1d | 59.1d 2.1d | 7.0d 100.0% | 98.0% 5.1d | 1.0d 2026-04-14 23:43:32 224.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Valid, V2Dir, Fast, Stable, Exit 96.2 Mbit/s | 8.4 Mbit/s 96.2 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 62.7% | 98% 1.5d | 8d 20557.4d | 312.2d 2.1d | 8.0d 62.7% | 98.0% 1.5d | 9.8d 2026-04-14 10:05:27 120.0 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 96.2 Mbit/s | 816.0 Kbit/s 96.2 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.0d | 8d 5.0d | 59.3d 2.1d | 7.5d 100.0% | 98.0% 5.0d | 1.0d 2026-04-14 23:43:32 216.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.