View Relay "DerrickJensen"

Fingerprint: E0023AC14180112A2FFF00A84C6049862BB3E6C3 | Family: 1 relay | 1187 EF45 9760 66ED 5AB5 5D50 9755... | AS16276 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
2/7 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | UP 1d 14h 5m ago
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 8 Mbit/s Observed By Relay
Version
0.4.9.14 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 8 Mbit/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 3.6% 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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: WFU below threshold : WFU 3.6% 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.
  • Low bandwidth authority measurements : Only 2/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.

Addresses
OR Address
vps-705b3e2c.vps.ovh.us
147.135.112.139: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
AS16276
AS Name
OVH SAS (BGP.tools)
AS Rarity
Common (score: 0/5, 13.25% consensus weight, 181 operators)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 8.1 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 (0/9 DA) Median: 1.6d (1/9 DA above threshold)
Min/Max: 1.5d / 181.7d (9/9 DA, Voting / Total Eligible)
≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Uptime Below (0/9 DA) 1.6d (R) ≥6.1d - 6.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 3.8% (0/9 DA above threshold)
Min/Max: 3.6% / 14.6% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 42.5d (9/9 DA above threshold)
Min/Max: 9.7d / 44.9d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (4/9 DA) 4/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 ≥4.8d - 7.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10748.8d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 3.8% (0/9 DA above threshold)
Min/Max: 3.6% / 14.6% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 42.5d (9/9 DA above threshold)
Min/Max: 9.7d / 44.9d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8.1 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.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-23 16:00:54).

Capacity (Relay Reported)
Observed Bandwidth
8.08 Mbit/s
Advertised Bandwidth
8.08 Mbit/s
Rate Limit
8.19 Mbit/s
Burst Limit
12.29 Mbit/s
Total Data
15 GB (6 months)
1mo: 3.3 GB | 6mo: 15 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-23 16:00:54

Measured By
2/7 Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, tor26
Median Measurement
8.1 Kbit/s
Min / Max
1760 bit/s / 8.1 Kbit/s
Deviation
6320 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0000% (3th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 1d 14h 5m 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 14h 6m ago (2026-10-22 03:00:00)
Last Seen
2h 6m 4s ago (2026-10-23 15:00:00)
Last Restarted
1d 14h 5m ago (2026-10-22 03:00:18)
Last Changed Address
2026-10-22 03:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-10-23 08:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
1187 EF45 9760 66ED 5AB5 5D50 9755 3391 D0BF 49BA Norris Thomlinson <norris@aktivix.org>
Family Configuration
Family Support
MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
E0023AC14180112A2FFF00A84C6049862BB3E6C3 (this relay)
Alleged Member: 1
(they don't list you back)
9C2BF9B1E30EBB1A3836FA04BEEE8CC192CC1E5B
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.14 on Linux
Version
0.4.9.14 — Recommended
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 Fri, 23 Oct 2026 17:05:48 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-23 16:00:54).

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 8.1 Mbit/s | 816.0 Kbit/s 8.1 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 3.6% | 98% 41.7d | 8d 1.5d | 4.8d 1.6d | 6.4d 3.6% | 98.0% 41.7d | 1.0d 2026-10-22 20:06:06 2400 bit/s
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 8.1 Mbit/s | 816.0 Kbit/s 8.1 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 6.3% | 98% 34.0d | 8d 2.1d | 5.8d 1.6d | 6.5d 6.3% | 98.0% 34.0d | 1.0d 2026-10-23 14:06:07 8.1 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 8.1 Mbit/s | 816.0 Kbit/s 8.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 4.9% | 98% 36.2d | 8d 1.7d | 7.6d 1.6d | 6.4d 4.9% | 98.0% 36.2d | 1.0d 2026-10-23 14:06:07 8.1 Kbit/s
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir 8.1 Mbit/s | 816.0 Kbit/s 8.1 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 3.8% | 98% 42.5d | 8d 1.6d | 8.0d 1.6d | 6.9d 3.8% | 98.0% 42.5d | 1.0d 2026-10-23 14:06:07 8.1 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 8.1 Mbit/s | 816.0 Kbit/s 8.1 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 3.6% | 98% 44.7d | 8d 1.6d | 7.7d 1.6d | 6.5d 3.6% | 98.0% 44.7d | 1.0d 2026-10-23 14:06:07 8.1 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 8.1 Mbit/s | 816.0 Kbit/s 8.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 3.8% | 98% 44.9d | 8d 1.7d | 7.9d 1.6d | 6.4d 3.8% | 98.0% 44.9d | 1.0d 2026-10-23 14:06:07 8.1 Kbit/s
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 8.1 Mbit/s | 816.0 Kbit/s 8.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 3.6% | 98% 44.1d | 8d 1.6d | 7.7d 1.6d | 6.4d 3.6% | 98.0% 44.1d | 1.0d 2026-10-23 14:06:07 8.1 Kbit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 8.1 Mbit/s | 8.4 Mbit/s 8.1 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 14.6% | 98% 9.7d | 8d 181.7d | 10748.8d 1.6d | 6.1d 14.6% | 98.0% 9.7d | 9.8d 2026-10-23 14:06:07 1760 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir 8.1 Mbit/s | 816.0 Kbit/s 8.1 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 3.8% | 98% 42.6d | 8d 1.6d | 7.9d 1.6d | 6.7d 3.8% | 98.0% 42.6d | 1.0d 2026-10-23 14:06:07 8.1 Kbit/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.