View Relay "usNjBobVps4806"

Family: 1 relay | AS20473 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, HSDir, Running, Stable, V2Dir, Valid (6)
BW Verified
5/6 BW Auths Measured 7840 bit/s Median
Stability
Overloaded | UP 1mo 3w 1d ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1y 11mo 1w ago
BW Weight
0.00% of Network | 9 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • 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.
  • 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 (10 Mbit/s) was hit 485 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 (10 Mbit/s) was hit 1,708 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=10 Mbit/s, Burst=13 Mbit/s. Limits hit: Write=485, Read=1,708.

Connectivity and Location

Addresses
OR Address
149.28.58.137.vultrusercontent.com
149.28.58.137:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS20473
AS Name
The Constant Company, LLC (BGP.tools)

Flags and Eligibility

Current Flags (6): Stable, Fast, HSDir, Running, V2Dir, Valid
Eligible Flags (6): Guard: 0/9 | Stable: 8/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | V2Dir: 9/9 | Valid: 9/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Guard WFU Meets 100.0% (DA) ≥98% (all authorities)
Time Known Meets 301.5 days (DA) ≥8 days (all authorities)
Bandwidth Below 9.6 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Partial (8/9) 302 days (DA) ≥26.6d - 45.4d (varies)
Uptime Meets 52.1d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 9.6 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Meets 100.0% (DA) ≥98.0%
Time Known Meets 301.5 days (DA) ≥1.0d (most) / 9.9d (max)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname
usNjBobVps4806
Fingerprint
F192BD51EF2C9CA553646F28668D28A7AF1CAB0D
AROI (?)
none
Contact
none
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
F192BD51EF2C9CA553646F28668D28A7AF1CAB0D
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
9.59 Mbit/s | 9.59 Mbit/s| 10.49 Mbit/s| 12.58 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
149.28.58.137.vultrusercontent.com | 149.28.58.137:9001
Exit Address
none
Dir Address
none
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS20473 | The Constant Company, LLC (BGP.tools)
Flags: 6
Fast Fast HSDir HSDir Running Running Stable Stable V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (100.0%/100.0%/99.9%/99.4%)
Uptime (1M/6M/1Y/5Y)
100.0%/100.0%/99.9%/99.4%
Uptime / Downtime
UP 1mo 3w 1d ago
Seen (First | Last)
1y 11mo 1w ago (2024-02-03 20:00:00) | 1h 55m 1s ago (2026-01-10 03:00:00)
Last Restarted
1mo 3w 1d ago (2025-11-19 01:27:33)
Last Changed Address or Port
2024-02-03 20:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status)
0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Guard: 0/9 | Stable: 8/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 7840 bit/s | Min: 2480 bit/s | Max: 9.6 Kbit/s [Warning] High deviation
  • Identified Issues:
    • 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.
    • 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 (10 Mbit/s) was hit 485 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 (10 Mbit/s) was hit 1,708 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=10 Mbit/s, Burst=13 Mbit/s. Limits hit: Write=485, Read=1,708.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 7840 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 100.0% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 301.5 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 9.6 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 52.1d ≥19.1d - 19.7d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 302 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		PARTIAL - 8/9
Fast Speed (Relay Reported) 9.6 Mbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 100.0% ≥98.0% (from all auths) PARTIAL - 8/9
HSDir TK (Dir. Auth., tk) 301.5 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		PARTIAL - 8/9

Per-Authority Details

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority Running Valid 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 Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 9.6 Mbit/s | 816.0 Kbit/s 9.6 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 301.5d | 8d 301.5d | 47.0d 52.1d | 19.7d 100.0% | 98.0% 301.5d | 1.0d 2026-01-10 00:27:54 7840 bit/s
dannenberg (DE) Yes Yes N Yes Fast, HSDir, Running, Stable, V2Dir, Valid 9.6 Mbit/s | 816.0 Kbit/s 9.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 301.0d | 8d 301.0d | 35.7d 52.1d | 20.2d 100.0% | 98.0% 301.0d | 1.0d 2026-01-10 00:27:54 9.6 Kbit/s
dizum (NL) Yes Yes N Yes Fast, HSDir, Running, Stable, V2Dir, Valid 9.6 Mbit/s | 816.0 Kbit/s 9.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 30.9d | 8d 29.2d | 26.6d 52.1d | 20.4d 100.0% | 98.0% 30.9d | 1.0d 2026-01-10 00:27:54 9.6 Kbit/s
faravahar (US) Yes Yes N Yes Fast, HSDir, Running, Stable, V2Dir, Valid 9.6 Mbit/s | 816.0 Kbit/s 9.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 300.9d | 8d 300.9d | 41.9d 52.1d | 19.1d 100.0% | 98.0% 300.9d | 1.0d 2026-01-10 00:27:54 9.6 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 9.6 Mbit/s | 816.0 Kbit/s 9.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 301.7d | 8d 301.7d | 45.4d 52.1d | 19.6d 100.0% | 98.0% 301.7d | 1.0d 2026-01-10 00:27:54 2480 bit/s
longclaw (US) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 9.6 Mbit/s | 816.0 Kbit/s 9.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 300.8d | 8d 300.8d | 48.7d 52.1d | 19.5d 100.0% | 98.0% 300.8d | 1.0d 2026-01-10 00:27:54 9.6 Kbit/s
maatuska (SE) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 9.6 Mbit/s | 816.0 Kbit/s 9.6 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 74.2d | 8d 74.2d | 42.3d 52.1d | 19.4d 100.0% | 98.0% 74.2d | 1.0d 2026-01-10 00:27:54 3360 bit/s
moria1 (US) Yes Yes Y Yes Running, Stable, V2Dir, Valid 9.6 Mbit/s | 8.4 Mbit/s 9.6 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 9.9d | 8d 288.9d | 376.2d 52.1d | 20.4d 100.0% | 98.0% 9.9d | 9.9d 2026-01-10 00:27:54 6640 bit/s
tor26 (AT) Yes Yes Y Yes Fast, HSDir, Running, Stable, V2Dir, Valid 9.6 Mbit/s | 816.0 Kbit/s 9.6 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 301.8d | 8d 301.8d | 51.8d 52.1d | 19.7d 100.0% | 98.0% 301.8d | 1.0d 2026-01-10 00:27:54 2800 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). This is your relay's self-reported uptime from its 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.