View Relay "Killix"

Fingerprint: 71804D89E6F633D6CC5992E512273C348AA6EC7A | Family: 8 relays | tor@kllx.eu | AS20860 | United Kingdom of Great Britain and Northern Ireland | Linux

Consensus
In Consensus (9/10 Directory Auths)
BW Verified
4/8 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | UP 14h 49s ago
Reachability
IPv4: 9/10 | v6: 8/8(Directory Auths)
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.17 Recommended
Issues Detected:
  • Not getting the Fast flag : Only 0/10 authorities vote Fast (6 needed). E30CF7B3, dannenberg, gabelmoo and moria1 measured this relay at 8.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). dizum, faravahar, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored). Its consensus weight, the median of the 4 bandwidth-scanner measurements, is 8.0 Kbit/s.
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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 : 0/10 authorities credit this relay with enough bandwidth for Guard (6 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 256.0 Mbit/s). E30CF7B3, dannenberg, gabelmoo and moria1 measured this relay at 8.0 Kbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported unknown. tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • Guard: Time Known below threshold : 0/10 authorities meet guard-tk (≥8 days; E30CF7B3: ≥3 days 4 hours 32 minutes 57 seconds; 6 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have known this relay for 11.7 hours–13.1 hours.
    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 : 0/10 authorities meet Stable (uptime or MTBF at or above their own median; 6 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 do not.
    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: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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.
Notes:
  • Partial IPv4 reachability: 9/10 authorities can reach this relay
    Suggestion: Some authorities cannot reach you: 5947BB57. This may be temporary or due to geographic routing issues.
  • Bandwidth authority measurements below majority: 4/8 bandwidth authorities measured this relay (majority is 5).
    Suggestion: Some bandwidth authorities cannot measure your relay. This may be temporary or due to geographic routing. Monitor over 24-48 hours. If persistent, check firewall rules and ensure ORPort is accessible from various locations.

Addresses
OR Address
109.122.1.87:8443
[2001:1b40:5700:9b4f::1]:8443
Reachability (Directory Authorities)
IPv4
9/10
IPv6
8/8 (1 don't test)
Location
Country
United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS20860
AS Name
IOMART CLOUD SERVICES LIMITED (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.56% consensus weight, 6 operators)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/10 | Valid: 9/10 | V2Dir: 9/10 | Fast: 0/10 | Stable: 0/10 | HSDir: 0/10 | Guard: 0/10 | Exit: 0/10
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (9/10 DA) 9/10 authorities reached relay ≥6/10 DA ORPort reachable
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (9/10 DA) 9/10 authorities assigned Valid Not blacklisted + valid descriptor (≥6/10 DA)
V2Dir DirPort Available Meets (9/10 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥6/10 DA)
Fast Speed Below (0/10 DA) 8.0 Kbit/s (4 DA measured)
0 bit/s (4 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/10 DA) Median: 0.5d (0/10 DA above threshold)
Min/Max: 0.5d / 0.5d (9/10 DA, Voting / Total Eligible)
≥0.0d - 7.5d (varies) (≥6/10 DA)
[Stricter] moria1: ≥11846.6d
Uptime Below (0/10 DA) 0.6d (R) ≥2.1d - 2.1d (varies) (≥6/10 DA)
[Stricter] 5947BB57: ≥5.9d
HSDir Prereq: Fast Below (0/10 DA) 0/10 DA assigned Fast
8.0 Kbit/s (4 DA measured)
0 bit/s (4 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/10 DA) 0/10 DA assigned Stable ≥0.0d - 7.5d (varies) (≥6/10 DA)
[Stricter] moria1: ≥11846.6d
Prereq: V2Dir Meets (9/10 DA) 9/10 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥6/10 DA)
Uptime Below (0/10 DA) 0.6d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥6/10 DA)
[Stricter] moria1: ≥98% WFU and ≥9.6d Time Known
Guard Prereq: Fast Below (0/10 DA) 0/10 DA assigned Fast
8.0 Kbit/s (4 DA measured)
0 bit/s (4 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥6/10 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/10 DA) 0/10 DA assigned Stable ≥0.0d - 7.5d (varies) (≥6/10 DA)
[Stricter] moria1: ≥11846.6d
Prereq: V2Dir Meets (9/10 DA) 9/10 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥6/10 DA)
WFU Partial (9/10 DA) Majority: 100.0% (9/10 DA above threshold) ≥98%; maatuska: ≥97.17199999999999% (≥6/10 DA)
Time Known Below (0/10 DA) Median: 0.5d (0/10 DA above threshold)
Min/Max: 0.5d / 0.5d (9/10 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥3 days 4 hours 32 minutes 57 seconds (≥6/10 DA)
Bandwidth Below (0/10 DA) 8.0 Kbit/s (4 DA measured)
0 bit/s (4 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-256.0 Mbit/s) (≥6/10 DA)
Exit Exit Policy Below (0/10 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥6/10 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-16 06:45:06).

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

Source: CollecTor — fetched 2026-11-16 06:45:06

Measured By
4/8 Bandwidth Authorities
Not measured by: 5947BB57, faravahar, longclaw, tor26
Consensus Weight
8.0 Kbit/s (median of 4 measurements)
Measured Min / Max
8.0 Kbit/s / 8.0 Kbit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 14h 49s 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
13h 45m 39s ago (2026-11-15 17:00:00)
Last Seen
1h 45m 39s ago (2026-11-16 05:00:00)
Last Restarted
14h 49s ago (2026-11-15 16:44:50)
Last Changed Address
2026-11-15 17:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-16 06:45 UTC. /details snapshot 2026-11-16 05:00:00 UTC (cached 45s ago). /bandwidth snapshot 2026-11-15 21:00:00 UTC (cached 8h ago).

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
Status
No rate-limit report in available data
Rate Limit
—
Burst Limit
—
Write counter
—
Read counter
—
About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.

curl http://127.0.0.1:9035/metrics
History
Uptime, last 30 days

Operator Identity

Source: AROI Validation API — 2026-11-15 22: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 (42) — Has family-cert in server descriptor (guide) | View Full Family (8)
Happy Families (family-cert)
Effective Members: 42
0251D83BD2C2B796782927EA6F2788300A6A7632
1166AEB23D23DAA98AD1B26F33A22EFA4728156A
11F1F03FAC206D210EDA738D87741888572D8F51
1445E267FABC1258CD48E1BBA874CF2B24E64B14
14E8A657A65DA1CAB27312724716FBF121BD9FA3
2527036AF282A01B49EDBE08C1968D7A11ABFAAC
292EA547A468242D8E0674249E118D171A76F702
3204BDBDF4BA195ECDD24636BD4A5A286F8F91EE
32A1B61C0B911CC5C7F7BA5F10DCDF021E394654
3AB453B8C3DC15D8227CCBCF46ABD4043229F6C5
3D62FC61399E0DB497303BED14B66E0CE22EFA15
48BF7793A9D66D64500CFC9E13E254D29F958D19
4D1C9BA70C884135BD0B8DFA61335F7CE0A87EF6
52748D60C5C2B0E4C8E77CFB0DD73AAB4E93EA88
54836BA33D51A7EBEF4B12D49C9AC8E694E23B85
5B26E959ED27C3C592EE5FFE13EBC823522F42F4
67E4E67D99E1C7A9C21A62FC7CA606F9B317511C
6FD1D76B5610425119AD8408A10AC85893A5D849
71804D89E6F633D6CC5992E512273C348AA6EC7A (this relay)
73CF853616968C32E5A749AF1031CE578A615AEE
783D2CED0A4076861E592360D6C3BA1678F8BCF6
7DBEC94539BC6C7D4BA479B1E74E3DD77480304D
7DDCD7BA81281C66812D0454DAF13D4094EEEFE5
843B79FA8BA62F8EBD2DD384339D00B25C4AF10B
99166FD0DCD08DBD252346AC3F360C55F94A26AB
A523F1BA3168371F81BAA702011A6F102C048A47
AB7ABEFB85835B2514E274D14242DCCC5C737D0B
AE58F537146DDACC46997D3A1873C13361BA455A
B0AFC7D6158A8A8BC0872115531F6276BB9FE4E1
B7802269A66895EBEFC5544CCB2F593A2C747A6E
BA32B4CD0916FA4EB672D419B33906E989C44165
BBF737F14EA8FB839A5266E3F04C71E27AFAFE3E
C29DCCA7A300A1E8A753EE990694FD25248AE5ED
D59013FB6F56547F2D5F9A7CC2F9F12EF92AC6FD
D5BCE2DD18BF1C09C7CE48B2DCEFF3007CE51867
DD6591D8171D4C1F85E36667662283B415D19073
DDBA0B343C37E38E6A3DFD611CC96EC0FBFB23FF
ED979063EF8E6AC38C6FE06C9A1E42E2996C797F
F82857827400C38D58BD32166A9F3A12263F3245
F98EB9A36CDD142FE07661EECB97F8AA59FE5EC4
FB24621A9852CEA64EF88B22029D9FBAB018E198
FD3A973D6C7BC207FFC3CD59ED16EC71E0ADB802
MyFamily (legacy declarations) — none

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

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 Mon, 16 Nov 2026 06:45:38 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-16 06:45:06).

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 (BW|T) Guard BW (BW|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) Desc Published Cons Wt (Authority)
5947BB57 No — — — Y No — — — — — — — — — —
E30CF7B3 Yes Yes No — Y Yes Yes Running, Valid, V2Dir 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.5d | 3d 0.5d | 1.9d 0.6d | 2.1d 2026-11-15 16:44:59 8.0 Kbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 7.5d 0.6d | 2.1d 2026-11-15 16:44:59 8.0 Kbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 6.0d 0.6d | 2.1d 2026-11-15 16:44:59 —
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 6.3d 0.6d | 2.1d 2026-11-15 16:44:59 —
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 8.0 Kbit/s (M) | 816.0 Kbit/s 8.0 Kbit/s (M) | 232.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 7.7d 0.6d | 2.1d 2026-11-15 16:44:59 8.0 Kbit/s (M)
longclaw (US) Yes Yes No — Y Yes N/T Running, Valid, V2Dir 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 8.4d 0.6d | 2.1d 2026-11-15 16:44:59 —
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 97% 0.5d | 8d 0.5d | 1.7d 0.6d | 2.1d 2026-11-15 16:44:59 —
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 8.0 Kbit/s (M) | 8.4 Mbit/s 8.0 Kbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 11846.6d 0.6d | 2.1d 2026-11-15 16:44:59 8.0 Kbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 232.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.5d | 8d 0.5d | 7.7d 0.6d | 2.1d 2026-11-15 16:44:59 —

N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.