View Relay "Unnamed"
Fingerprint: 38CAB05C61912D343A5CE4CA8D90FB2691852D6D |
Family: 1 relay
|
AS3816
|
Colombia
|
Linux
- Consensus
- In Consensus (7/7 Directory Auths)
- BW Verified
- 5/6 BW Auths Measured 6400 bit/s Median
- Stability
- Overloaded | UP 2d 1h 42m ago | UP 99% (1M)
- Reachability
- IPv4: 7/7 (Directory Auths)
- BW Weight
- 0.00% of Network | 16 Mbit/s Observed By Relay
- Version
- 0.4.8.22 Not Recommended
-
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: Time Known below threshold
: Time Known 7.4 days is below 8 days requirement (0.6 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. -
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. -
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. -
Tor version not recommended
: Running Tor version 0.4.8.22 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases. -
General Overload Active
: Relay reported general overload at 2026-07-12 11: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.
Addresses
- OR Address
- 179.33.21.132:34684
Reachability (Directory Authorities)
- IPv4
- 7/7
Location
- Country
-
Colombia
- Interactive Map
- View in RouteFluxMap
Autonomous System
- AS Number
- AS3816
- AS Name
- Unknown
- AS Rarity
- Legendary (score: 5/5, <0.05% consensus weight, 1 operator)
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (7/7 DA) | 7/7 authorities reached relay | ≥4/7 DA ORPort reachable |
| Valid | Descriptor | Meets (7/7 DA) | 7/7 authorities assigned Valid | Not blacklisted + valid descriptor (≥4/7 DA) |
| V2Dir | DirPort Available | Meets (7/7 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥4/7 DA) |
| Fast | Speed | Meets (7/7 DA) | 16.5 Mbit/s (R) | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (1/7 DA) | Median: 4.1d (1/7 DA above threshold) Min/Max: 4.0d / 9268.9d (7/7 DA, Voting / Total Eligible) |
≥9.3d - 19.8d (varies) (≥4/7 DA) [Stricter] moria1: ≥7800.1d |
| Uptime | Below (0/7 DA) | 2.1d (R) | ≥4.1d - 4.1d (varies) (≥4/7 DA) | |
| HSDir | Prereq: Fast | Meets (6/7 DA) | 6/7 DA assigned Fast | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/7 DA) | 1/7 DA assigned Stable | ≥9.3d - 19.8d (varies) (≥4/7 DA) [Stricter] moria1: ≥7800.1d |
|
| Prereq: V2Dir | Meets (7/7 DA) | 7/7 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥4/7 DA) | |
| WFU | Meets (7/7 DA) | Median: 99.0% (7/7 DA above threshold) Min/Max: 98.7% / 99.2% (7/7 DA, Voting / Total Eligible) |
≥98.0% (≥4/7 DA) | |
| Time Known | Meets (6/7 DA) | Median: 7.4d (0/7 DA above threshold) Min/Max: 5.8d / 7.7d (7/7 DA, Voting / Total Eligible) |
≥1.0d (most) (≥4/7 DA) [Stricter] moria1: ≥9.9d |
|
| Guard | Prereq: Fast | Meets (6/7 DA) | 6/7 DA assigned Fast | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/7 DA) | 1/7 DA assigned Stable | ≥9.3d - 19.8d (varies) (≥4/7 DA) [Stricter] moria1: ≥7800.1d |
|
| Prereq: V2Dir | Meets (7/7 DA) | 7/7 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥4/7 DA) | |
| WFU | Meets (7/7 DA) | Median: 99.0% (7/7 DA above threshold) Min/Max: 98.7% / 99.2% (7/7 DA, Voting / Total Eligible) |
≥98% (≥4/7 DA) | |
| Time Known | Below (0/7 DA) (need 0.6 more days) | Median: 7.4d (0/7 DA above threshold) Min/Max: 5.8d / 7.7d (7/7 DA, Voting / Total Eligible) |
≥8 days (≥4/7 DA) | |
| Bandwidth | Meets (7/7 DA) | 16.5 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.0 Mbit/s (≥4/7 DA) | |
| Exit | Exit Policy | Below (0/7 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-14 08:45:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 16.52 Mbit/s
- Advertised Bandwidth
- 16.52 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- 92 GB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-07-14 08:45:05
- Measured By
-
5/6
Bandwidth Authorities
Not measured by: bastet - Median Measurement
- 6400 bit/s
- Min / Max
- 320 bit/s / 16.5 Kbit/s
- Deviation
- 16.2 Kbit/s [Warning] High variation
Uptime Metrics
- Current Status
- UP 2d 1h 42m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.0%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- 98.8%/—/—/—
- Hibernating
- No
Timestamps
- First Seen
- 1w 1d 17h ago (2026-07-05 16:00:00)
- Last Seen
- 1h 45m 44s ago (2026-07-14 08:00:00)
- Last Restarted
- 2d 1h 42m ago (2026-07-12 08:03:41)
- Last Changed Address
- 2026-07-05 16:00:00
General Overload (from /details)
- Status
- Reported
- When
- 2026-07-12 11: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)
No rate limit data from /bandwidth endpoint.
Recommendations
- Check CPU/memory:
htop - Review
MaxMemInQueuesin torrc
Operator Identity
Source: AROI Validation API — 2026-07-14 01:00 UTC
Family Configuration
- Family Support
- None — No family membership configured
- Effective Members: 0
- none
- Effective Member: 1
38CAB05C61912D343A5CE4CA8D90FB2691852D6D (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.8.22 on Linux
- Version
- 0.4.8.22 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Tue, 14 Jul 2026 09:45:41 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-07-14 08:45:05).
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 | No | — | Y | Yes | Running, Valid, V2Dir, Fast | 16.5 Mbit/s | 816.0 Kbit/s | 16.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 99.0% | 98% | 7.4d | 8d | 4.1d | 29.3d | 2.1d | 4.2d | 99.0% | 98.0% | 7.4d | 1.0d | 2026-07-13 23:04:20 | 16.5 Kbit/s |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir | 16.5 Mbit/s | 816.0 Kbit/s | 16.5 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s | 99.2% | 98% | 7.4d | 8d | 4.1d | 9.3d | 2.1d | 4.1d | 99.2% | 98.0% | 7.4d | 1.0d | 2026-07-13 23:04:20 | 320 bit/s |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir, Fast | 16.5 Mbit/s | 816.0 Kbit/s | 16.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 99.0% | 98% | 7.4d | 8d | 4.1d | 18.2d | 2.1d | 4.1d | 99.0% | 98.0% | 7.4d | 1.0d | 2026-07-13 23:04:20 | 16.5 Kbit/s |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast | 16.5 Mbit/s | 816.0 Kbit/s | 16.5 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s | 99.2% | 98% | 7.4d | 8d | 4.1d | 16.0d | 2.1d | 4.1d | 99.2% | 98.0% | 7.4d | 1.0d | 2026-07-13 23:04:20 | 6400 bit/s |
| maatuska (SE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast | 16.5 Mbit/s | 816.0 Kbit/s | 16.5 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s | 99.2% | 98% | 7.7d | 8d | 4.1d | 19.8d | 2.1d | 4.1d | 99.2% | 98.0% | 7.7d | 1.0d | 2026-07-13 23:04:20 | 4560 bit/s |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable | 16.5 Mbit/s | 8.4 Mbit/s | 16.5 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s | 98.7% | 98% | 5.8d | 8d | 9268.9d | 7800.1d | 2.1d | 4.1d | 98.7% | 98.0% | 5.8d | 9.9d | 2026-07-13 23:04:20 | 8.8 Kbit/s |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast | 16.5 Mbit/s | 816.0 Kbit/s | 16.5 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s | 99.0% | 98% | 7.4d | 8d | 4.0d | 28.6d | 2.1d | 4.1d | 99.0% | 98.0% | 7.4d | 1.0d | 2026-07-13 23:04:20 | 3680 bit/s |
— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known
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.
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.