View Relay "arbitraryTessa5"

Fingerprint: `485492A420AFDFFFBCCA05DFF317CDCA43052C11` | Operator: arbitrary.ch v3 (14 relays) ✓ Validated | Family: 14 relays | email:tor[]arbitrary.ch... | AS24940 | Finland | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast (4)
BW Verified: 5/7 BW Auths Measured 144 Mbit/s Median
Stability: Not Overloaded | UP 6d 23h 29m ago | UP 87% (1M)

Reachability: IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen: 4y 7mo 3w ago
BW Weight: 0.01% of Network | 95 Mbit/s Observed By Relay
Version: 0.4.9.15 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: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.87300000000001%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 86.6%–89.7%.
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 : 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 do not.
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.
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: tessa.arbitrary.ch
95.217.112.245:465
[2a01:4f9:4a:2e4e::2]:465

Reachability (Directory Authorities)

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

Location

Country: Finland
Interactive Map: View in RouteFluxMap

Autonomous System

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

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, 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 (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)	104.0 Mbit/s – 192.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: 5.2d (1/9 DA above threshold) Min/Max: 1.5d / 12082.1d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥7621.1d
Stable	Uptime	Meets (9/9 DA)	7.0d (R)	≥5.2d - 5.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 104.0 Mbit/s – 192.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 (5/9 DA)	5/9 DA assigned Stable	≥2.4d - 9.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥7621.1d
	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)	7.0d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 104.0 Mbit/s – 192.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 (5/9 DA)	5/9 DA assigned Stable	≥2.4d - 9.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥7621.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: 89.1% (0/9 DA above threshold) Min/Max: 86.6% / 89.7% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.87300000000001% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 13.6d (9/9 DA above threshold) Min/Max: 9.9d / 13.9d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	104.0 Mbit/s – 192.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 18:45:05).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 95.94 Mbit/s
Advertised Bandwidth: 95.94 Mbit/s
Rate Limit: 178.96 Mbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 3.0 PB (5 years)
1mo: 40 TB | 6mo: 283 TB | 1y: 600 TB | 5y: 3.0 PB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 18:45:05

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

Network Participation: Consensus Weight: 0.0093% of network (63th pctl) | Guard: N/A | Middle: 0.0272% (85th pctl) | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 6d 23h 29m ago
Overall Uptime (1M/6M/1Y/5Y): 87.1%/96.1%/97.8%/99.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (87.1%/96.1%/97.8%/99.0%)
Hibernating: No

Timestamps

First Seen: 4y 7mo 3w ago (2022-03-14 00:00:00)
Last Seen: 1h 45m 16s ago (2026-11-04 17:00:00)
Last Restarted: 6d 23h 29m ago (2026-10-28 19:15:53)
Last Changed Address: 2026-04-06 23:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 18:45 UTC. /details snapshot 2026-11-04 17:00:00 UTC (cached 21s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 11h 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 10:00 UTC

AROI Domain (?): arbitrary.ch
Operator Validation: Validated (14/14 relays)
This Relay: Validated (dns-familyid-ed25519)
Contact: email:tor[]arbitrary.ch url:arbitrary.ch proof:dns-familyid-ed25519 abuse:tor[]arbitrary.ch ciissversion:3

Family Configuration

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

Happy Families (family-cert)

Effective Members: 14

15291291D81E404FB6BEC16D366608590D2B0247
360A4AA120D8B2DF1E03FE6117F3A725DB4902F0
3F43D0584A2613C9DB631382FF486DC6B95EA1C8
409FDB0A3CEAA4FF20F4B8FA7F52AB0DE4338F56
485492A420AFDFFFBCCA05DFF317CDCA43052C11 (this relay)
4D70F05DD308A2EA5B671E440879BFADAC92860F
54FF87E18CF4B351BB078A640A4DC5265969485E
624B7391B9790E7CD2AF6A7238239BA3D6928A57
99D5C9A5A7238986D1EA1D7771CF81B4A192C4D0
A2CD32D9D0668DB764AD68C745CE29693CA851B9
ACAAE1708144F6485AAFFD59C3C6EAA1EA4AAAB2
C3F7F3E1E32A64B22B2F0734E7C7A312F993D102
D8056CAD4A3D6EE7D82748027474BF5C53E569D9
FA1845C313B88EF49E8BE1F23B02CD0AC702B636

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 18:45:16 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 18: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	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	176.0 Mbit/s (M) \| 816.0 Kbit/s	176.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	88.6% \| 98%	13.4d \| 8d	4.4d \| 8.4d	7.0d \| 5.2d	2026-11-03 19:16:08	176.0 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast	192.0 Mbit/s (M) \| 816.0 Kbit/s	192.0 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	89.7% \| 98%	13.8d \| 8d	4.7d \| 9.5d	7.0d \| 5.5d	2026-11-04 13:16:09	192.0 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	89.1% \| 98%	13.9d \| 8d	6.6d \| 6.8d	7.0d \| 5.5d	2026-11-04 13:16:09	80.0 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	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	88.7% \| 98%	12.7d \| 8d	3.8d \| 6.6d	7.0d \| 5.5d	2026-11-04 13:16:09	80.0 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	120.0 Mbit/s (M) \| 816.0 Kbit/s	120.0 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	89.6% \| 98%	13.9d \| 8d	5.3d \| 10.9d	7.0d \| 5.5d	2026-11-04 13:16:09	120.0 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	N/T	Running, Valid, V2Dir, Fast, Stable, HSDir	80.0 Mbit/s (R) \| 816.0 Kbit/s	80.0 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	89.6% \| 98%	13.7d \| 8d	5.3d \| 11.1d	7.0d \| 5.5d	2026-11-04 13:16:09	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	86.6% \| 98%	12.2d \| 8d	1.5d \| 2.4d	7.0d \| 5.5d	2026-11-04 13:16:09	80.0 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable	104.0 Mbit/s (M) \| 8.4 Mbit/s	104.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	86.7% \| 98%	9.9d \| 8d	12082.1d \| 7621.1d	7.0d \| 5.5d	2026-11-04 13:16:09	104.0 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	144.0 Mbit/s (M) \| 816.0 Kbit/s	144.0 Mbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	89.6% \| 98%	13.6d \| 8d	5.2d \| 10.8d	7.0d \| 5.5d	2026-11-04 13:16:09	144.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 "arbitraryTessa5"

Fingerprint: 485492A420AFDFFFBCCA05DFF317CDCA43052C11 | Operator: arbitrary.ch v3 (14 relays) ✓ Validated | Family: 14 relays | email:tor[]arbitrary.ch... | AS24940 | Finland | 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: `485492A420AFDFFFBCCA05DFF317CDCA43052C11` | Operator: arbitrary.ch v3 (14 relays) ✓ Validated | Family: 14 relays | email:tor[]arbitrary.ch... | AS24940 | Finland | Linux