View Relay "OnionSisterLisa"

Fingerprint: `A0C5ECF60EC6184A3E7F22688D05761279315EB5` | Family: 9 relays | AS24940 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, HSDir, Guard (7)
BW Verified: 5/7 BW Auths Measured 136 Mbit/s Median
Stability: Not Overloaded | UP 20h 31m 2s ago | UP 99% (1M)

Reachability: IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen: 6mo 3w 3d ago
BW Weight: 0.01% of Network | 95 Mbit/s Observed By Relay
Version: 0.4.9.15 Recommended

Issues Detected:

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: static.43.149.75.5.clients.your-server.de
5.75.149.43:23416
[2a01:4f8:c2c:241b::1]:23416

Reachability (Directory Authorities)

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

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS24940
AS Name: Hetzner Online GmbH (BGP.tools)
AS Rarity: Common (score: 0/5, 8.27% consensus weight, 240 operators)

Flags and Eligibility

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard

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)	80.0 Mbit/s – 200.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	Partial (8/9 DA)	Median: 27.8d (8/9 DA above threshold) Min/Max: 3.3d / 3835.4d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d
Stable	Uptime	Below (0/9 DA)	0.9d (R)	≥5.2d - 5.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 80.0 Mbit/s – 200.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 (9/9 DA)	9/9 DA assigned Stable	≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	Uptime	Partial (8/9 DA)	0.9d (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 80.0 Mbit/s – 200.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 (9/9 DA)	9/9 DA assigned Stable	≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (9/9 DA)	Median: 99.9% (9/9 DA above threshold) Min/Max: 99.1% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.86% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 35.2d (9/9 DA above threshold) Min/Max: 9.8d / 57.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	80.0 Mbit/s – 200.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 17:15:06).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 95.52 Mbit/s
Advertised Bandwidth: 83.89 Mbit/s
Rate Limit: 83.89 Mbit/s
Burst Limit: 125.83 Mbit/s
Total Data: 213 TB (1 year)
1mo: 33 TB | 6mo: 190 TB | 1y: 213 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 17:15:06

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight: 136.0 Mbit/s (median of 5 measurements)
Measured Min / Max: 80.0 Mbit/s / 200.0 Mbit/s
Deviation: 120.0 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0097% of network (64th pctl) | Guard: 0.0201% (57th pctl) | Middle: 0.0083% (62th pctl) | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 20h 31m 2s ago
Overall Uptime (1M/6M/1Y/5Y): 99.9%/100.0%/100.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): —/29.8%/29.9%/—
Hibernating: No

Timestamps

First Seen: 6mo 3w 3d ago (2026-04-14 13:00:00)
Last Seen: 2h 15m 39s ago (2026-11-04 15:00:00)
Last Restarted: 20h 31m 2s ago (2026-11-03 20:44:37)
Last Changed Address: 2026-04-14 13:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 17:15 UTC. /details snapshot 2026-11-04 15:00:00 UTC (cached 33s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 9h 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 08:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: none

Family Configuration

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

Happy Families (family-cert)

Effective Members: 9

1F25873E5339F3A11D18B1577019570C670BAD47
4377DD069D3DE316F5D6946856790EA6488D3AA4
5674EC15789CD0365BDA3C3CF0DD8789275D4ADA
8D350282DD61C1B9491E035D9B9CEEBD70F6A38F
95703FB111D37F28B79FE51EC9FD6267EE701A9E
A0C5ECF60EC6184A3E7F22688D05761279315EB5 (this relay)
AC4B15EB87159D713AC787FBC1702A776D7B4117
B8C974537B7135E418D55AF46384516A41AAFF3C
ED7CBA6BB8C2D82AFD66D7C82A5257C0B1C70545

MyFamily (legacy declarations) — 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 17:15:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 17:15:06).

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, HSDir, Guard	80.0 Mbit/s (M) \| 816.0 Kbit/s	80.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	99.9% \| 98%	31.3d \| 8d	20.8d \| 8.4d	0.9d \| 5.2d	2026-11-03 20:50:19	80.0 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Valid, V2Dir, Fast, Stable, HSDir, Guard	136.0 Mbit/s (M) \| 816.0 Kbit/s	136.0 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	99.9% \| 98%	22.6d \| 8d	13.9d \| 9.4d	0.9d \| 5.5d	2026-11-04 14:50:20	136.0 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	99.5% \| 98%	47.2d \| 8d	27.8d \| 6.8d	0.9d \| 5.5d	2026-11-04 14:50:20	80.0 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	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%	35.5d \| 8d	19.5d \| 6.5d	0.9d \| 5.5d	2026-11-04 14:50:20	80.0 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	200.0 Mbit/s (M) \| 816.0 Kbit/s	200.0 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	35.2d \| 8d	28.7d \| 10.8d	0.9d \| 5.5d	2026-11-04 14:50:20	200.0 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	N/T	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	56.2d \| 8d	45.4d \| 10.9d	0.9d \| 5.3d	2026-11-03 20:50:19	80.0 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	99.1% \| 98%	24.4d \| 8d	3.3d \| 2.4d	0.9d \| 5.5d	2026-11-04 14:50:20	80.0 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	88.0 Mbit/s (M) \| 8.4 Mbit/s	88.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	99.9% \| 98%	9.8d \| 8d	3835.4d \| 7616.8d	0.9d \| 5.5d	2026-11-04 14:50:20	88.0 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	168.0 Mbit/s (M) \| 816.0 Kbit/s	168.0 Mbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	100.0% \| 98%	57.1d \| 8d	46.6d \| 10.7d	0.9d \| 5.5d	2026-11-04 14:50:20	168.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 "OnionSisterLisa"

Fingerprint: A0C5ECF60EC6184A3E7F22688D05761279315EB5 | Family: 9 relays | AS24940 | Germany | 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: `A0C5ECF60EC6184A3E7F22688D05761279315EB5` | Family: 9 relays | AS24940 | Germany | Linux