View Relay "TrujillosExit"

Fingerprint: 83BF46C486384BEBB1642925910930012B1C6A91 | Family: 1 relay | Tor volunteer david.e.trujillo... | AS263812 | Mexico | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast, Stable, Exit (5)
DNS Health
Healthy (15.3s, 53rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 68 Mbit/s Median
Stability
Not Overloaded | UP 1d 10h 50m ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen
2y 10mo 1w ago
BW Weight
0.00% of Network | 91 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
Issues Detected:
  • HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • 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.

Connectivity and Location

Addresses
OR Address
190.103.179.98:9001
[2800:ba0:6:c1::4858]:9001
Exit Address
190.103.179.98
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Mexico Mexico
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS263812
AS Name
S.A.S. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 10 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, Fast, Stable, Exit
Eligible Flags (6): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/9
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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 49.6 Mbit/s – 88.0 Mbit/s (5 DA measured)
80.0 Mbit/s (4 DA relay-reported)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (8/9 DA) Median: 58.2d (8/9 DA above threshold)
Min/Max: 8.4d / 347.3d (9/9 DA, Voting / Total Eligible)		 ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Uptime Below (0/9 DA) 1.5d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
49.6 Mbit/s – 88.0 Mbit/s (5 DA measured)
80.0 Mbit/s (4 DA relay-reported)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 1.5d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
49.6 Mbit/s – 88.0 Mbit/s (5 DA measured)
80.0 Mbit/s (4 DA relay-reported)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥2.4d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.5d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Median: 100.0% (9/9 DA above threshold)
Min/Max: 99.7% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 80.3d (9/9 DA above threshold)
Min/Max: 9.8d / 347.0d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 49.6 Mbit/s – 88.0 Mbit/s (5 DA measured)
80.0 Mbit/s (4 DA relay-reported)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (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
91.88 Mbit/s
Advertised Bandwidth
91.88 Mbit/s
Rate Limit
122.88 Mbit/s
Burst Limit
122.88 Mbit/s
Total Data
330 TB (5 years)
1mo: 24 TB | 6mo: 97 TB | 1y: 150 TB | 5y: 330 TB
Measurement (Directory Authority Verified)

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

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
68.8 Mbit/s (median of 5 measurements)
Measured Min / Max
49.6 Mbit/s / 88.0 Mbit/s
Deviation
38.4 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0034% of network (40th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0110% (18th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 5 years Throughput and write/read, last 30 days
1M 6M 1Y 5Y

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 10h 50m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/100.0%/100.0%/95.8%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/100.0%/100.0%/95.8%)
Hibernating
No
Timestamps
First Seen
2y 10mo 1w ago (2024-01-01 00:00:00)
Last Seen
2h 15m 38s ago (2026-11-04 11:00:00)
Last Restarted
1d 10h 50m ago (2026-11-03 02:24:57)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 5h 30m ago).

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
Status
No rate-limit report in available data
Rate Limit
—
Burst Limit
—
Write counter
—
Read 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
Uptime, last 6 months Uptime, last year Uptime, last 5 years Uptime, last 30 days
1M 6M 1Y 5Y

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
Tor volunteer david.e.trujillo <trujillosexit.proton.me>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
83BF46C486384BEBB1642925910930012B1C6A91 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.15 on Linux
Version
0.4.9.15 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Healthy (avg. 15.3s, 53rd percentile)
Query Domain
5580ca8738304b7ea92c5a9ef5d3dde2.83bf46c4.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Google (public resolver)
Google 100% (~34 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
showbiz (US) 1DBB29EBAD018432653C72B8D3BC713342F047A4
Exit Address Used
190.103.179.98
Per-Instance Results
Cross Validation Attempt 1: Success, 9.9s (cv1_w2)
Cross Validation Attempt 2: Success, 19.5s (cv2_w2)
Cross Validation Attempt 3: Success, 18.9s (cv3_w2)
Cross Validation Attempt 4: Success, 12.8s (cv4_w2)
Tested: 2026-11-03 20:09:44 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-21
  43
  53
  80
  110
  143
  220
  443
  873
  989-993
  995
  1194
  1293
  3690
  4321
  5222-5223
  5228
  9418
  11371
  64738
IPv6 Exit Policy Summary
None
Full 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 190.103.179.98:*
accept *:20-21
accept *:43
accept *:53
accept *:80
accept *:110
accept *:143
accept *:220
accept *:443
accept *:873
accept *:989-990
accept *:991
accept *:992
accept *:993
accept *:995
accept *:1194
accept *:1293
accept *:3690
accept *:4321
accept *:5222-5223
accept *:5228
accept *:9418
accept *:11371
accept *:64738
reject *:*

Last fetch was at Wed, 04 Nov 2026 13:15:37 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 v6 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 Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 88.0 Mbit/s (M) | 816.0 Kbit/s 88.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 33.2d | 8d 21.7d | 8.4d 1.5d | 5.2d 2026-11-03 20:25:04 88.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 49.6 Mbit/s (M) | 816.0 Kbit/s 49.6 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 49.1d | 8d 34.3d | 9.3d 1.5d | 5.3d 2026-11-03 20:25:04 49.6 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, Fast, Stable, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 85.5d | 8d 58.2d | 6.7d 1.5d | 5.3d 2026-11-03 20:25:04 80.0 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 80.3d | 8d 49.3d | 6.5d 1.5d | 5.3d 2026-11-03 20:25:04 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 68.8 Mbit/s (M) | 816.0 Kbit/s 68.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 106.4d | 8d 106.3d | 10.8d 1.5d | 5.3d 2026-11-03 20:25:04 68.8 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Running, Valid, Fast, Stable, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 167.3d | 8d 167.3d | 10.9d 1.5d | 5.3d 2026-11-03 20:25:04 80.0 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, Fast, Stable, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 48.3d | 8d 8.4d | 2.4d 1.5d | 5.3d 2026-11-03 20:25:04 80.0 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 80.0 Mbit/s (M) | 8.4 Mbit/s 80.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 9.8d | 8d 347.3d | 7607.5d 1.5d | 5.3d 2026-11-03 20:25:04 80.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 53.6 Mbit/s (M) | 816.0 Kbit/s 53.6 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 347.0d | 8d 347.0d | 10.6d 1.5d | 5.3d 2026-11-03 20:25:04 53.6 Mbit/s (M)

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.