View Relay "TRONTO346"

Fingerprint: 93FC232E585D064A063140180FB3BB061D239529 | Family: 1 relay | noc@example.com | AS210083 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (16.0s, 25th percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 6320 bit/s Median
Stability
Overloaded | UP 3w 15h 56m ago | UP 82% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3w 4d 20h ago
BW Weight
0.00% of Network | 11 Mbit/s Observed By Relay
Version
0.4.9.6 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 1.4 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 90.3% 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 90.3% 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.
  • General Overload Active : Relay reported general overload at 2026-05-26 14:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses
OR Address
203.12.31.99:9001
Exit Address
203.12.31.99
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS210083
AS Name
Privex Inc. (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.07% consensus weight, 4 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 1/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
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.2 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 (1/9 DA) Median: 1.1d (1/9 DA above threshold)
Min/Max: 0.9d / 18831.5d (9/9 DA, Voting / Total Eligible)		 ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.6d
Uptime Meets (9/9 DA) 21.7d (R) ≥13.3d - 13.7d (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 (1/9 DA) 1/9 DA assigned Stable ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.6d
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: 92.3% (0/9 DA above threshold)
Min/Max: 90.3% / 93.9% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 12.0d (9/9 DA above threshold)
Min/Max: 9.3d / 13.9d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
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 (1/9 DA) 1/9 DA assigned Stable ≥21.2d - 52.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥338.6d
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: 92.3% (0/9 DA above threshold)
Min/Max: 90.3% / 93.9% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.0d (9/9 DA above threshold)
Min/Max: 9.3d / 13.9d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 11.2 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 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-05-27 08:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
11.18 Mbit/s
Advertised Bandwidth
8.39 Mbit/s
Rate Limit
8.39 Mbit/s
Burst Limit
16.78 Mbit/s
Total Data
324 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-27 08:45:07

Measured By
6/7 Bandwidth Authorities
Not measured by: dannenberg
Median Measurement
6320 bit/s
Min / Max
2480 bit/s / 9.6 Kbit/s
Deviation
7120 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0003% of network (14th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0010% (3th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 3w 15h 56m ago
Overall Uptime (1M/6M/1Y/5Y)
82.6%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (82.6%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3w 4d 20h ago (2026-05-01 12:00:00)
Last Seen
1h 45m 44s ago (2026-05-27 07:00:00)
Last Restarted
3w 15h 56m ago (2026-05-05 16:48:56)
Last Changed Address
2026-05-01 12:00:00
[Warning] OVERLOADED — General overload at 2026-05-26 14:00 UTC
General Overload (from /details)
Status
Reported
When
2026-05-26 14:00 UTC (18 hours ago)

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)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-27 01:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
noc@example.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
93FC232E585D064A063140180FB3BB061D239529 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 16.0s, 25th percentile)
Query Domain
ae7615248467478b8c176ffb46b93c17.93fc232e.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
pinselohrkatze00 (DE) 76D2EBA82BBCCA3DF9F254A9A8372A10A26F3D14
Exit Address Used
203.12.31.99
Per-Instance Results
Cross Validation Attempt 1: Success, 19.1s (cv1_w2)
Cross Validation Attempt 2: Success, 16.3s (cv2_w2)
Cross Validation Attempt 3: Success, 12.1s (cv3_w2)
Cross Validation Attempt 4: Success, 16.4s (cv4_w2)
Tested: 2026-05-26 19:10:49 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  22
  80
  443
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 203.12.31.99:*
accept *:80
accept *:443
accept *:22
reject *:*

Last fetch was at Wed, 27 May 2026 08:45:43 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-27 08:45:07).

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 Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 11.2 Mbit/s | 816.0 Kbit/s 11.2 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 90.3% | 98% 11.9d | 8d 1.0d | 50.7d 21.7d | 13.3d 90.3% | 98.0% 11.9d | 1.0d 2026-05-26 14:16:44 6320 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 11.2 Mbit/s | 816.0 Kbit/s 11.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.7% | 98% 13.1d | 8d 1.1d | 46.5d 21.7d | 13.6d 92.7% | 98.0% 13.1d | 1.0d 2026-05-26 14:16:44 8.4 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 11.2 Mbit/s | 816.0 Kbit/s 11.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.9% | 98% 13.1d | 8d 1.2d | 21.2d 21.7d | 13.6d 93.9% | 98.0% 13.1d | 1.0d 2026-05-26 14:16:44 8.4 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 11.2 Mbit/s | 816.0 Kbit/s 11.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 91.0% | 98% 12.1d | 8d 0.9d | 52.1d 21.7d | 13.7d 91.0% | 98.0% 12.1d | 1.0d 2026-05-26 14:16:44 8.4 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 11.2 Mbit/s | 816.0 Kbit/s 11.2 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 93.6% | 98% 13.9d | 8d 1.3d | 53.0d 21.7d | 13.8d 93.6% | 98.0% 13.9d | 1.0d 2026-05-26 14:16:44 2640 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 11.2 Mbit/s | 816.0 Kbit/s 11.2 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 93.2% | 98% 12.0d | 8d 1.1d | 57.8d 21.7d | 13.7d 93.2% | 98.0% 12.0d | 1.0d 2026-05-26 14:16:44 6320 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 11.2 Mbit/s | 816.0 Kbit/s 11.2 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 92.0% | 98% 11.9d | 8d 1.1d | 24.6d 21.7d | 13.5d 92.0% | 98.0% 11.9d | 1.0d 2026-05-26 14:16:44 9.6 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 11.2 Mbit/s | 8.4 Mbit/s 11.2 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 91.1% | 98% 9.3d | 8d 18831.5d | 338.6d 21.7d | 14.1d 91.1% | 98.0% 9.3d | 9.9d 2026-05-26 14:16:44 5280 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 11.2 Mbit/s | 816.0 Kbit/s 11.2 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 11.4d | 8d 0.9d | 54.0d 21.7d | 13.7d 92.3% | 98.0% 11.4d | 1.0d 2026-05-26 14:16:44 2480 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.