View Relay "tortortor"

Fingerprint: `860669650E8486B4304E413912390B3E4222E7E7` | Family: 1 relay | lka_sucks@proton.me | AS51396 | Netherlands | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Fast, Stable, MiddleOnly, BadExit (6)
BW Verified: 6/7 BW Auths Measured 128 Kbit/s Median
Stability: Overloaded | UP 2w 4d 10h ago | UP 100% (1M)

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 1y 8mo 1w ago
BW Weight: 0.01% of Network | 190 Mbit/s Observed By Relay
Version: 0.4.9.11 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.
BadExit flag assigned : This relay has been flagged as a bad exit by directory authorities. BadExit means authorities detected malicious behavior (traffic modification, SSL stripping, etc.).
Suggestion: Contact bad-relays@lists.torproject.org to understand and resolve this issue.
MiddleOnly restriction active : This relay has been restricted to middle position only by directory authorities. MiddleOnly removes Guard, Exit, HSDir, and V2Dir flags, and adds BadExit. This significantly limits the relay's role in the network.
Suggestion: This may indicate suspicious behavior patterns, Sybil risk indicators, or policy violations. Contact bad-relays@lists.torproject.org for more information.
General Overload Active : Relay reported general overload at 2026-08-04 14:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses

OR Address: 176.65.148.149.ptr.pfcloud.network
176.65.148.149:443
[2a05:b0c7:6e37::1]:443

Reachability (Directory Authorities)

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

Location

Country: Netherlands
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS51396
AS Name: Pfcloud UG (haftungsbeschrankt) (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.29% consensus weight, 8 operators)

Flags and Eligibility

Current Flags (6): Running, Valid, Fast, Stable, MiddleOnly, BadExit

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	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)	190.3 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Partial (8/9 DA)	Median: 103.9d (9/9 DA above threshold) Min/Max: 17.1d / 186.3d (9/9 DA, Voting / Total Eligible)	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
Stable	Uptime	Meets (9/9 DA)	18.4d (R)	≥5.3d - 5.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/9 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
	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)	Majority: 100.0% (6/9 DA) Min/Med/Max: 99.9% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 86.2d (9/9 DA above threshold) Min/Max: 9.8d / 186.0d (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	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Meets (9/9 DA)	9/9 DA assigned Stable	≥9.9d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8501.8d
	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)	Majority: 100.0% (6/9 DA) Min/Med/Max: 99.9% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 86.2d (9/9 DA above threshold) Min/Max: 9.8d / 186.0d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	190.3 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit	Exit Policy	Partial (0/9 DA) (only port 80)	Port 80: Yes \| Port 443: Yes (R)	Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly	Restriction (by DA)	Flagged (9/9 DA)	9/9 authorities assigned MiddleOnly	Suspicious behavior, Sybil risk, or policy violation
BadExit	Restriction (by DA)	Flagged (5/9 DA)	5/9 authorities assigned BadExit	Exit traffic manipulation, SSL stripping, or policy violation

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-08-06 05:15:06).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 190.27 Mbit/s
Advertised Bandwidth: 190.27 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 200 TB (5 years)
1mo: 38 TB | 6mo: 70 TB | 1y: 143 TB | 5y: 200 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-06 05:15:06

Measured By: 6/7 Bandwidth Authorities
Not measured by: faravahar
Median Measurement: 128.0 Kbit/s
Min / Max: 80.0 Kbit/s / 344.0 Kbit/s
Deviation: 264.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0083% of network (63th pctl) | Guard: N/A | Middle: 0.0249% (84th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 2w 4d 10h ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/100.0%/95.3%/95.5%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (100.0%/100.0%/95.3%/95.5%)
Hibernating: No

Timestamps

First Seen: 1y 8mo 1w ago (2024-12-01 00:00:00)
Last Seen: 1h 16m 6s ago (2026-08-06 05:00:00)
Last Restarted: 2w 4d 10h ago (2026-07-18 20:09:01)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — General overload at 2026-08-04 14:00 UTC

General Overload (from /details)

Status: Reported
When: 2026-08-04 14:00 UTC (1 days ago)

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)

Status: Not Reported

Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations

Check CPU/memory: htop
Review MaxMemInQueues in torrc

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-05 22:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: lka_sucks@proton.me

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

860669650E8486B4304E413912390B3E4222E7E7 (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 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Not an exit relay — DNS health testing does not apply.

IPv4 Exit Policy Summary

IPv6 Exit Policy Summary

Full Exit Policy

reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 176.65.148.149:*
reject *:25
reject *:194
reject *:465
reject *:587
reject *:994
accept *:*

Last fetch was at Thu, 06 Aug 2026 06:16:05 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-08-06 05: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 (Relay\|T)	Guard BW (Relay\|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	Yes	N	Yes	Yes	Running, Valid, Fast, Stable, MiddleOnly	190.3 Mbit/s \| 816.0 Kbit/s	190.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	103.9d \| 8d	103.9d \| 12.2d	18.4d \| 5.5d	100.0% \| 98.0%	103.9d \| 1.0d	2026-08-05 20:10:43	80.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	Yes	Y	Yes	Yes	Running, Valid, Fast, Stable, MiddleOnly	190.3 Mbit/s \| 816.0 Kbit/s	190.3 Mbit/s \| 328.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	35.8d \| 8d	20.0d \| 10.6d	18.4d \| 5.6d	99.9% \| 98.0%	35.8d \| 1.0d	2026-08-05 20:10:43	344.0 Kbit/s
dizum (NL)	Yes	Yes	No	Yes	N	Yes	Yes	Running, Valid, Fast, Stable, MiddleOnly	190.3 Mbit/s \| 816.0 Kbit/s	190.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	86.2d \| 8d	86.2d \| 9.9d	18.4d \| 5.3d	100.0% \| 98.0%	86.2d \| 1.0d	2026-08-05 20:10:43	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	Yes	Y	Yes	Yes	Running, Valid, Fast, Stable, MiddleOnly, BadExit	190.3 Mbit/s \| 816.0 Kbit/s	190.3 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	36.2d \| 8d	35.3d \| 10.1d	18.4d \| 5.4d	99.9% \| 98.0%	36.2d \| 1.0d	2026-08-05 20:10:43	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	Yes	Y	Yes	Yes	Running, Valid, Fast, Stable, MiddleOnly, BadExit	190.3 Mbit/s \| 816.0 Kbit/s	190.3 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	30.2d \| 8d	17.1d \| 13.4d	18.4d \| 5.5d	100.0% \| 98.0%	30.2d \| 1.0d	2026-08-05 20:10:43	336.0 Kbit/s
longclaw (US)	Yes	Yes	No	Yes	Y	Yes	—	Running, Valid, Fast, Stable, MiddleOnly, BadExit	190.3 Mbit/s \| 816.0 Kbit/s	190.3 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	170.8d \| 8d	170.8d \| 17.3d	18.4d \| 5.5d	100.0% \| 98.0%	170.8d \| 1.0d	2026-08-05 20:10:43	128.0 Kbit/s
maatuska (SE)	Yes	Yes	No	Yes	Y	Yes	Yes	Running, Valid, Fast, Stable, MiddleOnly	190.3 Mbit/s \| 816.0 Kbit/s	190.3 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	107.3d \| 8d	107.3d \| 10.8d	18.4d \| 5.5d	100.0% \| 98.0%	107.3d \| 1.0d	2026-08-05 20:10:43	136.0 Kbit/s
moria1 (US)	Yes	Yes	No	Yes	Y	Yes	Yes	Running, Valid, Fast, Stable, MiddleOnly, BadExit	190.3 Mbit/s \| 8.4 Mbit/s	190.3 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	9.8d \| 8d	186.3d \| 8501.8d	18.4d \| 5.4d	100.0% \| 98.0%	9.84d \| 9.85d	2026-08-05 20:10:43	112.0 Kbit/s
tor26 (AT)	Yes	Yes	No	Yes	Y	Yes	Yes	Running, Valid, Fast, Stable, MiddleOnly, BadExit	190.3 Mbit/s \| 816.0 Kbit/s	190.3 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	186.0d \| 8d	186.0d \| 12.6d	18.4d \| 5.4d	100.0% \| 98.0%	186.0d \| 1.0d	2026-08-05 20:10:43	232.0 Kbit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.

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.