View Relay "zgato"

Family: 1 relay | tor@zgato.ru | AS7489 | Singapore | Linux

Health Status

Consensus
In Consensus (5/9 Directory Auths)
Flags
Fast, Running, Stable, V2Dir, Valid (5)
BW Verified
2/6 BW Auths Measured 20 Kbit/s Median
Stability
Not Overloaded | DOWN 21h 15m 48s ago | UP 99% (1M)
Reachability
IPv4: 5/9 (Directory Auths)
First Seen
1mo 3w 6d ago
BW Weight
0.00% of Network | 20 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 96.0% 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.0% 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.
  • Low bandwidth authority measurements : Only 2/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • StaleDesc flag assigned : Relay descriptor is older than 18 hours
    Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
Notes:
  • Partial IPv4 reachability: 5/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
210.16.120.200:443
Reachability (Directory Authorities)
IPv4
5/9
Location
Country
Singapore Singapore
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS7489
AS Name
HostUS (BGP.tools)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Stable
Eligible Flags (5): Running: 5/9 | Valid: 5/9 | V2Dir: 5/9 | Fast: 5/9 | Stable: 5/9 | HSDir: 0/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) 20.6 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 16.6d (0/9 DA above threshold)
Min/Max: 15.3d / 26.7d (5/9 DA, Voting / Total Eligible)		 ≥22.2d - 53.9d (varies)
[Stricter] moria1: ≥405.2d
Uptime Below 1.5d (R) ≥9.9d - 10.6d (varies)
HSDir Prereq: Stable Meets 5/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 5/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 96.6% (0/9 DA above threshold)
Min/Max: 96.0% / 97.1% (5/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 24.5d (5/9 DA above threshold)
Min/Max: 20.7d / 27.9d (5/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets 5/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Meets 5/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 5/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 96.6% (0/9 DA above threshold)
Min/Max: 96.0% / 97.1% (5/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 24.5d (5/9 DA above threshold)
Min/Max: 20.7d / 27.9d (5/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 20.6 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 13:15:03).

Last fetch was at Thu, 29 Jan 2026 13:15:47 GMT.

Nickname
zgato
Fingerprint
34975072B20FEEB895D920EB8EEED69B4FE8CCF3
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 
34975072B20FEEB895D920EB8EEED69B4FE8CCF3
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
20.60 Mbit/s | 20.60 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | N/A
OR Address
210.16.120.200:443
Exit Address
none
Dir Address
none
Country
Singapore Singapore
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS7489 | HostUS (BGP.tools)
Flags: 5
Fast Fast Running Running Stable Stable V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
—/96.8%/—/—
Uptime (1M/6M/1Y/5Y)
99.9%/99.9%/0.0%/0.0%
Uptime / Downtime
DOWN 21h 15m 48s ago
Seen (First | Last)
1mo 3w 6d ago (2025-12-03 00:00:00) | 21h 17m 16s ago (2026-01-28 16:00:00)
Last Restarted
1d 12h 11m ago (2026-01-28 01:05:47)
Last Changed Address or Port
2025-12-03 00: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 13:15:03).

  • Consensus Status (need ≥5/9): In Consensus — 5/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Running: 5/9 | Valid: 5/9 | V2Dir: 5/9 | Fast: 5/9 | Stable: 5/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 5/9
  • Consensus Weight (Dir. Auth.): Median: 20.6 Kbit/s | Min: 4640 bit/s | Max: 20.6 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 96.0% 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.0% 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.
    • Low bandwidth authority measurements: Only 2/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
      • Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
    • StaleDesc flag assigned: Relay descriptor is older than 18 hours
      • Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
  • Notes:
    • Partial IPv4 reachability: 5/9 authorities can reach this relay

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.) 5/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 5/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 5/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 20.6 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 96.6% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 24.5 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 20.6 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 1.5d ≥9.9d - 10.6d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 17 days ≥22.2d - 53.9d (typical)
[Stricter] moria1: ≥405.2d 		BELOW - 0/9
Fast Speed (Relay Reported) 20.6 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.6% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 24.5 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.8d 		BELOW - 0/9

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 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) No — Y No — — — — — — — — — — —
dannenberg (DE) Yes Yes N Yes Valid, V2Dir, Fast, Stable, StaleDesc 20.6 Mbit/s | 816.0 Kbit/s 20.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.0% | 98% 20.7d | 8d 15.9d | 22.2d 1.5d | 10.7d 96.0% | 98.0% 20.7d | 1.0d 2026-01-28 14:17:51 [Stale] 20.6 Kbit/s
dizum (NL) Yes Yes N Yes Valid, V2Dir, Fast, Stable, StaleDesc 20.6 Mbit/s | 816.0 Kbit/s 20.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.4% | 98% 23.1d | 8d 15.3d | 34.8d 1.5d | 10.6d 96.4% | 98.0% 23.1d | 1.0d 2026-01-28 14:17:51 [Stale] 20.6 Kbit/s
faravahar (US) Yes Yes N Yes Valid, V2Dir, Fast, Stable, StaleDesc 20.6 Mbit/s | 816.0 Kbit/s 20.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.6% | 98% 24.5d | 8d 16.6d | 47.5d 1.5d | 9.9d 96.6% | 98.0% 24.5d | 1.0d 2026-01-28 14:17:51 [Stale] 20.6 Kbit/s
gabelmoo (DE) No — Y No — — — — — — — — — — —
longclaw (US) No — Y No — — — — — — — — — — —
maatuska (SE) Yes Yes Y Yes Valid, V2Dir, Fast, Stable, StaleDesc 20.6 Mbit/s | 816.0 Kbit/s 20.6 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 96.8% | 98% 25.8d | 8d 24.2d | 55.3d 1.5d | 10.0d 96.8% | 98.0% 25.8d | 1.0d 2026-01-28 14:17:51 [Stale] 4640 bit/s
moria1 (US) No — Y No — — — — — — — — — — —
tor26 (AT) Yes Yes Y Yes Valid, V2Dir, Fast, Stable, StaleDesc 20.6 Mbit/s | 816.0 Kbit/s 20.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 97.1% | 98% 27.9d | 8d 26.7d | 55.8d 1.5d | 11.3d 97.1% | 98.0% 27.9d | 1.0d 2026-01-28 14:17:51 [Stale] 5440 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.