View Relay "DS19TorRelay"

Fingerprint: E2117FFA2CB2FB29B6521E6C03824E37DB03C92D | Family: 1 relay | AS9198 | Kazakhstan | Linux

Health Status

Consensus
In Consensus (has Running flag)
Flags
Fast, HSDir, Running, Stable, V2Dir, Valid (6)
BW Verified
Measured
Stability
Overloaded | DOWN 1d 21h 6m ago | UP 100% (1M)
Reachability
N/A
First Seen
1w 16h 6m ago
BW Weight
0.00% of Network | 17 Mbit/s Observed By Relay
Version
0.4.9.13 Recommended
Issues Detected:
  • General Overload Active : Relay reported general overload at 2026-10-15 18: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.
  • Read Bandwidth Limit Hit : Read rate limit (20 Mbit/s) was hit 1 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=20 Mbit/s, Burst=2.5 MB. Limits hit: Write=0, Read=1.

Connectivity and Location

Addresses
OR Address
2.133.97.194.dynamic.telecom.kz
2.133.97.194:9001
Reachability (Directory Authorities)
Status
Reachability data unavailable
Location
Country
Kazakhstan Kazakhstan
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS9198
AS Name
JSC Kazakhtelecom (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
17.48 Mbit/s
Advertised Bandwidth
17.48 Mbit/s
Rate Limit
20.00 Mbit/s
Burst Limit
20.00 Mbit/s
Total Data
65 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-17 23:00:36

Measured By
Yes (≥3 authorities)
Network Participation: Consensus Weight: 0.0006% of network (13th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 1d 21h 6m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1w 16h 6m ago (2026-10-10 08:00:00)
Last Seen
1d 21h 6m ago (2026-10-16 03:00:00)
Last Restarted
1w 16h 44m ago (2026-10-10 07:21:39)
Last Changed Address
2026-10-10 08:00:00
[Warning] OVERLOADED — General overload at 2026-10-15 18:00 UTC; Rate limits hit W:0 R:1 (limit: 20 Mbit/s)
General Overload (from /details)
Status
Reported
When
2026-10-15 18:00 UTC (2 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
20.00 Mbit/s
Burst Limit
2.5 MB
Write Limit Hit
0 times
Read Limit Hit
1 times
Last Reported
3 days ago
Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-17 16:00 UTC

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

Software and Version

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

Exit Health & Policy

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 Sun, 18 Oct 2026 00:06:03 GMT.