View Relay "zer"

Fingerprint: `5FE47FBF91A1336649BE7B0FF7C1D981F112F7CF` | Family: 1 relay | admin(at)gmail(dot)com | AS51167 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir (3)
BW Verified: 3/7 BW Auths Measured 688 Kbit/s Median
Stability: Not Overloaded | UP 2h 32m 20s ago

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 2h 15m 38s ago
BW Weight: 0.00% of Network | 925 Kbit/s Observed By Relay
Version: 0.4.9.11 Not Recommended

Issues Detected:

Not getting the Fast flag : Only 4/9 authorities vote Fast (5 needed). bastet and moria1 measured this relay at 384.0 Kbit/s – 688.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). dannenberg and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored). faravahar judged it by bandwidth not shown in the votes. Its consensus weight, the median of the 3 bandwidth-scanner measurements, is 688.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/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 and moria1 measured this relay at 384.0 Kbit/s – 2.2 Mbit/s. dizum, longclaw and maatuska used the relay-reported 920.0 Kbit/s. dannenberg and 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: WFU below threshold : Weighted Fractional Uptime 1.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 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.
HSDir: WFU below threshold : WFU 1.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.11 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.

Notes:

Bandwidth authority measurements below majority: 3/7 bandwidth authorities measured this relay (majority is 4).

Connectivity and Location

Addresses

OR Address: vmi738242.contaboserver.net
167.86.122.9:9001

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS51167
AS Name: Contabo GmbH (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.20% consensus weight, 35 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir

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
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	Below (4/9 DA)	384.0 Kbit/s – 2.2 Mbit/s (3 DA measured) 920.0 Kbit/s (3 DA relay-reported) 0 bit/s (2 DA unmeasured, counted as 0) 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 (0/9 DA)	Median: 0.4d (1/9 DA above threshold) Min/Max: 0.3d / 584.2d (9/9 DA, Voting / Total Eligible)	≥5.0d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.1d
Stable	Uptime	Below (0/9 DA)	0.1d (R)	≥3.3d - 3.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (4/9 DA)	4/9 DA assigned Fast 384.0 Kbit/s – 2.2 Mbit/s (3 DA measured) 920.0 Kbit/s (3 DA relay-reported) 0 bit/s (2 DA unmeasured, counted as 0) 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.0d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.1d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 1.1% (0/9 DA above threshold) Min/Max: 0.8% / 4.6% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 37.7d (9/9 DA above threshold) Min/Max: 9.5d / 40.5d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below (4/9 DA)	4/9 DA assigned Fast 384.0 Kbit/s – 2.2 Mbit/s (3 DA measured) 920.0 Kbit/s (3 DA relay-reported) 0 bit/s (2 DA unmeasured, counted as 0) 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.0d - 10.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥8990.1d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 1.1% (0/9 DA above threshold) Min/Max: 0.8% / 4.6% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 37.7d (9/9 DA above threshold) Min/Max: 9.5d / 40.5d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	384.0 Kbit/s – 2.2 Mbit/s (3 DA measured) 920.0 Kbit/s (3 DA relay-reported) 0 bit/s (2 DA unmeasured, counted as 0) 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-11 23:15:05).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 925.70 Kbit/s
Advertised Bandwidth: 925.70 Kbit/s
Rate Limit: 16.78 Mbit/s
Burst Limit: 8.59 Gbit/s
Total Data: N/A

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-11 23:15:05

Measured By: 3/7 Bandwidth Authorities
Not measured by: dannenberg, faravahar, longclaw, tor26
Consensus Weight: 688.0 Kbit/s (median of 3 measurements)
Measured Min / Max: 384.0 Kbit/s / 2.2 Mbit/s
Deviation: 1.9 Mbit/s [Warning] High variation

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

Uptime and Stability

Uptime Metrics

Current Status: UP 2h 32m 20s ago
Overall Uptime (1M/6M/1Y/5Y): 0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): N/A
Hibernating: No

Timestamps

First Seen: 2h 15m 38s ago (2026-10-11 21:00:00)
Last Seen: 1h 15m 38s ago (2026-10-11 22:00:00)
Last Restarted: 2h 32m 20s ago (2026-10-11 20:43:18)
Last Changed Address: 2026-10-11 21:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: admin(at)gmail(dot)com

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

5FE47FBF91A1336649BE7B0FF7C1D981F112F7CF (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.11 on Linux
Version: 0.4.9.11 — 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 Sun, 11 Oct 2026 23:15:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-11 23:15: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, V2Dir	688.0 Kbit/s (M) \| 816.0 Kbit/s	688.0 Kbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	1.2% \| 98%	37.0d \| 8d	0.4d \| 10.8d	0.1d \| 3.3d	1.2% \| 98.0%	37.0d \| 1.0d	2026-10-11 20:43:20	688.0 Kbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s (U) \| 816.0 Kbit/s	0 bit/s (U) \| 280.0 Mbit/s OR 16.8 Mbit/s	4.6% \| 98%	28.3d \| 8d	1.2d \| 5.0d	0.1d \| 3.3d	4.6% \| 98.0%	28.3d \| 1.0d	2026-10-11 20:43:20	920.0 Kbit/s (R)
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	920.0 Kbit/s (R) \| 816.0 Kbit/s	920.0 Kbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	2.9% \| 98%	30.9d \| 8d	0.8d \| 10.8d	0.1d \| 3.3d	2.9% \| 98.0%	30.9d \| 1.0d	2026-10-11 20:43:20	920.0 Kbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	not published \| 816.0 Kbit/s	not published \| 280.0 Mbit/s OR 16.8 Mbit/s	0.8% \| 98%	40.3d \| 8d	0.3d \| 11.7d	0.1d \| 3.3d	0.8% \| 98.0%	40.3d \| 1.0d	2026-10-11 20:43:20	920.0 Kbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	2.2 Mbit/s (M) \| 816.0 Kbit/s	2.2 Mbit/s (M) \| 264.0 Mbit/s OR 16.8 Mbit/s	0.9% \| 98%	40.4d \| 8d	0.4d \| 10.8d	0.1d \| 3.3d	0.9% \| 98.0%	40.4d \| 1.0d	2026-10-11 20:43:20	2.2 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	920.0 Kbit/s (R) \| 816.0 Kbit/s	920.0 Kbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	1.0% \| 98%	40.5d \| 8d	0.4d \| 11.1d	0.1d \| 3.3d	1.0% \| 98.0%	40.5d \| 1.0d	2026-10-11 20:43:20	920.0 Kbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	920.0 Kbit/s (R) \| 816.0 Kbit/s	920.0 Kbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	0.8% \| 98%	37.7d \| 8d	0.3d \| 10.5d	0.1d \| 3.3d	0.8% \| 98.0%	37.7d \| 1.0d	2026-10-11 20:43:20	920.0 Kbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	384.0 Kbit/s (M) \| 8.4 Mbit/s	384.0 Kbit/s (M) \| 208.0 Mbit/s OR 16.8 Mbit/s	2.0% \| 98%	9.5d \| 8d	584.2d \| 8990.1d	0.1d \| 3.3d	2.0% \| 98.0%	9.5d \| 9.8d	2026-10-11 20:43:20	384.0 Kbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s (U) \| 816.0 Kbit/s	0 bit/s (U) \| 272.0 Mbit/s OR 16.8 Mbit/s	1.1% \| 98%	38.0d \| 8d	0.4d \| 11.2d	0.1d \| 3.4d	1.1% \| 98.0%	38.0d \| 1.0d	2026-10-11 20:43:20	920.0 Kbit/s (R)

— = 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.