Tor Relays :: nil

View Relay "nil"

Fingerprint: `97E6A009185FCF2A58D884545E4E18FF612B7B06` | Family: 4 relays | tsjk@hotmail.com | AS33885 | Sweden | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast (4)
BW Verified: 4/8 BW Auths Measured 33 Kbit/s Median
Stability: Overloaded | DOWN 3h 16m 26s ago | UP 51% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 10y 10mo 1w ago
BW Weight: 0.00% of Network | 34 Mbit/s Observed By Relay
Version: 0.4.9.11 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 : Weighted Fractional Uptime 69.9% is below 98% requirement
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 : Uptime or MTBF below network median for most authorities
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.
HSDir: WFU below threshold : WFU 69.9% below 98% required for HSDir
Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
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.
File Descriptor Exhaustion : Relay ran out of file descriptors at 2026-07-25 03:00 UTC. This severely impacts connections and performance.
Suggestion: Increase file descriptor limits: For systemd: add "LimitNOFILE=65535" to [Service] section. For shell: ulimit -n 65535. Persistent: edit /etc/security/limits.conf.

Notes:

Bandwidth authority measurements below majority: 4/8 bandwidth authorities measured this relay (majority is 5).

Connectivity and Location

Addresses

OR Address: 92-244-31-28.customers.ownit.se
92.244.31.28:59001

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Sweden
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS33885
AS Name: Telenor Sverige AB (BGP.tools)
AS Rarity: Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

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
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)	35.0 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	Below (1/9 DA)	Median: 0.2d (1/9 DA above threshold) Min/Max: 0.1d / 20648.5d (9/9 DA, Voting / Total Eligible)	≥8.0d - 12.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥9298.7d
Stable	Uptime	Below (0/9 DA)	6.5d (R)	≥7.2d - 7.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (6/9 DA)	6/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	Below (1/9 DA)	1/9 DA assigned Stable	≥8.0d - 12.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥9298.7d
	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: 69.9% (0/9 DA above threshold) Min/Max: 67.1% / 74.3% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 10.0d (7/9 DA above threshold) Min/Max: 4.2d / 10.4d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥10.0d
Guard	Prereq: Fast	Meets (6/9 DA)	6/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	Below (1/9 DA)	1/9 DA assigned Stable	≥8.0d - 12.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥9298.7d
	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: 69.9% (0/9 DA above threshold) Min/Max: 67.1% / 74.3% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (7/9 DA)	Median: 10.0d (7/9 DA above threshold) Min/Max: 4.2d / 10.4d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	35.0 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.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-07-25 10:15:09).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 34.98 Mbit/s
Advertised Bandwidth: 33.55 Mbit/s
Rate Limit: 33.55 Mbit/s
Burst Limit: 41.94 Mbit/s
Total Data: 287 TB (5 years)
1mo: 117 GB | 6mo: 1.6 TB | 1y: 3.9 TB | 5y: 287 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-25 10:15:09

Measured By: 4/8 Bandwidth Authorities
Not measured by: bastet, dannenberg, longclaw, maatuska
Median Measurement: 33.6 Kbit/s
Min / Max: 1520 bit/s / 49.6 Kbit/s
Deviation: 48.1 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0006% of network (13th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: DOWN 3h 16m 26s ago
Overall Uptime (1M/6M/1Y/5Y): 51.4%/56.1%/60.4%/69.7%
Flag Uptime (1M/6M/1Y/5Y): 48.7%/55.6%/59.9%/69.4%
Hibernating: No

Timestamps

First Seen: 10y 10mo 1w ago (2015-09-23 12:00:00)
Last Seen: 3h 16m 26s ago (2026-07-25 08:00:00)
Last Restarted: 6d 12h 44m ago (2026-07-18 22:31:36)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — FD exhaustion (last: 2026-07-25)

General Overload (from /details)

Status: Not Reported

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

File Descriptor Exhaustion (from /bandwidth)

Status: Reported — 2026-07-25 03:00 UTC (8 hours ago)

Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations

Increase FD limit: ulimit -n 65535
systemd: LimitNOFILE=65535 in [Service]

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-25 03:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: tsjk@hotmail.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

97E6A009185FCF2A58D884545E4E18FF612B7B06 (this relay)
A77F16A6B3131EADB5D51DE2F8D0914F702AD357
E78B8256253D0C45E5ECDE44B328863AB5123050
F4CEB15E9E34972675A9BE1370989701D7F7D5DA

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

reject: 
  1-65535

Full Exit Policy

reject *:*

Last fetch was at Sat, 25 Jul 2026 11:16:24 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-25 10:15:09).

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 (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	—	Y	Yes	Valid, V2Dir, Fast	35.0 Mbit/s \| 816.0 Kbit/s	35.0 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	69.9% \| 98%	10.4d \| 8d	0.2d \| 16.7d	6.5d \| 7.2d	69.9% \| 98.0%	10.4d \| 1.0d	2026-07-25 06:58:04	33.6 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir	35.0 Mbit/s \| 816.0 Kbit/s	35.0 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	69.9% \| 98%	10.1d \| 8d	0.2d \| 8.0d	6.5d \| 7.4d	69.9% \| 98.0%	10.1d \| 1.0d	2026-07-25 06:58:04	33.6 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Valid, V2Dir, Fast	35.0 Mbit/s \| 816.0 Kbit/s	35.0 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	70.0% \| 98%	10.3d \| 8d	0.2d \| 11.7d	6.5d \| 7.4d	70.0% \| 98.0%	10.3d \| 1.0d	2026-07-25 06:58:04	33.6 Kbit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast	35.0 Mbit/s \| 816.0 Kbit/s	35.0 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	70.5% \| 98%	10.2d \| 8d	0.2d \| 11.9d	6.5d \| 7.7d	70.5% \| 98.0%	10.2d \| 1.0d	2026-07-25 06:58:04	49.6 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast	35.0 Mbit/s \| 816.0 Kbit/s	35.0 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	74.3% \| 98%	4.2d \| 7d	0.2d \| 12.3d	6.5d \| 7.5d	74.3% \| 98.0%	4.2d \| 1.0d	2026-07-25 06:58:04	24.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir	35.0 Mbit/s \| 816.0 Kbit/s	35.0 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	68.8% \| 98%	5.8d \| 8d	0.2d \| 24.7d	6.5d \| 8.1d	68.8% \| 98.0%	5.8d \| 1.0d	2026-07-25 06:58:04	33.6 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir	35.0 Mbit/s \| 816.0 Kbit/s	35.0 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	67.1% \| 98%	9.9d \| 8d	0.1d \| 12.5d	6.5d \| 8.1d	67.1% \| 98.0%	9.9d \| 1.0d	2026-07-25 06:58:04	33.6 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast, Stable	35.0 Mbit/s \| 8.4 Mbit/s	35.0 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	67.8% \| 98%	10.0d \| 8d	20648.5d \| 9298.7d	6.5d \| 7.5d	67.8% \| 98.0%	10.04d \| 9.97d	2026-07-25 06:58:04	10.4 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast	35.0 Mbit/s \| 816.0 Kbit/s	35.0 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	70.2% \| 98%	10.0d \| 8d	0.2d \| 16.7d	6.5d \| 7.5d	70.2% \| 98.0%	10.0d \| 1.0d	2026-07-25 06:58:04	1520 bit/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.