Tor Relays :: JAEN

View Relay "JAEN"

Family: 2 relays | Donny <[email protected]> | AS63949 | Singapore | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Exit, Fast, Running, V2Dir, Valid (5)
BW Verified: 5/6 BW Auths Measured 16 Kbit/s Median
Stability: Not Overloaded | UP 3d 6h 29m ago | UP 100% (1M)

Reachability: IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen: 1y 10mo 2w ago
BW Weight: 0.00% of Network | 28 Mbit/s Observed By Relay
Version: 0.4.8.16 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).
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.
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.8.16 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.

Connectivity and Location

Addresses

OR Address: tor-exit.triggersolutions.au
172.104.182.84:9001
[2400:8901::f03c:94ff:fe7f:59f6]:9001
Exit Address: 172.104.182.84

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 7/7 (2 don't test)

Location

Country: Singapore
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS63949
AS Name: Akamai Technologies, Inc. (BGP.tools)

Flags and Eligibility

Current Flags (5): Exit, Fast, Running, V2Dir, Valid

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Guard	WFU	Meets	99.4% (DA)	≥98% (all authorities)
	Time Known	Meets	17.3 days (DA)	≥8 days (all authorities)
	Bandwidth	Meets (≥2 MB/s)	28.8 Mbit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable	MTBF	Below	17 days (DA)	≥26.6d - 45.4d (varies)
Stable	Uptime	Below	3.3d (R)	≥19.1d - 19.7d (varies)
Fast	Speed	Meets (≥100 KB/s)	28.8 Mbit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir	WFU	Meets	99.4% (DA)	≥98.0%
HSDir	Time Known	Meets	17.3 days (DA)	≥1.0d (most) / 9.9d (max)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname

JAEN

Fingerprint

9489864F831668000BFEEAEE440DB25581275F4E

AROI (?)

none

Contact

Donny <[email protected]>

IPv4 Exit Policy Summary

accept: 
  80
  119
  443
  6660-6667

IPv6 Exit Policy Summary

none

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 172.104.182.84:*
accept *:6660-6667
accept *:119
accept *:443
accept *:80
reject *:*

Effective Family Members: 2 (View)

9489864F831668000BFEEAEE440DB25581275F4E
963E9B85071A5F9FD28A445158A602821557A67C

Alleged Family Members: 0

none

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 28.76 Mbit/s | 28.76 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.00% | N/A | N/A | 0.00%
OR Address: tor-exit.triggersolutions.au | 172.104.182.84:9001, [2400:8901::f03c:94ff:fe7f:59f6]:9001
Exit Address: none
Dir Address: none
Country: Singapore
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS63949 | Akamai Technologies, Inc. (BGP.tools)
Flags: 5: Exit Fast Running V2Dir Valid
Flag Uptime (1M/6M/1Y/5Y): —/—/—/90.5%
Uptime (1M/6M/1Y/5Y): 100.0%/100.0%/100.0%/90.7%
Uptime / Downtime: UP 3d 6h 29m ago
Seen (First | Last): 1y 10mo 2w ago (2024-02-25 04:00:00) | 1h 54m 58s ago (2026-01-10 03:00:00)
Last Restarted: 3d 6h 37m ago (2026-01-06 22:17:34)
Last Changed Address or Port: 2025-12-17 17:00:00
Hibernating: No
Platform (Short | Long): Linux | Tor 0.4.8.16 on Linux
Version (Running | Recommended | Status): 0.4.8.16 | No | obsolete

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
Flag Eligibility (need ≥5/9 for flag): Guard: 9/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
Consensus Weight (Dir. Auth.): Median: 16.0 Kbit/s | Min: 3920 bit/s | Max: 28.8 Kbit/s [Warning] High deviation
Identified Issues:
- 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).
- 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.
- 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.8.16 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.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric	Dir Auth Measured	Dir Auth Threshold	Status
In Consensus (Dir. Auth.)	9/9 authorities	≥5/9 (majority)	IN CONSENSUS
Running (IPv4 Reachable)	9/9 authorities reached this relay	≥5/9 (majority)	RUNNING
Valid	9/9 (Running + Valid Descriptor)	≥5/9 (majority)	VALID
Consensus Weight (Dir. Auth.)	16.0 Kbit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	99.4%	≥98% (all authorities)	MEETS
Guard TK (Dir. Auth., tk)	17.3 days	≥8 days (all authorities)	MEETS
Guard BW (Relay Reported)	28.8 Mbit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s	MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported)	3.3d	≥19.1d - 19.7d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	17 days	≥26.6d - 45.4d (typical) [Stricter] moria1: ≥376.2d	BELOW - 1/9
Fast Speed (Relay Reported)	28.8 Mbit/s	≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical) [Stricter] moria1: ≥8.4 Mbit/s	MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu)	99.4%	≥98.0% (from all auths)	PARTIAL - 8/9
HSDir TK (Dir. Auth., tk)	17.3 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.9d	PARTIAL - 8/9
IPv6 Reachable (Dir. Auth.)	7/7 tested	≥4/7 (majority)	REACHABLE

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	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	Y	Yes	Yes	Exit, Fast, Running, V2Dir, Valid	28.8 Mbit/s \| 816.0 Kbit/s	28.8 Mbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	99.4% \| 98%	17.3d \| 8d	4.3d \| 47.0d	3.3d \| 19.7d	99.4% \| 98.0%	17.3d \| 1.0d	2026-01-09 22:17:45	16.0 Kbit/s
dannenberg (DE)	Yes	Yes	N	Yes	Yes	Exit, Fast, Running, V2Dir, Valid	28.8 Mbit/s \| 816.0 Kbit/s	28.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	19.0d \| 8d	3.6d \| 35.7d	3.3d \| 20.2d	99.2% \| 98.0%	19.0d \| 1.0d	2026-01-09 22:17:45	28.8 Kbit/s
dizum (NL)	Yes	Yes	N	Yes	—	Exit, Fast, Running, V2Dir, Valid	28.8 Mbit/s \| 816.0 Kbit/s	28.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.5% \| 98%	14.8d \| 8d	4.7d \| 26.6d	3.3d \| 20.4d	99.5% \| 98.0%	14.8d \| 1.0d	2026-01-09 22:17:45	28.8 Kbit/s
faravahar (US)	Yes	Yes	N	Yes	Yes	Exit, Fast, Running, V2Dir, Valid	28.8 Mbit/s \| 816.0 Kbit/s	28.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	16.5d \| 8d	3.8d \| 41.9d	3.3d \| 19.1d	99.2% \| 98.0%	16.5d \| 1.0d	2026-01-09 22:17:45	28.8 Kbit/s
gabelmoo (DE)	Yes	Yes	Y	Yes	Yes	Exit, Fast, Running, Stable, V2Dir, Valid	28.8 Mbit/s \| 816.0 Kbit/s	28.8 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	77.5d \| 8d	17.0d \| 45.4d	3.3d \| 19.6d	99.9% \| 98.0%	77.5d \| 1.0d	2026-01-09 22:17:45	8.8 Kbit/s
longclaw (US)	Yes	Yes	Y	Yes	—	Exit, Fast, Running, V2Dir, Valid	28.8 Mbit/s \| 816.0 Kbit/s	28.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.5% \| 98%	18.8d \| 8d	4.8d \| 48.7d	3.3d \| 19.5d	99.5% \| 98.0%	18.8d \| 1.0d	2026-01-09 22:17:45	28.8 Kbit/s
maatuska (SE)	Yes	Yes	Y	Yes	Yes	Exit, Fast, Running, V2Dir, Valid	28.8 Mbit/s \| 816.0 Kbit/s	28.8 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	99.7% \| 98%	18.8d \| 8d	4.4d \| 42.3d	3.3d \| 19.4d	99.7% \| 98.0%	18.8d \| 1.0d	2026-01-09 22:17:45	3920 bit/s
moria1 (US)	Yes	Yes	Y	Yes	Yes	Exit, Fast, Running, Stable, V2Dir, Valid	28.8 Mbit/s \| 8.4 Mbit/s	28.8 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	99.5% \| 98%	9.8d \| 8d	12158.0d \| 376.2d	3.3d \| 20.4d	99.5% \| 98.0%	9.8d \| 9.9d	2026-01-09 22:17:45	16.0 Kbit/s
tor26 (AT)	Yes	Yes	Y	Yes	Yes	Exit, Fast, Running, Stable, V2Dir, Valid	28.8 Mbit/s \| 816.0 Kbit/s	28.8 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	99.8% \| 98%	19.0d \| 8d	7.9d \| 51.8d	3.3d \| 19.7d	99.8% \| 98.0%	19.0d \| 1.0d	2026-01-09 22:17:45	9.6 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). This is your relay's self-reported uptime from its 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.