View Relay "goodvikings"

Fingerprint: F55B95108CB1A788E2C157B932A0739EFD50630C | Family: 1 relay | ramo at goodvikings dot com | AS19318 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Stable, Exit (5)
DNS Health
Healthy (8.0s, 4th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 232 bit/s Median
Stability
Overloaded | UP 1w 2d 4h ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
11mo 3w 5d ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.8.21 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: bandwidth below threshold : Observed bandwidth 0.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.
  • 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.
  • 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 352 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 8,665 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=2 Mbit/s. Limits hit: Write=352, Read=8,665.

Connectivity and Location

Addresses
OR Address
161.129.68.162:9001
Exit Address
161.129.68.162
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
AS19318
AS Name
Interserver, Inc (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 3 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Stable, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 8/9 | HSDir: 3/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
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) 1.7 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 (2/9 DA) Median: 49.0d (1/9 DA above threshold)
Min/Max: 2.2d / 99.6d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
Uptime Below (0/9 DA) 9.2d (R) ≥9.7d - 12.6d (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 Meets (8/9 DA) 8/9 DA assigned Stable ≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Median: 99.9% (8/9 DA above threshold)
Min/Max: 97.6% / 99.9% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 49.1d (9/9 DA above threshold)
Min/Max: 9.7d / 49.4d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
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 Meets (8/9 DA) 8/9 DA assigned Stable ≥11.3d - 53.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.0d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Median: 99.9% (8/9 DA above threshold)
Min/Max: 97.6% / 99.9% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 49.1d (9/9 DA above threshold)
Min/Max: 9.7d / 49.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.7 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 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-03-15 19:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.66 Mbit/s
Advertised Bandwidth
1.64 Mbit/s
Rate Limit
1.64 Mbit/s
Burst Limit
1.64 Mbit/s
Total Data
2.8 TB (1 year)
1mo: 188 GB | 6mo: 1.6 TB | 1y: 2.8 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 19:15:08

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
232 bit/s
Min / Max
80 bit/s / 1632 bit/s
Deviation
1552 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 1w 2d 4h ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/94.8%/97.3%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/94.8%/97.3%/0.0%)
Hibernating
No
Timestamps
First Seen
11mo 3w 5d ago (2025-03-24 13:00:00)
Last Seen
1h 15m 39s ago (2026-03-15 18:00:00)
Last Restarted
1w 2d 4h ago (2026-03-06 14:39:30)
Last Changed Address
2025-03-24 13:00:00
[Warning] OVERLOADED — Rate limits hit W:352 R:8665 (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
1.64 Mbit/s
Burst Limit
1.64 Mbit/s
Write Limit Hit
352 times
Read Limit Hit
8,665 times
Last Reported
23 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-15 12:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
ramo at goodvikings dot com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
F55B95108CB1A788E2C157B932A0739EFD50630C (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.8.21 on Linux
Version
0.4.8.21 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Healthy (avg. 8.0s, 4th percentile)
Query Domain
ebcae8ca21c044d6b1cff3336fe87d25.f55b9510.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
xavierwulf (US) A0964C4976FEEF30BAB791DDDDBA55B915916B5A
Exit Address Used
161.129.68.162
Per-Instance Results
Cross Validation Attempt 1: Success, 8.0s (cv1_w4)
Cross Validation Attempt 2: Success, 7.2s (cv2_w4)
Cross Validation Attempt 3: Success, 8.7s (cv3_w4)
Cross Validation Attempt 4: Success, 8.1s (cv4_w4)
Tested: 2026-03-15 07:22:30 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  53
  80-81
  443
  3128
  8008
  8080
IPv6 Exit Policy Summary
None
Full 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 161.129.68.162:*
reject 62.250.11.0/24:*
reject 87.255.51.229:*
reject 212.227.20.19:*
reject 54.83.43.69:*
reject 192.42.116.41:*
reject 198.98.103.253:*
reject 192.42.119.41:*
reject 142.0.36.234:*
reject 82.165.37.26:*
reject 217.112.35.100:*
reject 199.27.128.0/21:*
reject 173.245.48.0/20:*
reject 103.21.244.0/22:*
reject 103.22.200.0/22:*
reject 103.31.4.0/22:*
reject 141.101.64.0/18:*
reject 108.162.192.0/18:*
reject 190.93.240.0/20:*
reject 188.114.96.0/20:*
reject 197.234.240.0/22:*
reject 198.41.128.0/17:*
reject 162.158.0.0/15:*
reject 104.16.0.0/12:*
accept *:53
accept *:80
accept *:81
accept *:443
accept *:3128
accept *:8008
accept *:8080
reject *:*

Last fetch was at Sun, 15 Mar 2026 19:15:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-15 19:15:08).

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 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 Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 49.0d | 8d 48.8d | 56.9d 9.2d | 11.9d 99.9% | 98.0% 49.0d | 1.0d 2026-03-15 14:40:19 232 bit/s
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 16.5d | 8d 2.2d | 11.3d 9.2d | 12.6d 97.6% | 98.0% 16.5d | 1.0d 2026-03-15 14:40:19 1632 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 49.3d | 8d 49.0d | 43.1d 9.2d | 9.7d 99.9% | 98.0% 49.3d | 1.0d 2026-03-15 14:40:19 1632 bit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 49.4d | 8d 49.3d | 53.0d 9.2d | 12.7d 99.9% | 98.0% 49.4d | 1.0d 2026-03-15 14:40:19 1632 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 49.4d | 8d 49.3d | 58.1d 9.2d | 12.6d 99.9% | 98.0% 49.4d | 1.0d 2026-03-15 14:40:19 80 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 47.4d | 8d 47.3d | 61.0d 9.2d | 12.7d 99.9% | 98.0% 47.4d | 1.0d 2026-03-15 14:40:19 1632 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 49.1d | 8d 48.9d | 40.7d 9.2d | 12.6d 99.9% | 98.0% 49.1d | 1.0d 2026-03-15 14:40:19 80 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.7 Mbit/s | 8.4 Mbit/s 1.7 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 9.7d | 8d 99.6d | 366.0d 9.2d | 15.4d 99.6% | 98.0% 9.7d | 9.9d 2026-03-15 14:40:19 208 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 49.4d | 8d 49.3d | 53.7d 9.2d | 12.7d 99.9% | 98.0% 49.4d | 1.0d 2026-03-15 14:40:19 80 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.