View Relay "BSDrelay09"

Fingerprint: `11AA8059BB9A0EC58412E91723F81FFD49C60E7E` | Operator: zwiebelrouter.net v3 (11 relays) ✓ Validated | Family: 11 relays | email:zwiebelrouter[]protonmail[]com... | AS53667 | Luxembourg | FreeBSD

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable (5)
BW Verified: 5/7 BW Auths Measured 208 Mbit/s Median
Stability: Not Overloaded | UP 3d 2h 26m ago | UP 97% (1M)

Reachability: IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen: 11mo 1w 18h ago
BW Weight: 0.01% of Network | 242 Mbit/s Observed By Relay
Version: 0.4.9.14 Not Recommended

Issues Detected:

Guard: WFU below threshold : 1/9 authorities meet guard-wfu (≥98%; dizum: ≥97.84099999999999%; 5 needed). bastet, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 95.7%–97.97%.
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: uptime below 96 hours : Only 0/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable.
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.14 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: bsdrelay09.zwiebelrouter.net
107.189.12.210:443
[2605:6400:30:fa58::1]:443

Reachability (Directory Authorities)

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

Location

Country: Luxembourg
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS53667
AS Name: FranTech Solutions (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.40% consensus weight, 30 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, 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	Meets (9/9 DA)	63.2 Mbit/s – 464.0 Mbit/s (5 DA measured) 80.0 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	Below (1/9 DA)	Median: 7.0d (1/9 DA above threshold) Min/Max: 2.2d / 11266.8d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
Stable	Uptime	Below (0/9 DA)	3.1d (R)	≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 63.2 Mbit/s – 464.0 Mbit/s (5 DA measured) 80.0 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 (7/9 DA)	7/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)	3.1d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 63.2 Mbit/s – 464.0 Mbit/s (5 DA measured) 80.0 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 (7/9 DA)	7/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 (1/9 DA)	Median: 97.7% (1/9 DA above threshold) Min/Max: 95.7% / 98.0% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 16.0d (9/9 DA above threshold) Min/Max: 9.5d / 17.8d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	63.2 Mbit/s – 464.0 Mbit/s (5 DA measured) 80.0 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: 242.07 Mbit/s
Advertised Bandwidth: 242.07 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 1.6 PB (1 year)
1mo: 82 TB | 6mo: 805 TB | 1y: 1.6 PB

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: 208.0 Mbit/s (median of 5 measurements)
Measured Min / Max: 63.2 Mbit/s / 464.0 Mbit/s
Deviation: 400.8 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0131% of network (72th pctl) | Guard: N/A | Middle: 0.0379% (89th pctl) | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 3d 2h 26m ago
Overall Uptime (1M/6M/1Y/5Y): 97.8%/98.5%/99.2%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (97.8%/98.5%/99.2%/0.0%)
Hibernating: No

Timestamps

First Seen: 11mo 1w 18h ago (2025-12-01 19:00:00)
Last Seen: 2h 15m 37s ago (2026-11-04 11:00:00)
Last Restarted: 3d 2h 26m ago (2026-11-01 10:49:05)
Last Changed Address: 2026-04-06 23:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 5h 30m 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 (?): zwiebelrouter.net
Operator Validation: Validated (11/11 relays)
This Relay: Validated (dns-familyid-ed25519)
Contact: email:zwiebelrouter[]protonmail[]com ciissversion:3 url:zwiebelrouter.net proof:dns-familyid-ed25519 os:FreeBSD

Family Configuration

Family Support: Happy Families (11) — Has family-cert in server descriptor (guide) | View Full Family (11)

Happy Families (family-cert)

Effective Members: 11

048B9A44712BDC2B896691E37B2B62C4A81D4DE5
11AA8059BB9A0EC58412E91723F81FFD49C60E7E (this relay)
43E366E41D547A1D3F22FBED10250B6C57F848DA
46F597072DCA7EAE96F8728748DC8098E2C99633
5DDFF053624BAD3126663545B5FCAB0D9FB10E72
8257411C95B2B8367F13FE5ED4BEE4F574940556
A782A4FACAD3CEABDEB51ABE4385BBF023F739DF
B3A7B5E707A290C44C8EC39F3F8D23DD65A767BD
C003825610F646FD4CCC82BFCC5F1FD98D9800C7
CE0D31663C7CE954B1944B6D65449963F12BDF78
DDB106FA0A9FC4C1490294E197641D80DCCB01E0

MyFamily (legacy declarations) — none

Software and Version

Platform: FreeBSD — Tor 0.4.9.14 on FreeBSD
Version: 0.4.9.14 — 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

IPv6 Exit Policy Summary

None

Full Exit Policy

reject *:*

Last fetch was at Wed, 04 Nov 2026 13:15:37 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	176.0 Mbit/s (M) \| 816.0 Kbit/s	176.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	97.3% \| 98%	14.1d \| 8d	5.3d \| 8.4d	3.1d \| 5.2d	2026-11-03 19:49:14	176.0 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	63.2 Mbit/s (M) \| 816.0 Kbit/s	63.2 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	98.0% \| 98%	17.8d \| 8d	7.0d \| 9.3d	3.1d \| 5.3d	2026-11-03 19:49:14	63.2 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	95.7% \| 98%	13.8d \| 8d	4.1d \| 6.7d	3.1d \| 5.3d	2026-11-03 19:49:14	80.0 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	97.7% \| 98%	16.0d \| 8d	5.9d \| 6.5d	3.1d \| 5.3d	2026-11-03 19:49:14	80.0 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	464.0 Mbit/s (M) \| 816.0 Kbit/s	464.0 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	97.9% \| 98%	17.0d \| 8d	8.3d \| 10.8d	3.1d \| 5.3d	2026-11-03 19:49:14	464.0 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	N/T	Running, Valid, V2Dir, Fast, Stable	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	97.97% \| 98%	17.0d \| 8d	8.2d \| 10.9d	3.1d \| 5.3d	2026-11-03 19:49:14	80.0 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	96.6% \| 98%	15.1d \| 8d	2.2d \| 2.4d	3.1d \| 5.3d	2026-11-03 19:49:14	80.0 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	208.0 Mbit/s (M) \| 8.4 Mbit/s	208.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	96.4% \| 98%	9.5d \| 8d	11266.8d \| 7607.5d	3.1d \| 5.3d	2026-11-03 19:49:14	208.0 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	424.0 Mbit/s (M) \| 816.0 Kbit/s	424.0 Mbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	97.9% \| 98%	17.1d \| 8d	8.3d \| 10.6d	3.1d \| 5.3d	2026-11-03 19:49:14	424.0 Mbit/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 "BSDrelay09"

Fingerprint: 11AA8059BB9A0EC58412E91723F81FFD49C60E7E | Operator: zwiebelrouter.net v3 (11 relays) ✓ Validated | Family: 11 relays | email:zwiebelrouter[]protonmail[]com... | AS53667 | Luxembourg | FreeBSD

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: `11AA8059BB9A0EC58412E91723F81FFD49C60E7E` | Operator: zwiebelrouter.net v3 (11 relays) ✓ Validated | Family: 11 relays | email:zwiebelrouter[]protonmail[]com... | AS53667 | Luxembourg | FreeBSD