View Relay "Bootlicker"

Fingerprint: `91B4A814EB50F5231297AF2A6607F7E9E95A3330` | Family: 1 relay | myemail@example.com | AS44869 | Denmark | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Fast, Stable (4)
BW Verified: 5/7 BW Auths Measured 248 Mbit/s Median
Stability: Not Overloaded | UP 2d 20h 33m ago | UP 98% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 3mo 1w 1d ago
BW Weight: 0.02% of Network | 209 Mbit/s Observed By Relay
Version: 0.4.9.13 Recommended

Issues Detected:

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
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: 80.208.58.219.static.fibianet.dk
80.208.58.219:9001

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Denmark
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS44869
AS Name: FIBIA P/S (BGP.tools)
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, 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
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	Meets (9/9 DA)	184.0 Mbit/s – 376.0 Mbit/s (5 DA measured) 80.0 Mbit/s (3 DA relay-reported) 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	Partial (8/9 DA)	Median: 27.5d (9/9 DA above threshold) Min/Max: 24.3d / 1574.0d (9/9 DA, Voting / Total Eligible)	≥5.2d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8784.9d
Stable	Uptime	Below (0/9 DA)	2.9d (R)	≥3.3d - 3.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 184.0 Mbit/s – 376.0 Mbit/s (5 DA measured) 80.0 Mbit/s (3 DA relay-reported) 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	Meets (9/9 DA)	9/9 DA assigned Stable	≥5.2d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8784.9d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (9/9 DA)	Median: 99.8% (9/9 DA above threshold) Min/Max: 99.6% / 99.9% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 29.1d (9/9 DA above threshold) Min/Max: 9.6d / 30.1d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 184.0 Mbit/s – 376.0 Mbit/s (5 DA measured) 80.0 Mbit/s (3 DA relay-reported) 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	Meets (9/9 DA)	9/9 DA assigned Stable	≥5.2d - 10.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8784.9d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (9/9 DA)	Median: 99.8% (9/9 DA above threshold) Min/Max: 99.6% / 99.9% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 29.1d (9/9 DA above threshold) Min/Max: 9.6d / 30.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Partial (8/9 DA)	184.0 Mbit/s – 376.0 Mbit/s (5 DA measured) 80.0 Mbit/s (3 DA relay-reported) 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 12:45:05).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 209.50 Mbit/s
Advertised Bandwidth: 209.50 Mbit/s
Rate Limit: 503.32 Mbit/s
Burst Limit: 671.09 Mbit/s
Total Data: 191 TB (6 months)
1mo: 72 TB | 6mo: 191 TB

Measurement (Directory Authority Verified)

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

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight: 248.0 Mbit/s (median of 5 measurements)
Measured Min / Max: 184.0 Mbit/s / 376.0 Mbit/s
Deviation: 192.0 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0154% of network (76th pctl) | Guard: N/A | Middle: 0.0451% (91th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 20h 33m ago
Overall Uptime (1M/6M/1Y/5Y): 98.3%/99.5%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (98.3%/99.5%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 3mo 1w 1d ago (2026-07-05 19:00:00)
Last Seen: 1h 45m 38s ago (2026-10-12 12:00:00)
Last Restarted: 2d 20h 33m ago (2026-10-09 17:12:21)
Last Changed Address: 2026-07-05 19:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-12 05:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: myemail@example.com

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

91B4A814EB50F5231297AF2A6607F7E9E95A3330 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.13 on Linux
Version: 0.4.9.13 — 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

Full Exit Policy

reject *:*

Last fetch was at Mon, 12 Oct 2026 13:45:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-12 12: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, Stable	184.0 Mbit/s (M) \| 816.0 Kbit/s	184.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	99.8% \| 98%	27.2d \| 8d	25.1d \| 10.8d	2.9d \| 3.3d	99.8% \| 98.0%	27.2d \| 1.0d	2026-10-11 23:12:47	184.0 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast, Stable	376.0 Mbit/s (M) \| 816.0 Kbit/s	376.0 Mbit/s (M) \| 280.0 Mbit/s OR 16.8 Mbit/s	99.8% \| 98%	30.1d \| 8d	27.7d \| 5.2d	2.9d \| 3.3d	99.8% \| 98.0%	30.1d \| 1.0d	2026-10-11 23:12:47	376.0 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, 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	99.9% \| 98%	29.7d \| 8d	27.5d \| 10.9d	2.9d \| 3.3d	99.9% \| 98.0%	29.7d \| 1.0d	2026-10-11 23:12:47	80.0 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast, Stable	not published \| 816.0 Kbit/s	not published \| 280.0 Mbit/s OR 16.8 Mbit/s	99.8% \| 98%	30.1d \| 8d	27.7d \| 11.8d	2.9d \| 3.3d	99.8% \| 98.0%	30.1d \| 1.0d	2026-10-11 23:12:47	80.0 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast, Stable	288.0 Mbit/s (M) \| 816.0 Kbit/s	288.0 Mbit/s (M) \| 264.0 Mbit/s OR 16.8 Mbit/s	99.8% \| 98%	28.5d \| 8d	26.4d \| 10.8d	2.9d \| 3.3d	99.8% \| 98.0%	28.5d \| 1.0d	2026-10-11 23:12:47	288.0 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, 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	99.8% \| 98%	29.1d \| 8d	26.7d \| 11.2d	2.9d \| 3.3d	99.8% \| 98.0%	29.1d \| 1.0d	2026-10-11 23:12:47	80.0 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Running, Valid, 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	99.8% \| 98%	26.4d \| 8d	24.3d \| 10.6d	2.9d \| 3.3d	99.8% \| 98.0%	26.4d \| 1.0d	2026-10-11 23:12:47	80.0 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast, Stable	216.0 Mbit/s (M) \| 8.4 Mbit/s	216.0 Mbit/s (M) \| 200.0 Mbit/s OR 16.8 Mbit/s	99.6% \| 98%	9.6d \| 8d	1574.0d \| 8784.9d	2.9d \| 3.3d	99.6% \| 98.0%	9.6d \| 9.8d	2026-10-11 23:12:47	216.0 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast, Stable	248.0 Mbit/s (M) \| 816.0 Kbit/s	248.0 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	99.8% \| 98%	30.1d \| 8d	27.7d \| 11.3d	2.9d \| 3.3d	99.8% \| 98.0%	30.1d \| 1.0d	2026-10-11 23:12:47	248.0 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.