View Relay "slotor02"

Fingerprint: `720ABE4554C55EE6F6099491CA55D1F5550512C5` | Family: 4 relays | sloetor@gmail.com | AS16276 | 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 576 Mbit/s Median
Stability: Overloaded | UP 3w 1d 4h ago | UP 98% (1M)

Reachability: IPv4: 9/9 | v6: None configured(Directory Auths)
First Seen: 4y 9mo 3w ago
BW Weight: 0.04% of Network | 258 Mbit/s Observed By Relay
Version: 0.4.9.11 Not 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.
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.
General Overload Active : Relay reported general overload at 2026-11-03 18:00 UTC. Reported timestamps use hour precision, so the displayed minute is not an exact incident time. The flag does not identify which trigger fired. Investigation paths are Tor's internal OOM handling, dropped ntor onionskins, and TCP port exhaustion.
Suggestion: Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself. MetricsPort: tor_relay_load_oom_bytes_total. Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired. MetricsPort: tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}. Compare each with the matching action="processed" series. Inspect both supported handshake types. Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks. MetricsPort: tor_relay_load_tcp_exhaustion_total. An increase records additional exhaustion events. See the Tor overload troubleshooting guide.

Notes:

Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at maatuska (98.0%, need ≥98%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu.

Connectivity and Location

Addresses

OR Address: vps-485bf31f.vps.ovh.net
135.125.202.252:9001

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: None configured

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS16276
AS Name: OVH SAS (BGP.tools)
AS Rarity: Common (score: 0/5, 13.14% consensus weight, 187 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
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)	232.0 Mbit/s – 960.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.8d (1/9 DA above threshold) Min/Max: 2.3d / 12014.7d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d
Stable	Uptime	Meets (9/9 DA)	22.2d (R)	≥5.2d - 5.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast 232.0 Mbit/s – 960.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.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)	22.2d (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 232.0 Mbit/s – 960.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.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	Partial (8/9 DA)	Median: 98.8% (8/9 DA above threshold) Min/Max: 97.1% / 99.0% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.86% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 13.9d (9/9 DA above threshold) Min/Max: 9.8d / 14.3d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	232.0 Mbit/s – 960.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: 258.67 Mbit/s
Advertised Bandwidth: 258.67 Mbit/s
Rate Limit: 1.47 Gbit/s
Burst Limit: 2.05 Gbit/s
Total Data: 5.3 PB (5 years)
1mo: 90 TB | 6mo: 769 TB | 1y: 1.5 PB | 5y: 5.3 PB

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: 576.0 Mbit/s (median of 5 measurements)
Measured Min / Max: 232.0 Mbit/s / 960.0 Mbit/s
Deviation: 728.0 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0377% of network (95th pctl) | Guard: 0.0786% (92th pctl) | Middle: 0.0325% (87th pctl) | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 3w 1d 4h ago
Overall Uptime (1M/6M/1Y/5Y): 98.7%/99.1%/99.5%/99.3%
Flag Uptime (1M/6M/1Y/5Y): 47.7%/89.3%/94.8%/97.9%
Hibernating: No

Timestamps

First Seen: 4y 9mo 3w ago (2022-01-13 00:00:00)
Last Seen: 2h 15m 39s ago (2026-11-04 15:00:00)
Last Restarted: 3w 1d 4h ago (2026-10-13 12:19:33)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — General overload at 2026-11-03 18:00 UTC

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).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

General Overload (from /details)

Status: Reported
When: 2026-11-03 18:00 UTC (23 hours ago)

The general-overload flag does not say which trigger fired. Possible paths are Tor’s internal memory handling, dropped ntor handshakes, and TCP port exhaustion. Allium treats a valid report as eligible for 72 hours; that cutoff is not proof the relay recovered then.

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: —

What to check

Tor internal memory pressure
Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself.

MetricsPort: tor_relay_load_oom_bytes_total — Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill.
ntor handshake pressure
Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired.

MetricsPort: tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"} — Compare each with the matching action="processed" series. Inspect both supported handshake types.
TCP port exhaustion
Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks.

MetricsPort: tor_relay_load_tcp_exhaustion_total — An increase records additional exhaustion events.

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: sloetor@gmail.com

Family Configuration

Family Support: MyFamily Only (4) — Legacy only. Consider migrating to Happy Families. | View Full Family (4)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 4

1A72CD02E538D20E6D55E7410B18A8A0943627AB
1E326EFE355AB98912272AF724D59176B5C23792
49604A7CC7E80AB3D518AFC3E95B2EA265532719
720ABE4554C55EE6F6099491CA55D1F5550512C5 (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

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	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	Running, Valid, V2Dir, Fast	416.0 Mbit/s (M) \| 816.0 Kbit/s	416.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	98.7% \| 98%	13.3d \| 8d	4.8d \| 8.4d	22.2d \| 5.2d	2026-11-03 20:16:08	416.0 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast, Stable, HSDir, Guard	656.0 Mbit/s (M) \| 816.0 Kbit/s	656.0 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	99.0% \| 98%	14.2d \| 8d	6.0d \| 9.4d	22.2d \| 5.5d	2026-11-04 14:16:09	656.0 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	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	97.1% \| 98%	14.0d \| 8d	4.8d \| 6.8d	22.2d \| 5.5d	2026-11-04 14:16:09	80.0 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	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	98.8% \| 98%	13.2d \| 8d	4.4d \| 6.5d	22.2d \| 5.5d	2026-11-04 14:16:09	80.0 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	960.0 Mbit/s (M) \| 816.0 Kbit/s	960.0 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	99.0% \| 98%	14.3d \| 8d	6.0d \| 10.8d	22.2d \| 5.5d	2026-11-04 14:16:09	960.0 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	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	98.9% \| 98%	14.1d \| 8d	5.8d \| 10.9d	22.2d \| 5.3d	2026-11-03 20:16:08	80.0 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	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	98.0% \| 98%	13.0d \| 8d	2.3d \| 2.4d	22.2d \| 5.5d	2026-11-04 14:16:09	80.0 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	232.0 Mbit/s (M) \| 8.4 Mbit/s	232.0 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	98.5% \| 98%	9.8d \| 8d	12014.7d \| 7616.8d	22.2d \| 5.5d	2026-11-04 14:16:09	232.0 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	576.0 Mbit/s (M) \| 816.0 Kbit/s	576.0 Mbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	98.9% \| 98%	13.9d \| 8d	5.9d \| 10.7d	22.2d \| 5.5d	2026-11-04 14:16:09	576.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 "slotor02"

Fingerprint: 720ABE4554C55EE6F6099491CA55D1F5550512C5 | Family: 4 relays | sloetor@gmail.com | AS16276 | 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)

What to check

History

Operator Identity

Family Configuration

Full Exit Policy

Fingerprint: `720ABE4554C55EE6F6099491CA55D1F5550512C5` | Family: 4 relays | sloetor@gmail.com | AS16276 | Germany | Linux