View Relay "Unnamed"
Fingerprint: 5409230F6864E81725E54A54A7FC1B8CD771376E |
Family: 1 relay
|
abhorrent759@hotmail.com |
AS211720
|
Seychelles
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Not Tested (via exitdnshealth.1aeo.com)
- BW Verified
- 4/7 BW Auths Measured 8 Kbit/s Median
- Stability
- Not Overloaded | UP 1d 1h 21m ago
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.00% of Network | 0 Kbit/s Observed By Relay
- Version
- 0.4.9.14 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 0/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo and tor26 measured this relay at 8.0 Kbit/s, below the Fast threshold (816.0 Kbit/s). dizum, faravahar, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored). Its consensus weight, the median of the 4 bandwidth-scanner measurements, is 8.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: 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
: 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 and tor26 measured this relay at 8.0 Kbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported unknown. moria1 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
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: Time Known below threshold
: 0/9 authorities meet guard-tk (≥8 days; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have known this relay for 5.4 hours–1.0 days.
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
: 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 do not.
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 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 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.
Addresses
- OR Address
-
185.231.32.32:9001
[2a0c:4d00:1:15::1]:9001 - Exit Address
- 185.231.32.32
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Seychelles
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/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 |
| IPv6 Reachability | Meets (8/8 DA) | 8/8 tested authorities reached relay | ≥5/8 tested (majority) (≥5/8 DA) | |
| 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 | Below (0/9 DA) | 8.0 Kbit/s (4 DA measured) 0 bit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥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 (0/9 DA) | Median: 1.0d (0/9 DA above threshold) Min/Max: 0.2d / 1.0d (9/9 DA, Voting / Total Eligible) |
≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
| Uptime | Below (0/9 DA) | 1.1d (R) | ≥3.2d - 4.0d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 8.0 Kbit/s (4 DA measured) 0 bit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (0/9 DA) | 0/9 DA assigned Stable | ≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 1.1d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known |
|
| Guard | Prereq: Fast | Below (0/9 DA) | 0/9 DA assigned Fast 8.0 Kbit/s (4 DA measured) 0 bit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (0/9 DA) | 0/9 DA assigned Stable | ≥2.5d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥8467.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (9/9 DA) | Majority: 100.0% (9/9 DA above threshold) | ≥98%; dizum: ≥97.264% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) | Median: 1.0d (0/9 DA above threshold) Min/Max: 0.2d / 1.0d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 8.0 Kbit/s (4 DA measured) 0 bit/s (4 DA relay-reported) 0 bit/s (1 DA unmeasured, counted as 0) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-288.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-11-02 07:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-02 07:45:06
- Measured By
-
4/7
Bandwidth Authorities
Not measured by: faravahar, longclaw, moria1 - Consensus Weight
- 8.0 Kbit/s (median of 4 measurements)
- Measured Min / Max
- 8.0 Kbit/s / 8.0 Kbit/s
Network Participation:
Consensus Weight:
0.0000% of network
(0th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0000% (0th pctl)
Uptime Metrics
- Current Status
- UP 1d 1h 21m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 0.0%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 1d 45m 28s ago (2026-11-01 07:00:00)
- Last Seen
- 1h 45m 28s ago (2026-11-02 06:00:00)
- Last Restarted
- 1d 1h 21m ago (2026-11-01 06:24:00)
- Last Changed Address
- 2026-11-01 07:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-02 07:45 UTC. /details snapshot 2026-11-02 06:00:00 UTC (cached 24s ago). /bandwidth snapshot 2026-11-02 05:00:00 UTC (cached 1h 30m ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- Rate Limit
- —
- Burst Limit
- —
- Write counter
- —
- Read counter
- —
About these reports and MetricsPort
Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.
MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.
The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.
curl http://127.0.0.1:9035/metrics
History
Operator Identity
Source: AROI Validation API — 2026-11-01 22:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- abhorrent759@hotmail.com
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
5409230F6864E81725E54A54A7FC1B8CD771376E (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
IPv4 Exit Policy Summary
reject: 22-23 25 110 143 445 465 587 631 993 995 2525 3389 5900 5998-6063 6667 6697 11211
IPv6 Exit Policy Summary
NoneFull 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 185.231.32.32:* reject *:6697 reject *:6029-6031 reject *:6054-6056 reject *:6039-6042 reject *:6012-6015 reject *:11211 reject *:6057-6060 reject *:6020-6023 reject *:5900 reject *:6061-6063 reject *:5998-5999 reject *:6005-6007 reject *:6051-6053 reject *:465 reject *:110 reject *:445 reject *:6024-6026 reject *:993 reject *:6045-6048 reject *:6036-6038 reject *:587 reject *:3389 reject *:6667 reject *:143 reject *:2525 reject *:6003-6004 reject *:6000-6002 reject *:6008-6011 reject *:6027-6028 reject *:6016-6019 reject *:995 reject *:22-23 reject *:6049-6050 reject *:25 reject *:631 reject *:6032-6035 reject *:6043-6044 accept *:*
Last fetch was at Mon, 02 Nov 2026 07:45:27 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-02 07:45:06).
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 | v6 | Flags | Fast (BW|T) | Guard BW (BW|Threshold) | Guard WFU (M|T) | Guard TK (M|T) | Stable MTBF (M|T) | Stable Uptime (Relay|T) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.4d | 8d | 0.4d | 7.1d | 1.1d | 3.4d | 2026-11-01 06:24:09 | 8.0 Kbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 288.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.0d | 8d | 1.0d | 8.5d | 1.1d | 4.0d | 2026-11-02 01:30:13 | 8.0 Kbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 97% | 1.0d | 8d | 1.0d | 5.9d | 1.1d | 4.0d | 2026-11-02 01:30:13 | — |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.0d | 8d | 1.0d | 5.9d | 1.1d | 4.0d | 2026-11-02 01:30:13 | — |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.0d | 8d | 1.0d | 9.8d | 1.1d | 4.0d | 2026-11-02 01:30:13 | 8.0 Kbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.0d | 8d | 1.0d | 9.9d | 1.1d | 4.0d | 2026-11-02 01:30:13 | — |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (R) | 816.0 Kbit/s | 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.2d | 8d | 0.2d | 2.5d | 1.1d | 3.2d | 2026-11-01 06:24:09 | — |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 0 bit/s (U) | 8.4 Mbit/s | 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.9d | 8d | 1.0d | 8467.5d | 1.1d | 4.0d | 2026-11-02 01:30:13 | — |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 8.0 Kbit/s (M) | 816.0 Kbit/s | 8.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.0d | 8d | 1.0d | 9.8d | 1.1d | 4.0d | 2026-11-02 01:30:13 | 8.0 Kbit/s (M) |
N/T = this authority does not test IPv6 • — = not in this vote • 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.