View Relay "sneed"

Fingerprint: D0968EE8B66665E15B8204AACF310E820AF8D799 | Family: 1 relay | nyc@bikerider.com | AS14061 | United States of America | Linux

Health Status

Consensus
In Consensus (8/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (15.8s, 42nd percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/7 BW Auths Measured 2236 bit/s Median
Stability
Overloaded | UP 3d 41m 29s ago
Reachability
IPv4: 8/9 (Directory Auths)
First Seen
3d 11m 26s ago
BW Weight
0.00% of Network | 3 Mbit/s Observed By Relay
Version
0.4.9.11 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 0.4 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: Time Known below threshold : Time Known 3.0 days is below 8 days requirement (5.0 more days needed)
    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 : 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.
  • 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 (3 Mbit/s) was hit 13 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 (3 Mbit/s) was hit 26 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay
  • Rate Limit Configuration: Configured limits: Rate=3 Mbit/s, Burst=7 Mbit/s. Limits hit: Write=13, Read=26.

Connectivity and Location

Addresses
OR Address
138.197.124.121:443
Exit Address
138.197.124.121
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14061
AS Name
DigitalOcean, LLC (BGP.tools)
AS Rarity
Emerging (score: 1/5, 0.57% consensus weight, 73 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 5/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 8/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/9 DA) 8/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Below (0/1 DA) 0/1 tested authorities reached relay ≥1/1 tested (majority) (≥1/1 DA)
Valid Descriptor Meets (8/9 DA) 8/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (8/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 3.5 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: 3.0d (0/9 DA above threshold)
Min/Max: 0.9d / 3.0d (8/9 DA, Voting / Total Eligible)		 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Uptime Below (0/9 DA) 3.0d (R) ≥4.3d - 5.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (6/9 DA) Majority: 100.0% (6/9 DA)
Min/Med/Max: 63.1% / 100.0% / 100.0% (8/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 3.0d (0/9 DA above threshold)
Min/Max: 2.5d / 3.0d (8/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (6/9 DA) Majority: 100.0% (6/9 DA)
Min/Med/Max: 63.1% / 100.0% / 100.0% (8/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.0 more days) Median: 3.0d (0/9 DA above threshold)
Min/Max: 2.5d / 3.0d (8/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 3.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (8/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-07-03 03:02:32).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
3.48 Mbit/s
Advertised Bandwidth
3.28 Mbit/s
Rate Limit
3.28 Mbit/s
Burst Limit
6.55 Mbit/s
Total Data
713 MB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-03 03:02:32

Measured By
4/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, gabelmoo
Median Measurement
2236.0 bit/s
Min / Max
8 bit/s / 3272 bit/s
Deviation
3264 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (0th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 3d 41m 29s 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
3d 11m 26s ago (2026-06-30 03:00:00)
Last Seen
2h 11m 26s ago (2026-07-03 01:00:00)
Last Restarted
3d 41m 29s ago (2026-06-30 02:29:57)
Last Changed Address
2026-06-30 03:00:00
[Warning] OVERLOADED — Rate limits hit W:13 R:26 (limit: 3 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
3.28 Mbit/s
Burst Limit
6.55 Mbit/s
Write Limit Hit
13 times
Read Limit Hit
26 times
Last Reported
22 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-02 19:00 UTC

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

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 15.8s, 42nd percentile)
Query Domain
539535ba5b8d4b48ad730bffe2238c32.d0968ee8.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
4532mLiskamm (CH) BA2AD0818B8D764F645A4116343BB71406D9C931
Exit Address Used
138.197.124.121
Per-Instance Results
Cross Validation Attempt 1: Success, 20.9s (cv1_w3)
Cross Validation Attempt 2: Success, 11.4s (cv2_w3)
Cross Validation Attempt 3: Success, 16.5s (cv3_w3)
Cross Validation Attempt 4: Success, 14.3s (cv4_w3)
Tested: 2026-07-02 19:15:28 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  445
  465
  587
  6881-6999
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 138.197.124.121:*
reject *:25
reject *:465
reject *:587
reject *:6881-6999
reject *:445
accept *:*

Last fetch was at Fri, 03 Jul 2026 03:11:23 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-03 03:02:32).

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, Fast, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.0d | 8d 3.0d | 48.4d 3.0d | 5.1d 100.0% | 98.0% 3.0d | 1.0d 2026-07-02 08:30:12 3272 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.4% | 98% 2.5d | 8d 1.4d | 10.1d 3.0d | 5.2d 96.4% | 98.0% 2.5d | 1.0d 2026-07-02 08:30:12 3272 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.0d | 8d 3.0d | 25.9d 3.0d | 5.2d 100.0% | 98.0% 3.0d | 1.0d 2026-07-02 08:30:12 3272 bit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 63.1% | 98% 2.8d | 8d 0.9d | 28.4d 3.0d | 5.2d 63.1% | 98.0% 2.8d | 1.0d 2026-07-02 08:30:12 3272 bit/s
gabelmoo (DE) No — — — Y No — — — — — — — — — — —
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.0d | 8d 3.0d | 57.2d 3.0d | 5.4d 100.0% | 98.0% 3.0d | 1.0d 2026-07-02 08:30:12 1200 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.0d | 8d 3.0d | 30.6d 3.0d | 5.3d 100.0% | 98.0% 3.0d | 1.0d 2026-07-02 08:30:12 680 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 3.5 Mbit/s | 8.4 Mbit/s 3.5 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.6d | 8d 3.0d | 1364.1d 3.0d | 5.4d 100.0% | 98.0% 2.6d | 9.8d 2026-07-02 08:30:12 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 3.5 Mbit/s | 816.0 Kbit/s 3.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.0d | 8d 3.0d | 53.1d 3.0d | 5.4d 100.0% | 98.0% 3.0d | 1.0d 2026-07-02 08:30:12 8 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.