View Relay "Killix"

Fingerprint: 5B26E959ED27C3C592EE5FFE13EBC823522F42F4 | Family: 1 relay | tor@kllx.eu | AS16276 | Poland | Linux

Health Status

Consensus
In Consensus (8/8 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
3/5 BW Auths Measured 664 bit/s Median
Stability
Not Overloaded | UP 1d 17h 10m ago
Reachability
IPv4: 8/9 | v6: 7/8 (Directory Auths)
First Seen
2d 46m 3s ago
BW Weight
0.00% of Network | 670 Kbit/s Observed By Relay
Version
0.4.9.6 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: 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.
  • 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
ip161.ip-51-83-156.eu
51.83.156.161:80
[2001:41d0:602:3a9a::fc0f]:80
Reachability (Directory Authorities)
IPv4
8/9
IPv6
7/8 (1 don't test)
Location
Country
Poland Poland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS16276
AS Name
OVH SAS (BGP.tools)
AS Rarity
Common (score: 0/5, 11.30% consensus weight, 195 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 1/8 | Stable: 0/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 0/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
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
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 Below (0/8 DA) 670.9 Kbit/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 (0/8 DA) Median: 2.0d (0/8 DA above threshold)
Min/Max: 1.7d / 2.0d (8/8 DA, Voting / Total Eligible)		 ≥18.7d - 60.9d (varies) (≥5/8 DA)
Uptime Below (0/8 DA) 1.7d (R) ≥12.9d - 13.1d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (1/8 DA) 1/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 Below (0/8 DA) 0/8 DA assigned Stable ≥18.7d - 60.9d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (8/8 DA) Majority: 100.0% (8/8 DA) ≥98.0% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 2.0d (0/8 DA above threshold)
Min/Max: 1.6d / 2.0d (8/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (1/8 DA) 1/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 Below (0/8 DA) 0/8 DA assigned Stable ≥18.7d - 60.9d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (8/8 DA) Majority: 100.0% (8/8 DA) ≥98% (≥5/8 DA)
Time Known Below (0/8 DA) (need 6.0 more days) Median: 2.0d (0/8 DA above threshold)
Min/Max: 1.6d / 2.0d (8/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 670.9 Kbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Below (0/8 DA) Port 80: No | Port 443: No (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-22 09:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
670.90 Kbit/s
Advertised Bandwidth
670.90 Kbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-22 09:45:07

Measured By
3/5 Bandwidth Authorities
Not measured by: gabelmoo, moria1
Median Measurement
664.0 bit/s
Min / Max
8 bit/s / 960 bit/s
Deviation
952 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 17h 10m 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 46m 3s ago (2026-04-20 10:00:00)
Last Seen
1h 46m 3s ago (2026-04-22 09:00:00)
Last Restarted
1d 17h 10m ago (2026-04-20 17:35:05)
Last Changed Address
2026-04-20 10:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-22 02:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
tor@kllx.eu
Family Configuration
Family Support
Happy Families (15) — Has family-cert in server descriptor (guide)
MyFamily (legacy declarations) — 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
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 22 Apr 2026 10:46:01 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-22 09: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) No — — — N No — — — — — — — — — — — —
dannenberg (DE) Yes Yes No — N Yes Yes Running, Valid, V2Dir 670.9 Kbit/s | 816.0 Kbit/s 670.9 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.0d | 39.8d 1.7d | 13.1d 100.0% | 98.0% 2.0d | 1.0d 2026-04-22 03:04:12 664 bit/s
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir 670.9 Kbit/s | 816.0 Kbit/s 670.9 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.0d | 39.7d 1.7d | 13.1d 100.0% | 98.0% 2.0d | 1.0d 2026-04-22 03:04:12 664 bit/s
faravahar (US) Yes Yes No — N Yes Yes Running, Valid, V2Dir 670.9 Kbit/s | 816.0 Kbit/s 670.9 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.0d | 60.9d 1.7d | 13.1d 100.0% | 98.0% 2.0d | 1.0d 2026-04-22 03:04:12 664 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 670.9 Kbit/s | 816.0 Kbit/s 670.9 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.0d | 60.9d 1.7d | 13.1d 100.0% | 98.0% 2.0d | 1.0d 2026-04-22 03:04:12 664 bit/s
longclaw (US) Yes Yes No — Y Yes — Running, Valid, V2Dir 670.9 Kbit/s | 816.0 Kbit/s 670.9 Kbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.0d | 63.0d 1.7d | 13.1d 100.0% | 98.0% 2.0d | 1.0d 2026-04-22 03:04:12 784 bit/s
maatuska (SE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 670.9 Kbit/s | 816.0 Kbit/s 670.9 Kbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.7d | 8d 1.7d | 18.7d 1.7d | 13.1d 100.0% | 98.0% 1.7d | 1.0d 2026-04-22 03:04:12 960 bit/s
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 670.9 Kbit/s | 8.4 Mbit/s 670.9 Kbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.6d | 8d 1.8d | 303.2d 1.7d | 12.9d 100.0% | 98.0% 1.6d | 9.9d 2026-04-22 03:04:12 664 bit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 670.9 Kbit/s | 816.0 Kbit/s 670.9 Kbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.0d | 61.9d 1.7d | 13.1d 100.0% | 98.0% 2.0d | 1.0d 2026-04-22 03:04:12 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.