View Relay "JohnFilch123"

Fingerprint: `C404F74B4F400C193422E0B615ACAECA7AADE8C9` | Family: 14 relays | relay operator - contact:... | AS34689 | Slovakia | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Stable (4)
BW Verified: 5/7 BW Auths Measured 456 Kbit/s Median
Stability: Not Overloaded | UP 11h 44m 23s ago | UP 100% (1M)

Reachability: IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen: 1mo 4d 14h ago
BW Weight: 0.00% of Network | 8 Mbit/s Observed By Relay
Version: 0.4.9.15 Recommended

Issues Detected:

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: bandwidth below threshold : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 312.0 Kbit/s – 1.7 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 4.1 Mbit/s.
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: WFU below threshold : 3/9 authorities meet guard-wfu (≥98%; dizum: ≥97.84099999999999%; 5 needed). bastet, dizum, faravahar, gabelmoo, maatuska and moria1 measured 96.6%–97.8%.
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.
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.
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: 95.131.202.24:9001
[2a05:5502::f38c:560d:c89f:1]:9001

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: Slovakia
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS34689
AS Name: Castlegem SRL (BGP.tools)
AS Rarity: Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Stable

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
Running	IPv6 Reachability	Meets (8/8 DA)	8/8 tested authorities reached relay	≥5/8 tested (majority) (≥5/8 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	Partial (5/9 DA)	312.0 Kbit/s – 1.7 Mbit/s (5 DA measured) 4.1 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Partial (6/9 DA)	Median: 12.3d (6/9 DA above threshold) Min/Max: 4.1d / 828.4d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
Stable	Uptime	Below (0/9 DA)	0.5d (R)	≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (5/9 DA)	5/9 DA assigned Fast 312.0 Kbit/s – 1.7 Mbit/s (5 DA measured) 4.1 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	Uptime	Below (0/9 DA)	0.5d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard	Prereq: Fast	Meets (5/9 DA)	5/9 DA assigned Fast 312.0 Kbit/s – 1.7 Mbit/s (5 DA measured) 4.1 Mbit/s (4 DA relay-reported)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (3/9 DA)	Median: 97.4% (3/9 DA above threshold) Min/Max: 96.6% / 98.7% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 19.2d (9/9 DA above threshold) Min/Max: 9.7d / 32.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	312.0 Kbit/s – 1.7 Mbit/s (5 DA measured) 4.1 Mbit/s (4 DA relay-reported)	≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA)
Exit	Exit Policy	Below (0/9 DA)	Port 80: No \| Port 443: No (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-11-04 12:45:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 8.77 Mbit/s
Advertised Bandwidth: 4.10 Mbit/s
Rate Limit: 4.10 Mbit/s
Burst Limit: 4.26 Mbit/s
Total Data: 1.7 TB (6 months)
1mo: 1.7 TB | 6mo: 1.7 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 12:45:10

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight: 456.0 Kbit/s (median of 5 measurements)
Measured Min / Max: 312.0 Kbit/s / 1.7 Mbit/s
Deviation: 1.4 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: 0.0001% (4th pctl) | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 11h 44m 23s ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/90.3%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (100.0%/90.3%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 1mo 4d 14h ago (2026-09-30 23:00:00)
Last Seen: 2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted: 11h 44m 23s ago (2026-11-04 02:01:16)
Last Changed Address: 2026-09-30 23:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h 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

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-11-04 04:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: relay operator - contact: lucasvandekwq [at] rambler [dot] ru

Family Configuration

Family Support: Both — Happy Families (14 / 100%) and MyFamily (0 / 0%) | View Full Family (14)

Happy Families (family-cert)

Effective Members: 14

0CA82A89EF522807DB0D6531CB113479A92AA98A
1F48F55FE04274F32AB34B8F946F9DB4488FFEFF
3757D20FF0267D068723B11A94173AEAD711BC3A
5384BDBED00FDE625E212F834D215B9C2868765E
9173EEB6ED71B478ECA8378B7883B6C6302E6083
9C5F0D959B2D68F2BDD19F4F73F595E9B1CCFDCF
9D33A2015B93D00CC7FCCBE00C201644221B00B3
9E3D756D51749425B6CDF76D752E171A502E2899
C404F74B4F400C193422E0B615ACAECA7AADE8C9 (this relay)
C96C517B69B61222AC63FB4890B2F32D555BB4ED
E024D785B62B0CDFD5D104D3558EC754593E36A0
EC7BA0909377D7F6222C099C356979540266F56F
F5BAF73466B5EA0BF4A7F75881C123D93949387D
F6C945404950062B15F2678A165A9D09F9E6FF98

MyFamily (legacy declarations)

Effective Members: 0

none

Alleged Member: 1

(they don't list you back)

A00AD5BACFEB206079BF0C083A40D37545CA9385 (not in the network)

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.15 on Linux
Version: 0.4.9.15 — 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, 04 Nov 2026 13:45:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).

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 (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)
bastet (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	1.7 Mbit/s (M) \| 816.0 Kbit/s	1.7 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	97.4% \| 98%	17.3d \| 8d	10.9d \| 8.4d	0.5d \| 5.2d	2026-11-04 02:01:18	1.7 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Stable	456.0 Kbit/s (M) \| 816.0 Kbit/s	456.0 Kbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	98.7% \| 98%	31.9d \| 8d	21.4d \| 9.3d	0.5d \| 5.3d	2026-11-04 02:01:18	456.0 Kbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	4.1 Mbit/s (R) \| 816.0 Kbit/s	4.1 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	96.6% \| 98%	19.2d \| 8d	12.3d \| 6.7d	0.5d \| 5.3d	2026-11-04 02:01:18	4.1 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	4.1 Mbit/s (R) \| 816.0 Kbit/s	4.1 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	96.9% \| 98%	14.0d \| 8d	6.4d \| 6.5d	0.5d \| 5.3d	2026-11-04 02:01:18	4.1 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Stable	312.0 Kbit/s (M) \| 816.0 Kbit/s	312.0 Kbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	97.8% \| 98%	18.4d \| 8d	13.2d \| 10.8d	0.5d \| 5.3d	2026-11-04 02:01:18	312.0 Kbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	N/T	Running, Valid, V2Dir, Fast, Stable	4.1 Mbit/s (R) \| 816.0 Kbit/s	4.1 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	98.7% \| 98%	32.1d \| 8d	30.4d \| 10.9d	0.5d \| 5.3d	2026-11-04 02:01:18	4.1 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	4.1 Mbit/s (R) \| 816.0 Kbit/s	4.1 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	97.2% \| 98%	20.8d \| 8d	4.1d \| 2.4d	0.5d \| 5.3d	2026-11-04 02:01:18	4.1 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Stable	1.3 Mbit/s (M) \| 8.4 Mbit/s	1.3 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	97.0% \| 98%	9.7d \| 8d	828.4d \| 7607.5d	0.5d \| 5.3d	2026-11-04 02:01:18	1.3 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Stable	384.0 Kbit/s (M) \| 816.0 Kbit/s	384.0 Kbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	98.1% \| 98%	22.7d \| 8d	8.3d \| 10.6d	0.5d \| 5.3d	2026-11-04 02:01:18	384.0 Kbit/s (M)

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.

View Relay "JohnFilch123"

Fingerprint: C404F74B4F400C193422E0B615ACAECA7AADE8C9 | Family: 14 relays | relay operator - contact:... | AS34689 | Slovakia | Linux

Addresses

Reachability (Directory Authorities)

Location

Autonomous System

Eligibility Flag Vote Details

Capacity (Relay Reported)

Measurement (Directory Authority Verified)

History

Uptime Metrics

Timestamps

General Overload (from /details)

File Descriptor Exhaustion (from /bandwidth)

Rate Limits (from /bandwidth)

History

Operator Identity

Family Configuration

Full Exit Policy

Fingerprint: `C404F74B4F400C193422E0B615ACAECA7AADE8C9` | Family: 14 relays | relay operator - contact:... | AS34689 | Slovakia | Linux