View Relay "xilia23"

Fingerprint: `DF522999EA9908ABF8A0A9589B8B7319646590BD` | Family: 1 relay | Uu77bBt0eDko5iDrRNiXt2quIVPMNKvILk1eq... | AS56322 | Hungary | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Fast (3)
BW Verified: 4/7 BW Auths Measured 3 Mbit/s Median
Stability: Not Overloaded | DOWN 2h 45m 21s ago | UP 51% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 4mo 3w 11h ago
BW Weight: 0.00% of Network | 27 Mbit/s Observed By Relay
Version: 0.4.9.8 Not 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: bandwidth below threshold : 3/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 – 280.0 Mbit/s). bastet, gabelmoo, moria1 and tor26 measured this relay at 2.7 Mbit/s – 8.8 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 : Weighted Fractional Uptime 40.2% 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 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: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
HSDir: WFU below threshold : WFU 40.2% 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.
Tor version not recommended : Running Tor version 0.4.9.8 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Connectivity and Location

Addresses

OR Address: 99645408-stellar.serverastra.com
91.219.236.39:22222
[2a10:c800:1:6efd::1]:22222

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Hungary
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS56322
AS Name: ServerAstra Kft. (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.08% consensus weight, 8 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Fast

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 (3/3 DA)	3/3 tested authorities reached relay	≥2/3 tested (majority) (≥2/3 DA)
Valid	Descriptor	Meets (9/9 DA)	9/9 authorities assigned Valid	Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir	DirPort Available	Below (0/9 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Partial (8/9 DA)	2.7 Mbit/s – 8.8 Mbit/s (4 DA measured) 27.7 Mbit/s (3 DA relay-reported) dannenberg, faravahar: not published	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below (1/9 DA)	Median: 0.1d (1/9 DA above threshold) Min/Max: 0.1d / 20728.7d (9/9 DA, Voting / Total Eligible)	≥5.1d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.3d
Stable	Uptime	Below (0/9 DA)	0.8d (R)	≥3.2d - 3.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/9 DA assigned Fast 2.7 Mbit/s – 8.8 Mbit/s (4 DA measured) 27.7 Mbit/s (3 DA relay-reported) dannenberg, faravahar: not published	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/9 DA)	1/9 DA assigned Stable	≥5.1d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.3d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 42.6% (0/9 DA above threshold) Min/Max: 40.0% / 45.7% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 9.8d (9/9 DA above threshold) Min/Max: 9.7d / 10.0d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets (8/9 DA)	8/9 DA assigned Fast 2.7 Mbit/s – 8.8 Mbit/s (4 DA measured) 27.7 Mbit/s (3 DA relay-reported) dannenberg, faravahar: not published	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/9 DA)	1/9 DA assigned Stable	≥5.1d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.3d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 42.6% (0/9 DA above threshold) Min/Max: 40.0% / 45.7% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 9.8d (9/9 DA above threshold) Min/Max: 9.7d / 10.0d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (3/9 DA)	2.7 Mbit/s – 8.8 Mbit/s (4 DA measured) 27.7 Mbit/s (3 DA relay-reported) dannenberg, faravahar: not published	≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.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-10-12 06:45:05).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 27.75 Mbit/s
Advertised Bandwidth: 27.75 Mbit/s
Rate Limit: 41.94 Mbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 2.0 TB (6 months)
1mo: 989 GB | 6mo: 2.0 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-12 06:45:05

Measured By: 4/7 Bandwidth Authorities
Not measured by: dannenberg, faravahar, longclaw
Consensus Weight: 3.5 Mbit/s (median of 4 measurements)
Measured Min / Max: 2.7 Mbit/s / 8.8 Mbit/s
Deviation: 6.1 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0002% of network (10th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: DOWN 2h 45m 21s ago
Overall Uptime (1M/6M/1Y/5Y): 51.4%/71.8%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): —/69.9%/—/—
Hibernating: No

Timestamps

First Seen: 4mo 3w 11h ago (2026-05-23 20:00:00)
Last Seen: 2h 45m 21s ago (2026-10-12 05:00:00)
Last Restarted: 19h 34m 30s ago (2026-10-11 12:10:51)
Last Changed Address: 2026-05-23 20:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-11 23:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: Uu77bBt0eDko5iDrRNiXt2quIVPMNKvILk1eqJbAVk9e@posteo.ch

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

DF522999EA9908ABF8A0A9589B8B7319646590BD (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.8 on Linux
Version: 0.4.9.8 — Not Recommended
Version Status: Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health

Not an exit relay — DNS health testing does not apply.

IPv4 Exit Policy Summary

reject: 
  1-65535

Full Exit Policy

reject *:*

Last fetch was at Mon, 12 Oct 2026 07:45:20 GMT.

Consensus Evaluation

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

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 (BW\|T)	Guard BW (BW\|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	No	—	Y	Yes	Running, Valid, Fast	8.8 Mbit/s (M) \| 816.0 Kbit/s	8.8 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	40.2% \| 98%	9.8d \| 8d	0.1d \| 10.8d	0.8d \| 3.3d	40.2% \| 98.0%	9.8d \| 1.0d	2026-10-12 04:12:08	8.8 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	not published \| 816.0 Kbit/s	not published \| 280.0 Mbit/s OR 16.8 Mbit/s	40.7% \| 98%	9.8d \| 8d	0.1d \| 5.1d	0.8d \| 3.3d	40.7% \| 98.0%	9.8d \| 1.0d	2026-10-12 04:12:08	27.7 Mbit/s (R)
dizum (NL)	Yes	Yes	No	—	N	Yes	Valid, Fast	27.7 Mbit/s (R) \| 816.0 Kbit/s	27.7 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	44.9% \| 98%	9.9d \| 8d	0.1d \| 10.9d	0.8d \| 3.2d	44.9% \| 98.0%	9.9d \| 1.0d	2026-10-12 04:12:08	27.7 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Valid, Fast	not published \| 816.0 Kbit/s	not published \| 280.0 Mbit/s OR 16.8 Mbit/s	40.0% \| 98%	9.7d \| 8d	0.1d \| 11.7d	0.8d \| 3.2d	40.0% \| 98.0%	9.7d \| 1.0d	2026-10-12 04:12:08	27.7 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Valid, Fast	3.5 Mbit/s (M) \| 816.0 Kbit/s	3.5 Mbit/s (M) \| 264.0 Mbit/s OR 16.8 Mbit/s	43.7% \| 98%	9.9d \| 8d	0.1d \| 10.8d	0.8d \| 3.2d	43.7% \| 98.0%	9.9d \| 1.0d	2026-10-12 04:12:08	3.5 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	27.7 Mbit/s (R) \| 816.0 Kbit/s	27.7 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	45.7% \| 98%	9.7d \| 8d	0.1d \| 11.2d	0.8d \| 3.2d	45.7% \| 98.0%	9.7d \| 1.0d	2026-10-12 04:12:08	27.7 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Running, Valid, Fast	27.7 Mbit/s (R) \| 816.0 Kbit/s	27.7 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	43.8% \| 98%	10.0d \| 8d	0.1d \| 10.6d	0.8d \| 3.3d	43.8% \| 98.0%	10.0d \| 1.0d	2026-10-12 04:12:08	27.7 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Valid, Stable	6.1 Mbit/s (M) \| 8.4 Mbit/s	6.1 Mbit/s (M) \| 208.0 Mbit/s OR 16.8 Mbit/s	40.8% \| 98%	9.9d \| 8d	20728.7d \| 8990.3d	0.8d \| 3.3d	40.8% \| 98.0%	9.91d \| 9.90d	2026-10-12 04:12:08	6.1 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Valid, Fast	2.7 Mbit/s (M) \| 816.0 Kbit/s	2.7 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	42.6% \| 98%	9.7d \| 8d	0.1d \| 11.2d	0.8d \| 3.3d	42.6% \| 98.0%	9.7d \| 1.0d	2026-10-12 04:12:08	2.7 Mbit/s (M)

— = not tested/available • 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.