View Relay "TRRelay1"

Fingerprint: F16FA573E1A9B5B545920972618698235DD78E05 | Family: 2 relays | umutcankurhan8@gmail.com | AS207459 | Turkey | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
4/7 BW Auths Measured 36 Mbit/s Median
Stability
Overloaded | UP 3w 6d 12m ago | UP 99% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 47 Mbit/s Observed By Relay
Version
0.4.9.12 Recommended
Issues Detected:
  • HSDir: WFU below threshold : WFU 0.0% 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.
  • HSDir: Time Known below threshold : Time Known 0.0 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • General Overload Active : Relay reported general overload at 2026-10-11 13: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.
  • Write Bandwidth Limit Hit : Write rate limit (67 Mbit/s) was hit 163 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 (67 Mbit/s) was hit 10 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:

Addresses
OR Address
193.31.117.236:443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Turkey Turkey
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS207459
AS Name
TEKNOSOS BILISIM HIZMETLERI VE TIC. LTD. STI. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, Guard
Eligible Flags (6): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 7/9 | HSDir: 4/9 | Guard: 7/9 | Exit: 0/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 Partial (8/9 DA) 30.4 Mbit/s – 44.0 Mbit/s (4 DA measured)
47.8 Mbit/s (3 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (4/9 DA) Median: 10.6d (2/9 DA above threshold)
Min/Max: 0.0d / 11193.8d (9/9 DA, Voting / Total Eligible)
≥5.2d - 10.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8884.5d
Uptime Meets (9/9 DA) 27.0d (R) ≥3.4d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
30.4 Mbit/s – 44.0 Mbit/s (4 DA measured)
47.8 Mbit/s (3 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
faravahar: not published
≥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 (7/9 DA) 7/9 DA assigned Stable ≥5.2d - 10.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8884.5d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (7/9 DA) Median: 99.7% (7/9 DA above threshold)
Min/Max: 0.0% / 99.7% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 22.6d (7/9 DA above threshold)
Min/Max: 0.0d / 25.7d (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
30.4 Mbit/s – 44.0 Mbit/s (4 DA measured)
47.8 Mbit/s (3 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
faravahar: not published
≥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 (7/9 DA) 7/9 DA assigned Stable ≥5.2d - 10.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8884.5d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (7/9 DA) Median: 99.7% (7/9 DA above threshold)
Min/Max: 0.0% / 99.7% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 22.6d (7/9 DA above threshold)
Min/Max: 0.0d / 25.7d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Partial (8/9 DA) 30.4 Mbit/s – 44.0 Mbit/s (4 DA measured)
47.8 Mbit/s (3 DA relay-reported)
0 bit/s (1 DA unmeasured, counted as 0)
faravahar: not published
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.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-10-12 15:45:07).

Capacity (Relay Reported)
Observed Bandwidth
47.79 Mbit/s
Advertised Bandwidth
47.79 Mbit/s
Rate Limit
67.11 Mbit/s
Burst Limit
67.11 Mbit/s
Total Data
98 TB (1 year)
1mo: 21 TB | 6mo: 93 TB | 1y: 98 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-12 15:45:07

Measured By
4/7 Bandwidth Authorities
Not measured by: faravahar, gabelmoo, longclaw
Consensus Weight
36.0 Mbit/s (median of 4 measurements)
Measured Min / Max
30.4 Mbit/s / 44.0 Mbit/s
Network Participation: Consensus Weight: 0.0022% of network (27th pctl) | Guard: 0.0052% (13th pctl) | Middle: 0.0014% (21th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 30 days
1M 6M 1Y

Uptime Metrics
Current Status
UP 3w 6d 12m ago
Overall Uptime (1M/6M/1Y/5Y)
99.6%/99.7%/99.7%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/99.2%/94.9%/—
Hibernating
No
Timestamps
First Seen
6mo 3w 2d ago (2026-03-23 00:00:00)
Last Seen
1h 15m 40s ago (2026-10-12 15:00:00)
Last Restarted
3w 6d 12m ago (2026-09-15 16:02:59)
Last Changed Address
2026-04-06 23:00:00
[Warning] OVERLOADED — General overload at 2026-10-11 13:00 UTC; Rate limits hit W:163 R:10 (limit: 67 Mbit/s)
General Overload (from /details)
Status
Reported
When
2026-10-11 13:00 UTC (1 days 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)
Rate Limit
67.11 Mbit/s
Burst Limit
8.4 MB
Write Limit Hit
163 times
Read Limit Hit
10 times
Last Reported
1 days ago
Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic
History
Uptime, last 6 months Uptime, last year Uptime, last 30 days
1M 6M 1Y

Operator Identity

Source: AROI Validation API — 2026-10-12 08:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
umutcankurhan8@gmail.com
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2
02A47EF19F91E6181DBC4D24EA4F55AAC387E54D
F16FA573E1A9B5B545920972618698235DD78E05 (this relay)
Alleged Member: 1
(they don't list you back)
05AFCA2DF997D4538666D04B27DB36AB33E6E6C8 (not in the network)
Indirect Members: 0
none

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

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Mon, 12 Oct 2026 16:15:39 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-12 15:45:07).

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 (BW|T) Guard BW (BW|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 Valid, V2Dir, Fast 36.0 Mbit/s (M) | 816.0 Kbit/s 36.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 10.7d 27.0d | 3.4d 0.0% | 98.0% 0.0d | 1.0d 2026-10-12 06:38:35 36.0 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, Guard 44.0 Mbit/s (M) | 816.0 Kbit/s 44.0 Mbit/s (M) | 280.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 22.6d | 8d 10.6d | 5.2d 27.0d | 3.4d 99.7% | 98.0% 22.6d | 1.0d 2026-10-12 06:38:35 44.0 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 47.8 Mbit/s (R) | 816.0 Kbit/s 47.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 23.1d | 8d 10.6d | 10.9d 27.0d | 3.4d 99.7% | 98.0% 23.1d | 1.0d 2026-10-12 06:38:35 47.8 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, Guard not published | 816.0 Kbit/s not published | 280.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 22.6d | 8d 10.6d | 11.7d 27.0d | 3.4d 99.7% | 98.0% 22.6d | 1.0d 2026-10-12 06:38:35 47.8 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 264.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 10.8d 27.0d | 3.4d 0.0% | 98.0% 0.0d | 1.0d 2026-10-12 06:38:35 47.8 Mbit/s (R)
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, Guard 47.8 Mbit/s (R) | 816.0 Kbit/s 47.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 23.8d | 8d 10.8d | 11.2d 27.0d | 3.4d 99.7% | 98.0% 23.8d | 1.0d 2026-10-12 06:38:35 47.8 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 47.8 Mbit/s (R) | 816.0 Kbit/s 47.8 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 23.1d | 8d 10.6d | 10.5d 27.0d | 3.4d 99.7% | 98.0% 23.1d | 1.0d 2026-10-12 06:38:35 47.8 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 39.2 Mbit/s (M) | 8.4 Mbit/s 39.2 Mbit/s (M) | 200.0 Mbit/s OR 16.8 Mbit/s 99.2% | 98% 9.9d | 8d 11193.8d | 8884.5d 27.0d | 3.4d 99.2% | 98.0% 9.9d | 9.8d 2026-10-12 06:38:35 39.2 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 30.4 Mbit/s (M) | 816.0 Kbit/s 30.4 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 25.7d | 8d 11.7d | 11.2d 27.0d | 3.4d 99.7% | 98.0% 25.7d | 1.0d 2026-10-12 06:38:35 30.4 Mbit/s (M)

— = not tested/available • 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.