View Relay "ams01"

Family: 3 relays | no | AS56630 | Netherlands | Linux

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Guard, Running, Stable, V2Dir, Valid (6)
BW Verified
5/6 BW Auths Measured 16 Kbit/s Median
Stability
Overloaded | UP 1mo 3w 3d ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
1y 11mo 3w ago
BW Weight
0.00% of Network | 18 Mbit/s Observed By Relay
Version
0.4.8.16 Not Recommended
Issues Detected:
  • 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.
  • Tor version not recommended : Running Tor version 0.4.8.16 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
  • General Overload Active : Relay reported general overload at 2026-01-07 09:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.
  • Write Bandwidth Limit Hit : Write rate limit (17 Mbit/s) was hit 11,030 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 (17 Mbit/s) was hit 7,598 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=17 Mbit/s, Burst=34 Mbit/s. Limits hit: Write=11,030, Read=7,598.

Addresses
OR Address
ams01.dn42.ventilaar.net
185.140.209.158:8443
[2a06:f901:1:100:300:ffff:1b1:a671]:8443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS56630
AS Name
Melbikomas UAB (BGP.tools)

Current Flags (6): Guard, Stable, Fast, Running, V2Dir, Valid
Eligible Flags (7): Guard: 9/9 | Stable: 6/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 311.7 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 18.1 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Partial (6/9) 312 days (DA) ≥26.6d - 45.4d (varies)
Uptime Meets 54.7d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 18.1 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Meets 100.0% (DA) ≥98.0%
Time Known Meets 311.7 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.

18.05 Mbit/s | 16.78 Mbit/s| 16.78 Mbit/s| 33.55 Mbit/s  Measured
0.00% | 0.00% | 0.00% | N/A
ams01.dn42.ventilaar.net | 185.140.209.158:8443, [2a06:f901:1:100:300:ffff:1b1:a671]:8443
none
none
Netherlands Netherlands
View on Interactive Map
AS56630 | Melbikomas UAB (BGP.tools)
Fast Fast Guard Guard Running Running Stable Stable V2Dir V2Dir Valid Valid
65.3%/88.8%/86.0%/93.1%
99.8%/100.0%/100.0%/99.2%
UP 1mo 3w 3d ago
1y 11mo 3w ago (2024-01-22 12:00:00) | 1h 55m ago (2026-01-10 03:00:00)
1mo 3w 3d ago (2025-11-16 12:29:14)
2024-01-29 19:00:00
No
Linux | Tor 0.4.8.16 on Linux
0.4.8.16 | No | obsolete

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: 9/9 | Stable: 6/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 16.8 Kbit/s | Min: 5840 bit/s | Max: 17.6 Kbit/s [Warning] High deviation
  • Identified Issues:
    • 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.
    • Tor version not recommended: Running Tor version 0.4.8.16 which is not on the recommended list.
      • Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
    • General Overload Active: Relay reported general overload at 2026-01-07 09:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
      • Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.
    • Write Bandwidth Limit Hit: Write rate limit (17 Mbit/s) was hit 11,030 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 (17 Mbit/s) was hit 7,598 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=17 Mbit/s, Burst=34 Mbit/s. Limits hit: Write=11,030, Read=7,598.

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.) 16.8 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) 311.7 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 18.1 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 54.7d ≥19.1d - 19.7d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 312 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d
PARTIAL - 6/9
Fast Speed (Relay Reported) 18.1 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) 311.7 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d
PARTIAL - 8/9
IPv6 Reachable (Dir. Auth.) 7/7 tested ≥4/7 (majority) REACHABLE

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 Fast, Guard, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 816.0 Kbit/s 18.1 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 311.7d | 8d 179.6d | 47.0d 54.7d | 19.7d 100.0% | 98.0% 311.7d | 1.0d 2026-01-09 12:11:00 16.8 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Fast, Guard, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 816.0 Kbit/s 18.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.8% | 98% 30.9d | 8d 17.5d | 35.7d 54.7d | 20.2d 99.8% | 98.0% 30.9d | 1.0d 2026-01-09 12:11:00 16.8 Kbit/s
dizum (NL) Yes Yes N Yes Fast, Guard, HSDir, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 816.0 Kbit/s 18.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.7% | 98% 27.7d | 8d 15.4d | 26.6d 54.7d | 20.4d 99.7% | 98.0% 27.7d | 1.0d 2026-01-09 12:11:00 16.8 Kbit/s
faravahar (US) Yes Yes N Yes Yes Fast, Guard, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 816.0 Kbit/s 18.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 226.3d | 8d 94.3d | 41.9d 54.7d | 19.1d 100.0% | 98.0% 226.3d | 1.0d 2026-01-09 12:11:00 16.8 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Fast, HSDir, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 816.0 Kbit/s 18.1 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 463.7d | 8d 267.2d | 45.4d 54.7d | 19.6d 100.0% | 98.0% 463.7d | 1.0d 2026-01-09 12:11:00 6240 bit/s
longclaw (US) Yes Yes Y Yes Fast, Guard, HSDir, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 816.0 Kbit/s 18.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 462.3d | 8d 266.4d | 48.7d 54.7d | 19.5d 100.0% | 98.0% 462.3d | 1.0d 2026-01-09 12:11:00 16.8 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Fast, Guard, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 816.0 Kbit/s 18.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 99.9% | 98% 55.3d | 8d 31.9d | 42.3d 54.7d | 19.4d 99.9% | 98.0% 55.3d | 1.0d 2026-01-09 12:11:00 17.6 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Fast, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 8.4 Mbit/s 18.1 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 99.5% | 98% 9.7d | 8d 8671.8d | 376.2d 54.7d | 20.4d 99.5% | 98.0% 9.7d | 9.9d 2026-01-09 12:11:00 16.0 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Fast, Running, Stable, V2Dir, Valid 18.1 Mbit/s | 816.0 Kbit/s 18.1 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 463.0d | 8d 266.8d | 51.8d 54.7d | 19.7d 100.0% | 98.0% 463.0d | 1.0d 2026-01-09 12:11:00 5840 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.