View Relay "juliansTorNode"

Fingerprint: `FE623DA4EB2BA72791D9AA11AF7C929905F74832` | Family: 1 relay | juliantor(at)pm(dot)me [tor-relay.co] | AS3320 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast (4)
BW Verified: 5/7 BW Auths Measured 5600 bit/s Median
Stability: Overloaded | UP 1d 13h 59m ago | UP 100% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 1w 1d 13h ago
BW Weight: 0.00% of Network | 11 Mbit/s Observed By Relay
Version: 0.4.9.12 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: bandwidth below threshold : Observed bandwidth 12 Mbit/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
Guard: WFU below threshold : Weighted Fractional Uptime 28.5% 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 28.5% 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.
Write Bandwidth Limit Hit : Write rate limit (10 Mbit/s) was hit 9 times. Relay is throttling outbound traffic.
Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
Read Bandwidth Limit Hit : Read rate limit (10 Mbit/s) was hit 830 times. Relay is throttling inbound traffic.
Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.

Notes:

Rate Limit Configuration: Configured limits: Rate=10 Mbit/s, Burst=3.3 MB. Limits hit: Write=9, Read=830.

Connectivity and Location

Addresses

OR Address: p4ff1e527.dip0.t-ipconnect.de
79.241.229.39:9001

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS3320
AS Name: Deutsche Telekom AG (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.17% consensus weight, 45 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
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)	11.6 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 (2/9 DA)	Median: 4.0d (1/9 DA above threshold) Min/Max: 3.9d / 9619.5d (9/9 DA, Voting / Total Eligible)	≥3.2d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8518.3d
Stable	Uptime	Below (0/9 DA)	1.6d (R)	≥8.9d - 9.0d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/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 (2/9 DA)	2/9 DA assigned Stable	≥3.2d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8518.3d
	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: 28.6% (0/9 DA above threshold) Min/Max: 28.2% / 57.4% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 26.0d (9/9 DA above threshold) Min/Max: 9.9d / 26.1d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (8/9 DA)	8/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 (2/9 DA)	2/9 DA assigned Stable	≥3.2d - 12.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥8518.3d
	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: 28.6% (0/9 DA above threshold) Min/Max: 28.2% / 57.4% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 26.0d (9/9 DA above threshold) Min/Max: 9.9d / 26.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	11.6 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	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-09-22 00:15:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 11.58 Mbit/s
Advertised Bandwidth: 10.49 Mbit/s
Rate Limit: 10.49 Mbit/s
Burst Limit: 26.21 Mbit/s
Total Data: 973 GB (1 month)

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-09-22 00:15:10

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement: 5600 bit/s
Min / Max: 1040 bit/s / 10.5 Kbit/s
Deviation: 9.4 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0001% of network (6th pctl) | Guard: N/A | Middle: 0.0003% (7th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 1d 13h 59m ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 1w 1d 13h ago (2026-09-13 11:00:00)
Last Seen: 1h 15m 50s ago (2026-09-21 23:00:00)
Last Restarted: 1d 13h 59m ago (2026-09-20 10:15:55)
Last Changed Address: 2026-09-20 11:00:00

[Warning] OVERLOADED — Rate limits hit W:9 R:830 (limit: 10 Mbit/s)

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: Not Reported

Rate Limits (from /bandwidth)

Rate Limit: 10.49 Mbit/s
Burst Limit: 3.3 MB
Write Limit Hit: 9 times
Read Limit Hit: 830 times
Last Reported: 22 hours ago

Recommendations

Consider increasing RelayBandwidthRate
Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-09-21 17:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: juliantor(at)pm(dot)me [tor-relay.co]

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

FE623DA4EB2BA72791D9AA11AF7C929905F74832 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.12 on Linux
Version: 0.4.9.12 — 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 Tue, 22 Sep 2026 00:15:47 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-09-22 00:15: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 (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	Running, Valid, V2Dir, Fast	11.6 Mbit/s \| 816.0 Kbit/s	11.6 Mbit/s \| 208.0 Mbit/s OR 16.0 Mbit/s	28.5% \| 98%	26.1d \| 8d	4.0d \| 12.0d	1.6d \| 9.0d	28.5% \| 98.0%	26.1d \| 1.0d	2026-09-21 22:28:57	5600 bit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable	11.6 Mbit/s \| 816.0 Kbit/s	11.6 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	28.2% \| 98%	25.9d \| 8d	3.9d \| 3.2d	1.6d \| 9.0d	28.2% \| 98.0%	25.9d \| 1.0d	2026-09-21 22:28:57	1040 bit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	11.6 Mbit/s \| 816.0 Kbit/s	11.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	28.7% \| 98%	25.9d \| 8d	4.0d \| 11.5d	1.6d \| 8.9d	28.7% \| 98.0%	25.9d \| 1.0d	2026-09-21 22:28:57	10.5 Kbit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	11.6 Mbit/s \| 816.0 Kbit/s	11.6 Mbit/s \| 328.0 Mbit/s OR 16.0 Mbit/s	28.5% \| 98%	26.1d \| 8d	4.0d \| 13.1d	1.6d \| 9.7d	28.5% \| 98.0%	26.1d \| 1.0d	2026-09-21 22:28:57	10.5 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	11.6 Mbit/s \| 816.0 Kbit/s	11.6 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	28.7% \| 98%	25.9d \| 8d	4.0d \| 12.2d	1.6d \| 9.0d	28.7% \| 98.0%	25.9d \| 1.0d	2026-09-21 22:28:57	1600 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	11.6 Mbit/s \| 816.0 Kbit/s	11.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	28.6% \| 98%	26.0d \| 8d	4.0d \| 13.2d	1.6d \| 8.9d	28.6% \| 98.0%	26.0d \| 1.0d	2026-09-21 22:28:57	10.5 Kbit/s
maatuska (SE)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	11.6 Mbit/s \| 816.0 Kbit/s	11.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	28.6% \| 98%	26.0d \| 8d	4.0d \| 11.0d	1.6d \| 8.9d	28.6% \| 98.0%	26.0d \| 1.0d	2026-09-21 22:28:57	10.5 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	11.6 Mbit/s \| 8.4 Mbit/s	11.6 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	57.4% \| 98%	9.9d \| 8d	9619.5d \| 8518.3d	1.6d \| 9.4d	57.4% \| 98.0%	9.9d \| 9.8d	2026-09-21 22:28:57	3280 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	11.6 Mbit/s \| 816.0 Kbit/s	11.6 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	28.5% \| 98%	26.0d \| 8d	4.0d \| 12.3d	1.6d \| 9.3d	28.5% \| 98.0%	26.0d \| 1.0d	2026-09-21 22:28:57	1120 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.