View Relay "trapExitNode"

Family: 1 relay | [email protected] | AS132203 | Brazil | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Running, V2Dir, Valid (4)
BW Verified
1/6 BW Auths Measured 816 bit/s Median
Stability
Not Overloaded | UP 2d 3h 1m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1d 8h 47m ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.2 MB/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 54.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.
  • Guard: Time Known below threshold : Time Known 1.3 days is below 8 days requirement (6.7 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • 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: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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: WFU below threshold : WFU 54.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.
  • Low bandwidth authority measurements : Only 1/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

Connectivity and Location

Addresses
OR Address
43.157.157.73:9001
Exit Address
43.157.157.73
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Brazil Brazil
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS132203
AS Name
Shenzhen Tencent Computer Systems Company Limited (BGP.tools)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Meets (≥100 KB/s) 1.6 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 0.1d (1/9 DA above threshold)
Min/Max: 0.1d / 17719.6d (9/9 DA, Voting / Total Eligible)		 ≥22.3d - 53.9d (varies)
[Stricter] moria1: ≥403.9d
Uptime Below 2.1d (R) ≥10.0d - 10.8d (varies)
HSDir Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 4/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 62.7% (0/9 DA above threshold)
Min/Max: 54.9% / 69.6% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Below Median: 1.3d (0/9 DA above threshold)
Min/Max: 1.2d / 1.3d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below 4/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 62.7% (0/9 DA above threshold)
Min/Max: 54.9% / 69.6% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Below (need 6.7 more days) Median: 1.3d (0/9 DA above threshold)
Min/Max: 1.2d / 1.3d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 1.6 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 11:45:07).

Last fetch was at Thu, 29 Jan 2026 11:45:43 GMT.

Nickname
trapExitNode
Fingerprint
655FD6EA5DD37B000B1F37C3D569B518ACC39978
AROI (?)
none
Contact
[email protected]
IPv4 Exit Policy Summary 
accept: 
  80
  443
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 43.157.157.73:*
accept *:80
accept *:443
reject *:*
Effective Family Member: 1 
655FD6EA5DD37B000B1F37C3D569B518ACC39978
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
1.63 Mbit/s | 819.20 Kbit/s| 819.20 Kbit/s| 1.64 Mbit/s  Not Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | 0.00%
OR Address
43.157.157.73:9001
Exit Address
none
Dir Address
none
Country
Brazil Brazil
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS132203 | Shenzhen Tencent Computer Systems Company Limited (BGP.tools)
Flags: 4
Exit Exit Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 2d 3h 1m ago
Seen (First | Last)
1d 8h 47m ago (2026-01-28 03:00:00) | 1h 47m 15s ago (2026-01-29 10:00:00)
Last Restarted
2d 3h 2m ago (2026-01-27 08:44:39)
Last Changed Address or Port
2026-01-28 03:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status)
0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-29 11:45:07).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 816 bit/s | Min: 24 bit/s | Max: 816 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.2 MB/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 54.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.
    • Guard: Time Known below threshold: Time Known 1.3 days is below 8 days requirement (6.7 more days needed)
      • Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
    • 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: requires Fast flag: Guard flag requires having the Fast flag first
      • Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
    • 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: WFU below threshold: WFU 54.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.
    • Low bandwidth authority measurements: Only 1/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
      • Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

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.) 816 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 62.7% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 1.3 days ≥8 days (all authorities) BELOW - need 6.7 more days
Guard BW (Relay Reported) 1.6 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 2.1d ≥10.0d - 10.8d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 0 days ≥22.3d - 53.9d (typical)
[Stricter] moria1: ≥403.9d 		BELOW - 1/9
Fast Speed (Relay Reported) 1.6 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) 62.7% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 1.3 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.8d 		BELOW - 0/9

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 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 Valid, V2Dir, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 54.9% | 98% 1.3d | 8d 0.1d | 50.5d 2.1d | 11.4d 54.9% | 98.0% 1.3d | 1.0d 2026-01-29 03:15:49 816 bit/s
dannenberg (DE) Yes Yes N Yes Valid, V2Dir, Fast, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 62.3% | 98% 1.3d | 8d 0.1d | 22.3d 2.1d | 10.8d 62.3% | 98.0% 1.3d | 1.0d 2026-01-29 03:15:49 816 bit/s
dizum (NL) Yes Yes N Yes Valid, V2Dir, Fast, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 69.6% | 98% 1.3d | 8d 0.1d | 34.8d 2.1d | 10.9d 69.6% | 98.0% 1.3d | 1.0d 2026-01-29 03:15:49 816 bit/s
faravahar (US) Yes Yes N Yes Valid, V2Dir, Fast, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 63.7% | 98% 1.3d | 8d 0.1d | 47.4d 2.1d | 10.0d 63.7% | 98.0% 1.3d | 1.0d 2026-01-29 03:15:49 816 bit/s
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 65.8% | 98% 1.2d | 8d 0.1d | 53.9d 2.1d | 10.9d 65.8% | 98.0% 1.2d | 1.0d 2026-01-29 03:15:49 816 bit/s
longclaw (US) Yes Yes Y Yes Valid, V2Dir, Fast, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 60.5% | 98% 1.3d | 8d 0.1d | 55.1d 2.1d | 10.2d 60.5% | 98.0% 1.3d | 1.0d 2026-01-29 03:15:49 816 bit/s
maatuska (SE) Yes Yes Y Yes Valid, V2Dir, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 69.5% | 98% 1.3d | 8d 0.2d | 55.2d 2.1d | 10.1d 69.5% | 98.0% 1.3d | 1.0d 2026-01-29 03:15:49 24 bit/s
moria1 (US) Yes Yes Y Yes Running, Valid, V2Dir, Stable, Exit 1.6 Mbit/s | 8.4 Mbit/s 1.6 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 62.7% | 98% 1.2d | 8d 17719.6d | 403.9d 2.1d | 10.6d 62.7% | 98.0% 1.2d | 9.8d 2026-01-29 03:15:49 816 bit/s
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir, Exit 1.6 Mbit/s | 816.0 Kbit/s 1.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 61.3% | 98% 1.3d | 8d 0.1d | 55.8d 2.1d | 11.9d 61.3% | 98.0% 1.3d | 1.0d 2026-01-29 03:15:49 816 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). 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.