View Relay "GrmmlDag"

Family: 2 relays | Nurtic-Vibe <nurtic-vibe AT grmml DOT eu> | AS24940 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, Stable, V2Dir, Valid (5)
BW Verified
5/6 BW Auths Measured 320 Kbit/s Median
Stability
Not Overloaded | UP 4h 9m 56s ago | UP 89% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
7y 3mo 1w ago
BW Weight
0.03% of Network | 278 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 96.5% is below 98% requirement
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • HSDir: WFU below threshold : WFU 96.5% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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.

Connectivity and Location

Addresses
OR Address
dag.grmml.net
213.239.215.221:9001
[2a01:4f8:a0:90b0:789d:6a4:95f3:a78c]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS24940
AS Name
Hetzner Online GmbH (BGP.tools)

Flags and Eligibility

Current Flags (5): Stable, Fast, Running, V2Dir, Valid
Eligible Flags (4): Guard: 0/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 0/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 Below 96.5% (DA) ≥98% (all authorities)
Time Known Meets 31.7 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 278.9 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 32 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 0.2d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 278.9 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 96.5% (DA) ≥98.0%
Time Known Meets 31.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.

Nickname
GrmmlDag
Fingerprint
021DDCD687FD505B7EA7E75DA6CEF0D778AA07FB
AROI (?)
none
Contact
Nurtic-Vibe <nurtic-vibe AT grmml DOT eu>
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Members: 2 (View) 
021DDCD687FD505B7EA7E75DA6CEF0D778AA07FB
CBBA40F7D9F284F47A243EE2C081E96682741D22
Alleged Family Members: 3 
8C00FA7369A7A308F6A137600F0FA07990D9D451
CD36AF2A13B2CB70FDAA1096B9C30171EEC21AC9
FFA656D7A0C9ECDF6AB295C84B4C4D9449B63F1A
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
278.92 Mbit/s | 278.92 Mbit/s| 524.29 Mbit/s| 786.43 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.03% | N/A | 0.10% | N/A
OR Address
dag.grmml.net | 213.239.215.221:9001, [2a01:4f8:a0:90b0:789d:6a4:95f3:a78c]:9001
Exit Address
none
Dir Address
none
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS24940 | Hetzner Online GmbH (BGP.tools)
Flags: 5
Fast Fast Running Running Stable Stable V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (89.5%/98.0%/98.7%/95.5%)
Uptime (1M/6M/1Y/5Y)
89.5%/98.0%/98.7%/95.5%
Uptime / Downtime
UP 4h 9m 56s ago
Seen (First | Last)
7y 3mo 1w ago (2018-10-03 13:00:00) | 1h 54m 34s ago (2026-01-10 03:00:00)
Last Restarted
4h 17m 2s ago (2026-01-10 00:37:32)
Last Changed Address or Port
2022-01-15 16: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-10 04:46:16).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Guard: 0/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 0/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: 320.0 Kbit/s | Min: 80.0 Kbit/s | Max: 640.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 96.5% is below 98% requirement
      • Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
    • HSDir: WFU below threshold: WFU 96.5% below 98% required for HSDir
      • Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
    • 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.

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.) 320.0 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 96.5% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 31.7 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 278.9 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 0.2d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 32 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 278.9 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) 96.5% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 31.7 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 0/9
IPv6 Reachable (Dir. Auth.) 7/7 tested ≥4/7 (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 Fast, Running, Stable, V2Dir, Valid 278.9 Mbit/s | 816.0 Kbit/s 278.9 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 96.5% | 98% 31.7d | 8d 13.9d | 47.0d 0.2d | 19.7d 96.5% | 98.0% 31.7d | 1.0d 2026-01-10 03:09:55 320.0 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Fast, Running, Stable, V2Dir, Valid 278.9 Mbit/s | 816.0 Kbit/s 278.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.4% | 98% 18.5d | 8d 5.4d | 35.7d 0.2d | 20.2d 93.4% | 98.0% 18.5d | 1.0d 2026-01-10 03:09:55 80.0 Kbit/s
dizum (NL) Yes Yes N Yes — Fast, Running, V2Dir, Valid 278.9 Mbit/s | 816.0 Kbit/s 278.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.5% | 98% 15.3d | 8d 4.5d | 26.6d 0.2d | 20.4d 92.5% | 98.0% 15.3d | 1.0d 2026-01-10 03:09:55 80.0 Kbit/s
faravahar (US) Yes Yes N Yes Yes Fast, Running, Stable, V2Dir, Valid 278.9 Mbit/s | 816.0 Kbit/s 278.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.6% | 98% 17.8d | 8d 5.5d | 41.9d 0.2d | 19.1d 93.6% | 98.0% 17.8d | 1.0d 2026-01-10 03:09:55 80.0 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Fast, Running, Stable, V2Dir, Valid 278.9 Mbit/s | 816.0 Kbit/s 278.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 96.5% | 98% 30.9d | 8d 23.8d | 45.4d 0.2d | 19.6d 96.5% | 98.0% 30.9d | 1.0d 2026-01-10 03:09:55 600.0 Kbit/s
longclaw (US) Yes Yes Y Yes — Fast, Running, Stable, V2Dir, Valid 278.9 Mbit/s | 816.0 Kbit/s 278.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 93.8% | 98% 18.0d | 8d 7.8d | 48.7d 0.2d | 19.5d 93.8% | 98.0% 18.0d | 1.0d 2026-01-10 03:09:55 80.0 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Fast, Running, Stable, V2Dir, Valid 278.9 Mbit/s | 816.0 Kbit/s 278.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 93.7% | 98% 18.7d | 8d 7.9d | 42.3d 0.2d | 19.4d 93.7% | 98.0% 18.7d | 1.0d 2026-01-10 03:09:55 536.0 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Fast, Running, Stable, V2Dir, Valid 278.9 Mbit/s | 8.4 Mbit/s 278.9 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 90.2% | 98% 9.7d | 8d 9964.9d | 376.2d 0.2d | 20.4d 90.2% | 98.0% 9.7d | 9.9d 2026-01-10 03:09:55 344.0 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Fast, Running, Stable, V2Dir, Valid 278.9 Mbit/s | 816.0 Kbit/s 278.9 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 95.9% | 98% 27.8d | 8d 8.8d | 51.8d 0.2d | 19.7d 95.9% | 98.0% 27.8d | 1.0d 2026-01-10 03:09:55 640.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.