View Relay "jayrock"

Family: 1 relay | miwtor@web.de | AS63949 | India | Linux

Health Status

Consensus
Not In Consensus (3/9 Directory Auths, need 5)
Flags
Running, V2Dir, Valid (3)
BW Verified
1/6 BW Auths Measured 11 Kbit/s Median
Stability
Not Overloaded | DOWN 2d 22h 45m ago
Reachability
IPv4: 3/9 | v6: 2/8 (Directory Auths)
First Seen
3d 9h 47m ago
BW Weight
11 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Not in consensus : Only 3/9 authorities voted for this relay (need 5)
    Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
  • IPv4 reachability issues : Only 3/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, faravahar, gabelmoo, longclaw, maatuska, moria1. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
  • Guard: bandwidth below threshold : Observed bandwidth 1.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.4 days is below 8 days requirement (4.6 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.
  • 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: 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.
  • 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.
  • 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 1/6 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.

Connectivity and Location

Addresses
OR Address
45-79-125-252.ip.linodeusercontent.com
45.79.125.252:9001
[2400:8904::2000:b2ff:fe7e:a688]:9001
Reachability (Directory Authorities)
IPv4
3/9
IPv6
2/8 (1 don't test)
Location
Country
India India
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS63949
AS Name
Akamai Technologies, Inc. (BGP.tools)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (0): Running: 3/9 | Valid: 3/9 | V2Dir: 3/9 | Fast: 2/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Meets (≥100 KB/s) 11.5 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 3.4d (0/9 DA above threshold)
Min/Max: 3.4d / 3.4d (3/9 DA, Voting / Total Eligible)		 ≥22.0d - 54.0d (varies)
[Stricter] moria1: ≥405.5d
Uptime Below 1.3d (R) ≥9.7d - 10.1d (varies)
HSDir Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 2/9 authorities assigned Fast flag ≥5/9 authorities
WFU Meets Median: 100.0% (3/9 DA above threshold) ≥98.0%
Time Known Below Median: 3.4d (0/9 DA above threshold)
Min/Max: 3.4d / 3.4d (3/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below 2/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 0/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Below 3/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Meets Median: 100.0% (3/9 DA above threshold) ≥98% (all authorities)
Time Known Below (need 4.6 more days) Median: 3.4d (0/9 DA above threshold)
Min/Max: 3.4d / 3.4d (3/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 11.5 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-29 14:45:07).

Last fetch was at Thu, 29 Jan 2026 14:45:42 GMT.

Nickname
jayrock
Fingerprint
D7027BBD1E4414E893A7A115AA55474AB3B281CD
AROI (?)
none
Contact
miwtor@web.de
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
D7027BBD1E4414E893A7A115AA55474AB3B281CD
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
11.47 Mbit/s | 11.47 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Not Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
N/A | N/A | N/A | N/A
OR Address
45-79-125-252.ip.linodeusercontent.com | 45.79.125.252:9001, [2400:8904::2000:b2ff:fe7e:a688]:9001
Exit Address
none
Dir Address
none
Country
India India
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS63949 | Akamai Technologies, Inc. (BGP.tools)
Flags: 3
Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Uptime / Downtime
DOWN 2d 22h 45m ago
Seen (First | Last)
3d 9h 47m ago (2026-01-26 05:00:00) | 2d 22h 47m ago (2026-01-26 16:00:00)
Last Restarted
1d 8h 22m ago (2026-01-28 06:24:22)
Last Changed Address or Port
2026-01-26 05: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-29 14:45:07).

  • Consensus Status (need ≥5/9): Not In Consensus — 3/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 3/9 | Valid: 3/9 | V2Dir: 3/9 | Fast: 2/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 3/9 | IPv6: 2/8 (1 don't test)
  • Consensus Weight (Dir. Auth.): Median: 11.5 Kbit/s | Min: 8 bit/s | Max: 11.5 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Not in consensus: Only 3/9 authorities voted for this relay (need 5)
      • Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
    • IPv4 reachability issues: Only 3/9 authorities can reach this relay
      • Suggestion: Authorities that cannot reach you: bastet, faravahar, gabelmoo, longclaw, maatuska, moria1. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
    • Guard: bandwidth below threshold: Observed bandwidth 1.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.4 days is below 8 days requirement (4.6 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.
    • 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: 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.
    • 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.
    • 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 1/6 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.

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.) 3/9 authorities ≥5/9 (majority) NOT IN CONSENSUS
Running (IPv4 Reachable) 3/9 authorities reached this relay ≥5/9 (majority) NOT RUNNING
Valid 3/9 (Running + Valid Descriptor) ≥5/9 (majority) NOT VALID
Consensus Weight (Dir. Auth.) 11.5 Kbit/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) 3.4 days ≥8 days (all authorities) BELOW - need 4.6 more days
Guard BW (Relay Reported) 11.5 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 1.3d ≥9.7d - 10.1d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 3 days ≥22.0d - 54.0d (typical)
[Stricter] moria1: ≥405.5d 		BELOW - 0/9
Fast Speed (Relay Reported) 11.5 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) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 3.4 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/9
IPv6 Reachable (Dir. Auth.) 2/8 tested ≥5/8 (majority) PARTIAL

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 v6 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) No — Y No — — — — — — — — — — — —
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.4d | 8d 3.4d | 22.0d 1.3d | 10.1d 100.0% | 98.0% 3.4d | 1.0d 2026-01-29 12:42:28 11.5 Kbit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.4d | 8d 3.4d | 34.6d 1.3d | 10.1d 100.0% | 98.0% 3.4d | 1.0d 2026-01-29 12:42:28 11.5 Kbit/s
faravahar (US) No — N No — — — — — — — — — — — —
gabelmoo (DE) No — Y No — — — — — — — — — — — —
longclaw (US) No — Y No — — — — — — — — — — — —
maatuska (SE) No — Y No — — — — — — — — — — — —
moria1 (US) No — Y No — — — — — — — — — — — —
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir 11.5 Mbit/s | 816.0 Kbit/s 11.5 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.4d | 8d 3.4d | 55.9d 1.3d | 11.1d 100.0% | 98.0% 3.4d | 1.0d 2026-01-29 12:42:28 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). 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.