View Relay "nil"

Fingerprint: `97E6A009185FCF2A58D884545E4E18FF612B7B06` | Family: 3 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/7 BW Auths Measured 14 Mbit/s Median
Stability: Overloaded | DOWN 5h 45m 39s ago | UP 38% (1M)

Reachability: IPv4: 9/9 | v6: None configured(Directory Auths)
First Seen: 11y 1mo 2w ago
BW Weight: 0.00% of Network | 35 Mbit/s Observed By Relay
Version: 0.4.9.14 Not 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.84099999999999%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 33.7%–36.9%.
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.
Tor version not recommended : Running Tor version 0.4.9.14 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.
File Descriptor Exhaustion : Relay reported file-descriptor exhaustion at 2026-11-04 02:00 UTC. Reported timestamps use hour precision, so the displayed minute is not an exact incident time.
Suggestion: Review socket-open errors, current file-descriptor and socket usage, and the running process’s effective descriptor limit. On systemd, inspect the actual Tor unit’s LimitNOFILE. On Linux, /proc/<pid>/limits shows that process limit. Running ulimit in a shell does not change an existing systemd service. After checking headroom, adjust the service limit only if the process is short of descriptors. MetricsPort: tor_relay_load_socket_total{state="opened"}. A current socket gauge. In the verified Tor release the unlabeled tor_relay_load_socket_total sample is Tor’s maximum socket value. That gauge is context, not an FD-exhaustion event counter.

Connectivity and Location

Addresses

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

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: None configured

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	Partial (8/9 DA)	13.6 Mbit/s – 40.8 Mbit/s (4 DA measured) 33.6 Mbit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0)	≥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: 0.1d (1/9 DA above threshold) Min/Max: 0.0d / 20751.5d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
Stable	Uptime	Meets (9/9 DA)	10.1d (R)	≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/9 DA assigned Fast 13.6 Mbit/s – 40.8 Mbit/s (4 DA measured) 33.6 Mbit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/9 DA)	1/9 DA assigned Stable	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	Uptime	Partial (6/9 DA)	10.1d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard	Prereq: Fast	Meets (8/9 DA)	8/9 DA assigned Fast 13.6 Mbit/s – 40.8 Mbit/s (4 DA measured) 33.6 Mbit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0)	≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/9 DA)	1/9 DA assigned Stable	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
	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: 34.8% (0/9 DA above threshold) Min/Max: 33.7% / 36.9% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 9.8d (9/9 DA above threshold) Min/Max: 9.6d / 10.0d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Partial (6/9 DA)	13.6 Mbit/s – 40.8 Mbit/s (4 DA measured) 33.6 Mbit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0)	≥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 12:45:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 35.11 Mbit/s
Advertised Bandwidth: 33.55 Mbit/s
Rate Limit: 33.55 Mbit/s
Burst Limit: 41.94 Mbit/s
Total Data: 267 TB (5 years)
1mo: 514 GB | 6mo: 2.1 TB | 1y: 3.9 TB | 5y: 267 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 12:45:10

Measured By: 4/7 Bandwidth Authorities
Not measured by: faravahar, longclaw, tor26
Consensus Weight: 14.4 Mbit/s (median of 4 measurements)
Measured Min / Max: 13.6 Mbit/s / 40.8 Mbit/s
Deviation: 27.2 Mbit/s [Warning] High variation

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

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: DOWN 5h 45m 39s ago
Overall Uptime (1M/6M/1Y/5Y): 39.0%/45.7%/54.5%/66.8%
Flag Uptime (1M/6M/1Y/5Y): 37.9%/45.0%/54.2%/66.6%
Hibernating: No

Timestamps

First Seen: 11y 1mo 2w ago (2015-09-23 12:00:00)
Last Seen: 5h 45m 39s ago (2026-11-04 08:00:00)
Last Restarted: 1w 3d 2h ago (2026-10-25 10:56:56)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — FD exhaustion (last: 2026-11-04 02:00)

Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h ago).

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

General Overload (from /details)

Status: No general overload report in available data

File Descriptor Exhaustion (from /bandwidth)

Status: Reported
When: 2026-11-04 02:00 UTC (11 hours ago)

Rate Limits (from /bandwidth)

Status: No rate-limit report in available data
Rate Limit: —
Burst Limit: —
Write counter: —
Read counter: —

What to check

File-descriptor exhaustion
Review socket-open errors, current file-descriptor and socket usage, and the running process’s effective descriptor limit. On systemd, inspect the actual Tor unit’s LimitNOFILE. On Linux, /proc/<pid>/limits shows that process limit. Running ulimit in a shell does not change an existing systemd service. After checking headroom, adjust the service limit only if the process is short of descriptors.

MetricsPort: tor_relay_load_socket_total{state="opened"} — A current socket gauge. In the verified Tor release the unlabeled tor_relay_load_socket_total sample is Tor’s maximum socket value. That gauge is context, not an FD-exhaustion event 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 04: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 (3) — Legacy only. Consider migrating to Happy Families. | View Full Family (3)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 3

97E6A009185FCF2A58D884545E4E18FF612B7B06 (this relay)
E78B8256253D0C45E5ECDE44B328863AB5123050
F4CEB15E9E34972675A9BE1370989701D7F7D5DA

Alleged Member: 1

(they don't list you back)

A77F16A6B3131EADB5D51DE2F8D0914F702AD357 (not in the network)

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.14 on Linux
Version: 0.4.9.14 — 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 13:45:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).

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	Valid, V2Dir, Fast	13.6 Mbit/s (M) \| 816.0 Kbit/s	13.6 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	36.9% \| 98%	10.0d \| 8d	0.1d \| 8.4d	10.1d \| 5.2d	2026-11-04 07:26:15	13.6 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	14.4 Mbit/s (M) \| 816.0 Kbit/s	14.4 Mbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	34.9% \| 98%	10.0d \| 8d	0.1d \| 9.3d	10.1d \| 5.3d	2026-11-04 10:57:20	14.4 Mbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	33.6 Mbit/s (R) \| 816.0 Kbit/s	33.6 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	33.7% \| 98%	9.6d \| 8d	0.1d \| 6.7d	10.1d \| 5.3d	2026-11-04 10:57:20	33.6 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	33.6 Mbit/s (R) \| 816.0 Kbit/s	33.6 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	33.7% \| 98%	10.0d \| 8d	0.0d \| 6.5d	10.1d \| 5.3d	2026-11-04 10:57:20	33.6 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	40.8 Mbit/s (M) \| 816.0 Kbit/s	40.8 Mbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	34.8% \| 98%	9.6d \| 8d	0.1d \| 10.8d	10.1d \| 5.3d	2026-11-04 10:57:20	40.8 Mbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast	33.6 Mbit/s (R) \| 816.0 Kbit/s	33.6 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	34.0% \| 98%	9.8d \| 8d	0.1d \| 10.9d	10.1d \| 5.3d	2026-11-04 07:26:15	33.6 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	33.6 Mbit/s (R) \| 816.0 Kbit/s	33.6 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	33.7% \| 98%	9.7d \| 8d	0.0d \| 2.4d	10.1d \| 5.3d	2026-11-04 10:57:20	33.6 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Valid, V2Dir, Fast, Stable	38.4 Mbit/s (M) \| 8.4 Mbit/s	38.4 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	35.1% \| 98%	9.6d \| 8d	20751.5d \| 7607.5d	10.1d \| 5.3d	2026-11-04 10:57:20	38.4 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	0 bit/s (U) \| 816.0 Kbit/s	0 bit/s (U) \| 256.0 Mbit/s OR 16.8 Mbit/s	35.7% \| 98%	9.9d \| 8d	0.1d \| 10.6d	10.1d \| 5.3d	2026-11-04 10:57:20	33.6 Mbit/s (R)

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 "nil"

Fingerprint: 97E6A009185FCF2A58D884545E4E18FF612B7B06 | Family: 3 relays | tsjk@hotmail.com | AS33885 | Sweden | 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: `97E6A009185FCF2A58D884545E4E18FF612B7B06` | Family: 3 relays | tsjk@hotmail.com | AS33885 | Sweden | Linux