View Relay "ahgos"
Fingerprint: 483B5863C7C11296D3857910FD2C224771813BAC |
Family: 1 relay
|
archgreybeardshall@gmail.com |
AS29553
|
Poland
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 264 Kbit/s Median
- Stability
- Overloaded | UP 1d 2h 20m ago | UP 100% (1M)
- Reachability
- IPv4: 9/9 (Directory Auths)
- BW Weight
- 0.00% of Network | 2 Mbit/s Observed By Relay
- Version
- 0.4.9.14 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 3/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/s – 720.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). faravahar judged it by bandwidth not shown in the votes. Its consensus weight, the median of the 5 bandwidth-scanner measurements, is 264.0 Kbit/s.
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next. -
Guard: requires Fast flag
: Guard flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. -
Guard: bandwidth below threshold
: 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 288.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/s – 720.0 Kbit/s. dizum, longclaw and maatuska used the relay-reported 2.1 Mbit/s.
Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx. -
Guard: WFU below threshold
: Weighted Fractional Uptime 66.7% 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. -
HSDir: requires Fast flag
: HSDir flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. -
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 becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-dir-server. You can check with:grep tunnelled-dir-server /var/lib/tor/cached-descriptors -
HSDir: WFU below threshold
: WFU 66.7% 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. -
Write Bandwidth Limit Hit
: Write rate limit (2 Mbit/s) was hit 1 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 (2 Mbit/s) was hit 12 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=2 Mbit/s, Burst=307 KB. Limits hit: Write=1, Read=12.
Addresses
- OR Address
-
114.169.rev.vline.pl
217.76.114.169:9001
Reachability (Directory Authorities)
- IPv4
- 9/9
Location
- Country
-
Poland
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 9/9 | HSDir: 0/9 | Guard: 0/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 | Below (0/9 DA) | No DirPort, no tunnelled-dir-server (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (3/9 DA) | 8.0 Kbit/s – 720.0 Kbit/s (5 DA measured) 2.1 Mbit/s (3 DA relay-reported) 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 | Partial (8/9 DA) | Median: 12.7d (9/9 DA above threshold) Min/Max: 12.3d / 759.7d (9/9 DA, Voting / Total Eligible) |
≥5.4d - 10.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥9590.6d |
| Uptime | Below (0/9 DA) | 1.1d (R) | ≥3.9d - 4.0d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (3/9 DA) | 3/9 DA assigned Fast 8.0 Kbit/s – 720.0 Kbit/s (5 DA measured) 2.1 Mbit/s (3 DA relay-reported) 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 (9/9 DA) | 9/9 DA assigned Stable | ≥5.4d - 10.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥9590.6d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 67.1% (0/9 DA above threshold) Min/Max: 65.5% / 74.3% (9/9 DA, Voting / Total Eligible) |
≥98.0% (≥5/9 DA) | |
| Time Known | Meets (8/9 DA) | Median: 19.6d (9/9 DA above threshold) Min/Max: 9.9d / 20.0d (9/9 DA, Voting / Total Eligible) |
≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥10.0d |
|
| Guard | Prereq: Fast | Below (3/9 DA) | 3/9 DA assigned Fast 8.0 Kbit/s – 720.0 Kbit/s (5 DA measured) 2.1 Mbit/s (3 DA relay-reported) 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 (9/9 DA) | 9/9 DA assigned Stable | ≥5.4d - 10.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥9590.6d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 67.1% (0/9 DA above threshold) Min/Max: 65.5% / 74.3% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 19.6d (9/9 DA above threshold) Min/Max: 9.9d / 20.0d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 8.0 Kbit/s – 720.0 Kbit/s (5 DA measured) 2.1 Mbit/s (3 DA relay-reported) faravahar: not published |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-288.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-13 08:45:07).
Capacity (Relay Reported)
- Observed Bandwidth
- 2.38 Mbit/s
- Advertised Bandwidth
- 2.10 Mbit/s
- Rate Limit
- 2.10 Mbit/s
- Burst Limit
- 2.46 Mbit/s
- Total Data
- 1.0 GB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-10-13 08:45:07
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 264.0 Kbit/s (median of 5 measurements)
- Measured Min / Max
- 8.0 Kbit/s / 720.0 Kbit/s
- Deviation
- 712.0 Kbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0000% of network
(4th pctl)
|
Guard:
N/A |
Middle:
0.0000% (4th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 1d 2h 20m 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 5d 10h ago (2026-09-30 23:00:00)
- Last Seen
- 1h 15m 39s ago (2026-10-13 08:00:00)
- Last Restarted
- 1d 2h 20m ago (2026-10-12 06:55:16)
- Last Changed Address
- 2026-09-30 23:00:00
[Warning] OVERLOADED
— Rate limits hit W:1 R:12 (limit: 2 Mbit/s)
General Overload (from /details)
- Status
- Not Reported
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
- 2.46 Mbit/s
- Burst Limit
- 307 KB
- Write Limit Hit
- 1 times
- Read Limit Hit
- 12 times
- Last Reported
- 9 hours ago
Recommendations
- Consider increasing
RelayBandwidthRate - Check if ISP is throttling traffic
History
Operator Identity
Source: AROI Validation API — 2026-10-13 00:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- archgreybeardshall@gmail.com
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
483B5863C7C11296D3857910FD2C224771813BAC (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Tue, 13 Oct 2026 09:15:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-10-13 08: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 | Running, Valid, Stable | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 66.7% | 98% | 19.3d | 8d | 12.4d | 10.4d | 1.1d | 4.1d | 66.7% | 98.0% | 19.3d | 1.0d | 2026-10-13 00:55:21 | 8.0 Kbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, Stable | 296.0 Kbit/s (M) | 816.0 Kbit/s | 296.0 Kbit/s (M) | 288.0 Mbit/s OR 16.8 Mbit/s | 67.5% | 98% | 19.6d | 8d | 12.8d | 5.4d | 1.1d | 4.0d | 67.5% | 98.0% | 19.6d | 1.0d | 2026-10-13 00:55:21 | 296.0 Kbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, Fast, Stable | 2.1 Mbit/s (R) | 816.0 Kbit/s | 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 66.3% | 98% | 20.0d | 8d | 12.8d | 10.6d | 1.1d | 4.0d | 66.3% | 98.0% | 20.0d | 1.0d | 2026-10-13 00:55:21 | 2.1 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Stable | not published | 816.0 Kbit/s | not published | 280.0 Mbit/s OR 16.8 Mbit/s | 67.2% | 98% | 19.6d | 8d | 12.6d | 11.4d | 1.1d | 4.0d | 67.2% | 98.0% | 19.6d | 1.0d | 2026-10-13 00:55:21 | 2.1 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, Stable | 256.0 Kbit/s (M) | 816.0 Kbit/s | 256.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s | 65.7% | 98% | 19.7d | 8d | 12.5d | 10.4d | 1.1d | 4.0d | 65.7% | 98.0% | 19.7d | 1.0d | 2026-10-13 00:55:21 | 256.0 Kbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast, Stable | 2.1 Mbit/s (R) | 816.0 Kbit/s | 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 67.1% | 98% | 19.6d | 8d | 12.7d | 10.9d | 1.1d | 4.0d | 67.1% | 98.0% | 19.6d | 1.0d | 2026-10-13 00:55:21 | 2.1 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Running, Valid, Fast, Stable | 2.1 Mbit/s (R) | 816.0 Kbit/s | 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 65.5% | 98% | 19.6d | 8d | 12.3d | 10.3d | 1.1d | 4.0d | 65.5% | 98.0% | 19.6d | 1.0d | 2026-10-13 00:55:21 | 2.1 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Stable | 720.0 Kbit/s (M) | 8.4 Mbit/s | 720.0 Kbit/s (M) | 208.0 Mbit/s OR 16.8 Mbit/s | 74.3% | 98% | 9.9d | 8d | 759.7d | 9590.6d | 1.1d | 3.9d | 74.3% | 98.0% | 9.9d | 10.0d | 2026-10-13 00:55:21 | 720.0 Kbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, Stable | 264.0 Kbit/s (M) | 816.0 Kbit/s | 264.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 67.3% | 98% | 19.7d | 8d | 12.8d | 10.6d | 1.1d | 4.0d | 67.3% | 98.0% | 19.7d | 1.0d | 2026-10-13 00:55:21 | 264.0 Kbit/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 (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.