View Relay "Unnamed"

Fingerprint: FCD51F02A7D19F212A4447722FF71A6190D16E88 | Family: 1 relay | AS35916 | United States of America | OpenBSD

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
4/6 BW Auths Measured 9 Kbit/s Median
Stability
Overloaded | UP 1w 5d 21h ago | UP 80% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 9 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • 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 : Observed bandwidth 1.2 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • Guard: WFU below threshold : Weighted Fractional Uptime 83.3% 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.
  • 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.
  • 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 because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • HSDir: WFU below threshold : WFU 83.3% 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.
  • File Descriptor Exhaustion : Relay ran out of file descriptors at 2026-03-15 05:00 UTC. This severely impacts connections and performance.
    Suggestion: Increase file descriptor limits: For systemd: add "LimitNOFILE=65535" to [Service] section. For shell: ulimit -n 65535. Persistent: edit /etc/security/limits.conf.

Addresses
OR Address
averymt.zip
142.171.124.60:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS35916
AS Name
MULTACOM CORPORATION (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 7 operators)

Current Flags (3): Running, Valid, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/9 | Stable: 1/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 Meets (9/9 DA) 9.9 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/9 DA) Median: 0.4d (1/9 DA above threshold)
Min/Max: 0.3d / 19641.0d (9/9 DA, Voting / Total Eligible)
≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Uptime Below (1/9 DA) 12.9d (R) ≥12.0d - 14.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (7/9 DA) 7/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.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: 85.4% (0/9 DA above threshold)
Min/Max: 69.3% / 86.9% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 10.8d (9/9 DA above threshold)
Min/Max: 9.7d / 11.2d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (7/9 DA) 7/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.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: 85.4% (0/9 DA above threshold)
Min/Max: 69.3% / 86.9% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.8d (9/9 DA above threshold)
Min/Max: 9.7d / 11.2d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 9.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-15 16:15:07).

Capacity (Relay Reported)
Observed Bandwidth
9.94 Mbit/s
Advertised Bandwidth
9.94 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
302 GB (1 year)
1mo: 25 GB | 6mo: 219 GB | 1y: 302 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 16:15:07

Measured By
4/6 Bandwidth Authorities
Not measured by: bastet, longclaw
Median Measurement
9.9 Kbit/s
Min / Max
2080 bit/s / 9.9 Kbit/s
Deviation
7856 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (10th pctl) | Guard: N/A | Middle: 0.0004% (10th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 1w 5d 21h ago
Overall Uptime (1M/6M/1Y/5Y)
80.5%/82.2%/84.2%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/82.0%/83.1%/—
Hibernating
No
Timestamps
First Seen
7mo 2w 1d ago (2025-08-02 07:00:00)
Last Seen
1h 45m 55s ago (2026-03-15 15:00:00)
Last Restarted
1w 5d 21h ago (2026-03-02 18:47:14)
Last Changed Address
2025-08-02 07:00:00
[Warning] OVERLOADED — FD exhaustion (last: 2026-03-15)
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
Reported — 2026-03-15 05:00 UTC (11 hours ago)
Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Increase FD limit: ulimit -n 65535
  • systemd: LimitNOFILE=65535 in [Service]

Operator Identity

Source: AROI Validation API — 2026-03-15 09: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
FCD51F02A7D19F212A4447722FF71A6190D16E88 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
OpenBSD — Tor 0.4.8.21 on OpenBSD
Version
0.4.8.21Recommended
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 Sun, 15 Mar 2026 16:45:53 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-15 16:15: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 (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 9.9 Mbit/s | 816.0 Kbit/s 9.9 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 83.3% | 98% 10.7d | 8d 0.3d | 59.7d 12.9d | 13.6d 83.3% | 98.0% 10.7d | 1.0d 2026-03-14 08:47:18 9.9 Kbit/s
dannenberg (DE) Yes Yes No N Yes Running, Valid, Fast 9.9 Mbit/s | 816.0 Kbit/s 9.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 69.3% | 98% 10.8d | 8d 0.3d | 11.3d 12.9d | 14.3d 69.3% | 98.0% 10.8d | 1.0d 2026-03-14 08:47:18 9.9 Kbit/s
dizum (NL) Yes Yes No N Yes Running, Valid, Fast 9.9 Mbit/s | 816.0 Kbit/s 9.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 82.4% | 98% 10.7d | 8d 0.3d | 45.8d 12.9d | 12.0d 82.4% | 98.0% 10.7d | 1.0d 2026-03-14 08:47:18 9.9 Kbit/s
faravahar (US) Yes Yes No N Yes Running, Valid, Fast 9.9 Mbit/s | 816.0 Kbit/s 9.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 85.7% | 98% 11.2d | 8d 0.4d | 55.1d 12.9d | 14.5d 85.7% | 98.0% 11.2d | 1.0d 2026-03-14 08:47:18 9.9 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, Fast 9.9 Mbit/s | 816.0 Kbit/s 9.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 86.0% | 98% 10.9d | 8d 0.4d | 61.4d 12.9d | 14.4d 86.0% | 98.0% 10.9d | 1.0d 2026-03-14 08:47:18 2160 bit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, Fast 9.9 Mbit/s | 816.0 Kbit/s 9.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 86.9% | 98% 10.1d | 8d 0.4d | 62.0d 12.9d | 14.5d 86.9% | 98.0% 10.1d | 1.0d 2026-03-14 08:47:18 9.9 Kbit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, Fast 9.9 Mbit/s | 816.0 Kbit/s 9.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 85.6% | 98% 11.2d | 8d 0.4d | 40.2d 12.9d | 14.3d 85.6% | 98.0% 11.2d | 1.0d 2026-03-14 08:47:18 2080 bit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, Stable 9.9 Mbit/s | 8.4 Mbit/s 9.9 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 84.3% | 98% 9.7d | 8d 19641.0d | 347.6d 12.9d | 15.5d 84.3% | 98.0% 9.7d | 9.8d 2026-03-14 08:47:18 6480 bit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, Fast 9.9 Mbit/s | 816.0 Kbit/s 9.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 85.4% | 98% 11.2d | 8d 0.4d | 55.7d 12.9d | 14.5d 85.4% | 98.0% 11.2d | 1.0d 2026-03-14 08:47:18 2320 bit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
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.
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.