View Relay "gatter"

Fingerprint: E068898472A6FAC41D424FB5E124136C4BA69507 | Family: 4 relays | /dev/null | AS34288 | Switzerland | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (15.9s, 58th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 96 Kbit/s Median
Stability
Not Overloaded | UP 4d 19h 51m ago | UP 37% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
2y 8mo 2w ago
BW Weight
0.01% of Network | 91 Mbit/s Observed By Relay
Version
0.4.9.5 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: WFU below threshold : Weighted Fractional Uptime 39.2% 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.
  • 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.
  • HSDir: WFU below threshold : WFU 39.2% 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
46.234.47.105:443
[2001:4b20:12:f001::105]:443
Exit Address
46.234.47.105
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Switzerland Switzerland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS34288
AS Name
Kantonsschule Zug (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.06% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (9/9 DA) 9/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 91.8 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 (1/9 DA) Median: 4.5d (1/9 DA above threshold)
Min/Max: 2.5d / 4839.6d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Uptime Below (0/9 DA) 4.8d (R) ≥12.0d - 14.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 (1/9 DA) 1/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 39.1% (0/9 DA above threshold)
Min/Max: 36.3% / 46.9% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 15.2d (9/9 DA above threshold)
Min/Max: 9.5d / 15.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (9/9 DA) 9/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 (1/9 DA) 1/9 DA assigned Stable ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 39.1% (0/9 DA above threshold)
Min/Max: 36.3% / 46.9% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 15.2d (9/9 DA above threshold)
Min/Max: 9.5d / 15.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 91.8 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (9/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-03-15 16:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
91.78 Mbit/s
Advertised Bandwidth
91.78 Mbit/s
Rate Limit
838.86 Mbit/s
Burst Limit
838.86 Mbit/s
Total Data
968 TB (5 years)
1mo: 4.8 TB | 6mo: 451 TB | 1y: 850 TB | 5y: 968 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 16:15:07

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
96.0 Kbit/s
Min / Max
80.0 Kbit/s / 216.0 Kbit/s
Deviation
136.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0106% of network (66th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0319% (57th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 4d 19h 51m ago
Overall Uptime (1M/6M/1Y/5Y)
37.9%/82.9%/91.4%/95.9%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (37.9%/82.9%/91.4%/95.9%)
Hibernating
No
Timestamps
First Seen
2y 8mo 2w ago (2023-07-01 00:00:00)
Last Seen
1h 45m 55s ago (2026-03-15 15:00:00)
Last Restarted
4d 19h 51m ago (2026-03-10 20:54:40)
Last Changed Address
2024-01-29 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-15 09:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
/dev/null
Family Configuration
Family Support
MyFamily Only (4) — Legacy only. Consider migrating to Happy Families. | View Full Family (4)
Happy Families (family-cert)
Effective Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 15.9s, 58th percentile)
Query Domain
7d6693c7d0be4f66920d63c3c1669b7c.e0688984.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
dotsrcExit4 (DK) 5796FE1EB5744EB363FDB499FFBC2F7933C0CA4A
Exit Address Used
46.234.47.105
Per-Instance Results
Cross Validation Attempt 1: Success, 17.0s (cv1_w3)
Cross Validation Attempt 2: Success, 12.5s (cv3_w3)
Cross Validation Attempt 3: Success, 18.4s (cv4_w3)
Tested: 2026-03-15 07:17:42 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  80
  143
  443
IPv6 Exit Policy Summary
accept: 
  80
  143
  443
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 46.234.32.0/19:*
reject 81.94.112.0/20:*
reject 85.158.24.0/21:*
reject 109.233.176.0/21:*
reject 216.218.128.0/17:*
reject 184.104.0.0/15:*
reject 64.71.128.0/18:*
accept *:80
accept *:143
accept *:443
reject *:*

Last fetch was at Sun, 15 Mar 2026 16:45:53 GMT.

Consensus Evaluation

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

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 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 Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 91.8 Mbit/s | 816.0 Kbit/s 91.8 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 39.2% | 98% 15.1d | 8d 4.5d | 59.7d 4.8d | 13.6d 39.2% | 98.0% 15.1d | 1.0d 2026-03-14 20:49:18 136.0 Kbit/s
dannenberg (DE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 91.8 Mbit/s | 816.0 Kbit/s 91.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 36.3% | 98% 14.4d | 8d 2.5d | 11.3d 4.8d | 14.3d 36.3% | 98.0% 14.4d | 1.0d 2026-03-14 20:49:18 80.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 91.8 Mbit/s | 816.0 Kbit/s 91.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 39.2% | 98% 15.2d | 8d 4.5d | 45.8d 4.8d | 12.0d 39.2% | 98.0% 15.2d | 1.0d 2026-03-14 20:49:18 80.0 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 91.8 Mbit/s | 816.0 Kbit/s 91.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 38.3% | 98% 15.7d | 8d 4.6d | 55.1d 4.8d | 14.5d 38.3% | 98.0% 15.7d | 1.0d 2026-03-14 20:49:18 80.0 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 91.8 Mbit/s | 816.0 Kbit/s 91.8 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 39.1% | 98% 15.2d | 8d 4.5d | 61.4d 4.8d | 14.4d 39.1% | 98.0% 15.2d | 1.0d 2026-03-14 20:49:18 216.0 Kbit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Exit 91.8 Mbit/s | 816.0 Kbit/s 91.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 41.3% | 98% 14.6d | 8d 4.6d | 62.0d 4.8d | 14.5d 41.3% | 98.0% 14.6d | 1.0d 2026-03-14 20:49:18 80.0 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 91.8 Mbit/s | 816.0 Kbit/s 91.8 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 38.1% | 98% 15.6d | 8d 4.5d | 40.2d 4.8d | 14.3d 38.1% | 98.0% 15.6d | 1.0d 2026-03-14 20:49:18 184.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Exit 91.8 Mbit/s | 8.4 Mbit/s 91.8 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 46.9% | 98% 9.5d | 8d 4839.6d | 347.6d 4.8d | 15.5d 46.9% | 98.0% 9.5d | 9.8d 2026-03-14 20:49:18 96.0 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 91.8 Mbit/s | 816.0 Kbit/s 91.8 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 38.4% | 98% 15.7d | 8d 4.6d | 55.7d 4.8d | 14.5d 38.4% | 98.0% 15.7d | 1.0d 2026-03-14 20:49:18 168.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). 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.