View Relay "zgato"

Family: 1 relay | tor@zgato.ru | AS213438 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 104 Kbit/s Median
Stability
Not Overloaded | UP 1w 8h 50m ago | UP 92% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
1w 1d 7h ago
BW Weight
0.01% of Network | 104 Mbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 92.6% 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.
  • Guard: Time Known below threshold : Time Known 6.4 days is below 8 days requirement (1.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.
  • HSDir: WFU below threshold : WFU 92.6% 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
50.118.225.16:9001
[2a0f:ca80:1337::da0:c1c5]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS213438
AS Name
ColocaTel Inc. (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.40% consensus weight, 5 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 5/9 | HSDir: 4/9 | Guard: 4/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Fast Speed Meets (≥100 KB/s) 104.2 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 8.1d (1/9 DA above threshold)
Min/Max: 0.7d / 17735.3d (9/9 DA, Voting / Total Eligible)		 ≥21.9d - 51.8d (varies)
[Stricter] moria1: ≥454.5d
Uptime Below 7.4d (R) ≥6.3d - 7.5d (varies)
HSDir Prereq: Stable Meets 5/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 9/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 92.6% (4/9 DA above threshold)
Min/Max: 90.4% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Below Median: 6.4d (4/9 DA above threshold)
Min/Max: 5.6d / 8.3d (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 Meets 5/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 92.6% (4/9 DA above threshold)
Min/Max: 90.4% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Below (need 1.6 more days) Median: 6.4d (4/9 DA above threshold)
Min/Max: 5.6d / 8.3d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 104.2 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-304.0 Mbit/s

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

Last fetch was at Wed, 11 Feb 2026 20:45:45 GMT.

Nickname
zgato
Fingerprint
8369EAF7360D3980C3AD0A3C328D6016921BF165
AROI (?)
none
Contact
tor@zgato.ru
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
8369EAF7360D3980C3AD0A3C328D6016921BF165
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
104.22 Mbit/s | 104.22 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.01% | N/A | 0.03% | N/A
OR Address
50.118.225.16:9001, [2a0f:ca80:1337::da0:c1c5]:9001
Exit Address
none
Dir Address
none
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS213438 | ColocaTel Inc. (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
93.4%/—/—/—
Uptime (1M/6M/1Y/5Y)
92.8%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 1w 8h 50m ago
Seen (First | Last)
1w 1d 7h ago (2026-02-03 13:00:00) | 1h 47m 19s ago (2026-02-11 19:00:00)
Last Restarted
1w 8h 51m ago (2026-02-04 11:55:45)
Last Changed Address or Port
2026-02-03 13:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.22 on Linux
Version (Running | Recommended | Status)
0.4.8.22 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-02-11 19:45: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: 5/9 | HSDir: 4/9 | Guard: 4/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 104.0 Kbit/s | Min: 80.0 Kbit/s | Max: 200.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 92.6% 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.
    • Guard: Time Known below threshold: Time Known 6.4 days is below 8 days requirement (1.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.
    • HSDir: WFU below threshold: WFU 92.6% 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.) 104.0 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 92.6% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 6.4 days ≥8 days (all authorities) BELOW - need 1.6 more days
Guard BW (Relay Reported) 104.2 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-304.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 7.4d ≥6.3d - 7.5d (typical) BELOW - 3/9
Stable MTBF (Dir. Auth., mtbf) 8 days ≥21.9d - 51.8d (typical)
[Stricter] moria1: ≥454.5d 		BELOW - 1/9
Fast Speed (Relay Reported) 104.2 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) 92.6% ≥98.0% (from all auths) BELOW - 4/9
HSDir TK (Dir. Auth., tk) 6.4 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 4/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 Running, Valid, V2Dir, Fast 104.2 Mbit/s | 816.0 Kbit/s 104.2 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 6.4d | 8d 0.8d | 51.8d 7.4d | 7.5d 92.6% | 98.0% 6.4d | 1.0d 2026-02-11 13:18:22 104.0 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 104.2 Mbit/s | 712.0 Kbit/s 104.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 90.4% | 98% 5.9d | 6d 0.7d | 21.9d 7.4d | 6.4d 90.4% | 98.0% 5.9d | 1.0d 2026-02-11 13:18:22 80.0 Kbit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast 104.2 Mbit/s | 696.0 Kbit/s 104.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 91.9% | 98% 6.4d | 6d 0.9d | 27.7d 7.4d | 6.3d 91.9% | 98.0% 6.4d | 1.0d 2026-02-11 13:18:22 80.0 Kbit/s
faravahar (US) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 104.2 Mbit/s | 816.0 Kbit/s 104.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 8.3d | 8d 8.3d | 47.9d 7.4d | 7.5d 100.0% | 98.0% 8.3d | 1.0d 2026-02-11 13:18:22 80.0 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 104.2 Mbit/s | 816.0 Kbit/s 104.2 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 8.3d | 8d 8.3d | 60.1d 7.4d | 7.5d 100.0% | 98.0% 8.3d | 1.0d 2026-02-11 13:18:22 176.0 Kbit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 104.2 Mbit/s | 816.0 Kbit/s 104.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 8.1d | 8d 8.1d | 61.0d 7.4d | 7.3d 100.0% | 98.0% 8.1d | 1.0d 2026-02-11 13:18:22 80.0 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Valid, V2Dir, Fast 104.2 Mbit/s | 816.0 Kbit/s 104.2 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 91.8% | 98% 5.8d | 8d 0.7d | 42.2d 7.4d | 7.5d 91.8% | 98.0% 5.8d | 1.0d 2026-02-11 13:18:22 144.0 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable 104.2 Mbit/s | 8.4 Mbit/s 104.2 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 90.7% | 98% 5.6d | 8d 17735.3d | 454.5d 7.4d | 7.5d 90.7% | 98.0% 5.6d | 9.9d 2026-02-11 13:18:22 128.0 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 104.2 Mbit/s | 816.0 Kbit/s 104.2 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 8.3d | 8d 8.3d | 57.2d 7.4d | 7.5d 100.0% | 98.0% 8.3d | 1.0d 2026-02-11 13:18:22 200.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.