View Relay "safeRouter"

Family: 1 relay | email:team.node[]for-privacy.net | AS211507 | Netherlands | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 112 Kbit/s Median
Stability
Overloaded | UP 1w 20h 29m ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1w 20h 17m ago
BW Weight
0.01% of Network | 90 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: Time Known below threshold : Time Known 7.4 days is below 8 days requirement (0.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).
  • 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.
  • Write Bandwidth Limit Hit : Write rate limit (84 Mbit/s) was hit 4 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 (84 Mbit/s) was hit 4 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=84 Mbit/s, Burst=84 Mbit/s. Limits hit: Write=4, Read=4.

Connectivity and Location

Addresses
OR Address
lain.185.132.53.88.aluy.net
185.132.53.88:443
[2a14:c380:50:67::a]:443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS211507
AS Name
Julian Achter (BGP.tools)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 4/9 | HSDir: 3/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) 90.3 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 4.2d (1/9 DA above threshold)
Min/Max: 0.0d / 9721.9d (9/9 DA, Voting / Total Eligible)		 ≥22.2d - 53.9d (varies)
[Stricter] moria1: ≥405.5d
Uptime Below 7.9d (R) ≥15.8d - 16.3d (varies)
HSDir Prereq: Stable Below 4/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 9/9 authorities assigned Fast flag ≥5/9 authorities
WFU Meets Median: 99.9% (6/9 DA above threshold)
Min/Max: 16.9% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Below Median: 7.4d (0/9 DA above threshold)
Min/Max: 5.4d / 7.9d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets 9/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 4/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Meets Median: 99.9% (6/9 DA above threshold)
Min/Max: 16.9% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Below (need 0.6 more days) Median: 7.4d (0/9 DA above threshold)
Min/Max: 5.4d / 7.9d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 90.3 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 07:15:07).

Last fetch was at Thu, 29 Jan 2026 07:15:43 GMT.

Nickname
safeRouter
Fingerprint
85D22160B5DE12A8BE92F77CFA09C538920DCE57
AROI (?)
none
Contact
email:team.node[]for-privacy.net
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
85D22160B5DE12A8BE92F77CFA09C538920DCE57
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
90.30 Mbit/s | 83.89 Mbit/s| 83.89 Mbit/s| 83.89 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.01% | N/A | 0.03% | N/A
OR Address
lain.185.132.53.88.aluy.net | 185.132.53.88:443, [2a14:c380:50:67::a]:443
Exit Address
none
Dir Address
none
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS211507 | Julian Achter (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 1w 20h 29m ago
Seen (First | Last)
1w 20h 17m ago (2026-01-21 11:00:00) | 1h 17m 5s ago (2026-01-29 06:00:00)
Last Restarted
1w 20h 30m ago (2026-01-21 10:46:11)
Last Changed Address or Port
2026-01-21 11: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 07:15:07).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 4/9 | HSDir: 3/9 | Guard: 0/9
  • Reachability: IPv4: 9/9 | IPv6: 5/0
  • Consensus Weight (Dir. Auth.): Median: 112.0 Kbit/s | Min: 80.0 Kbit/s | Max: 168.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: Time Known below threshold: Time Known 7.4 days is below 8 days requirement (0.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).
    • 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.
    • Write Bandwidth Limit Hit: Write rate limit (84 Mbit/s) was hit 4 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 (84 Mbit/s) was hit 4 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=84 Mbit/s, Burst=84 Mbit/s. Limits hit: Write=4, Read=4.

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.) 112.0 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 99.9% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 7.4 days ≥8 days (all authorities) BELOW - need 0.6 more days
Guard BW (Relay Reported) 90.3 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 7.9d ≥15.8d - 16.3d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 4 days ≥22.2d - 53.9d (typical)
[Stricter] moria1: ≥405.5d 		BELOW - 1/9
Fast Speed (Relay Reported) 90.3 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) 99.9% ≥98.0% (from all auths) BELOW - 3/9
HSDir TK (Dir. Auth., tk) 7.4 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 3/9
IPv6 Reachable (Dir. Auth.) 5/5 tested ≥3/5 (majority) REACHABLE

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) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir 90.3 Mbit/s | 816.0 Kbit/s 90.3 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 7.4d | 8d 7.4d | 50.4d 7.9d | 16.7d 100.0% | 98.0% 7.4d | 1.0d 2026-01-29 02:29:33 128.0 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 90.3 Mbit/s | 816.0 Kbit/s 90.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 7.8d | 8d 3.4d | 22.2d 7.9d | 16.5d 99.9% | 98.0% 7.8d | 1.0d 2026-01-29 02:29:33 80.0 Kbit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast, Stable, HSDir 90.3 Mbit/s | 816.0 Kbit/s 90.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 7.9d | 8d 7.9d | 35.2d 7.9d | 16.3d 100.0% | 98.0% 7.9d | 1.0d 2026-01-29 02:29:33 80.0 Kbit/s
faravahar (US) Yes Yes N Yes — Valid, V2Dir, Fast 90.3 Mbit/s | 816.0 Kbit/s 90.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 82.6% | 98% 5.4d | 8d 0.0d | 47.3d 7.9d | 15.8d 82.6% | 98.0% 5.4d | 1.0d 2026-01-29 02:29:33 80.0 Kbit/s
gabelmoo (DE) Yes Yes Y Yes — Valid, V2Dir, Fast 90.3 Mbit/s | 816.0 Kbit/s 90.3 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 82.1% | 98% 5.5d | 8d 0.0d | 53.9d 7.9d | 16.3d 82.1% | 98.0% 5.5d | 1.0d 2026-01-29 02:29:33 168.0 Kbit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast, Stable, HSDir 90.3 Mbit/s | 816.0 Kbit/s 90.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 7.9d | 8d 7.9d | 54.6d 7.9d | 16.1d 100.0% | 98.0% 7.9d | 1.0d 2026-01-29 02:29:33 80.0 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 90.3 Mbit/s | 816.0 Kbit/s 90.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 16.9% | 98% 5.6d | 8d 0.0d | 55.0d 7.9d | 15.9d 16.9% | 98.0% 5.6d | 1.0d 2026-01-29 02:29:33 168.0 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable 90.3 Mbit/s | 8.4 Mbit/s 90.3 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 99.8% | 98% 5.5d | 8d 9721.9d | 405.5d 7.9d | 16.5d 99.8% | 98.0% 5.5d | 9.9d 2026-01-29 02:29:33 112.0 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 90.3 Mbit/s | 816.0 Kbit/s 90.3 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 7.9d | 8d 4.2d | 55.6d 7.9d | 17.1d 99.9% | 98.0% 7.9d | 1.0d 2026-01-29 02:29:33 152.0 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). 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.