View Relay "relaye02"

Family: 1 relay | stephan@example.invalid | AS141995 | Singapore | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, V2Dir, Valid (3)
BW Verified
5/6 BW Auths Measured 8 bit/s Median
Stability
Not Overloaded | DOWN 12h 15m 49s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
18h 17m 18s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.8.16 Not Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 36.8% 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 0.7 days is below 8 days requirement (7.3 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).
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 36.8% 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.
  • HSDir: Time Known below threshold : Time Known 17.4 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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.

Connectivity and Location

Addresses
OR Address
vmd188496.contaboserver.net
217.217.249.106:9002
[2400:d321:3018:8496::1]:9002
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Singapore Singapore
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS141995
AS Name
Contabo Asia Private Limited (BGP.tools)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 1/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 Below 8 bit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 0.3d (1/9 DA above threshold)
Min/Max: 0.3d / 20482.0d (9/9 DA, Voting / Total Eligible)		 ≥22.2d - 53.9d (varies)
[Stricter] moria1: ≥405.2d
Uptime Below 0.8d (R) ≥9.9d - 10.6d (varies)
HSDir Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Below 0/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 36.8% (0/9 DA above threshold)
Min/Max: 35.9% / 39.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Below Median: 0.7d (0/9 DA above threshold)
Min/Max: 0.7d / 0.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below 0/9 authorities assigned Fast flag ≥5/9 authorities
Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: V2Dir Meets 9/9 authorities assigned V2Dir flag ≥5/9 authorities
WFU Below Median: 36.8% (0/9 DA above threshold)
Min/Max: 35.9% / 39.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Below (need 7.3 more days) Median: 0.7d (0/9 DA above threshold)
Min/Max: 0.7d / 0.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 8 bit/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
relaye02
Fingerprint
46FBC5392FB0164F7360CC38257AE2FF2BC81BCD
AROI (?)
none
Contact
stephan@example.invalid
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
46FBC5392FB0164F7360CC38257AE2FF2BC81BCD
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
0.00 Kbit/s | unknown| 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
vmd188496.contaboserver.net | 217.217.249.106:9002, [2400:d321:3018:8496::1]:9002
Exit Address
none
Dir Address
none
Country
Singapore Singapore
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS141995 | Contabo Asia Private Limited (BGP.tools)
Flags: 3
Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Uptime / Downtime
DOWN 12h 15m 49s ago
Seen (First | Last)
18h 17m 18s ago (2026-01-28 19:00:00) | 12h 17m 18s ago (2026-01-29 01:00:00)
Last Restarted
19h 14m 27s ago (2026-01-28 18:02:51)
Last Changed Address or Port
2026-01-28 19:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.16 on Linux
Version (Running | Recommended | Status)
0.4.8.16 | No | obsolete

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-29 13:15:03).

  • 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: 0/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9 | IPv6: 0/0
  • Consensus Weight (Dir. Auth.): Median: 8 bit/s | Min: 0 bit/s | Max: 8 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 36.8% 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 0.7 days is below 8 days requirement (7.3 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).
    • Guard: requires Fast flag: Guard flag requires having the Fast flag first
      • Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
    • 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 36.8% 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.
    • HSDir: Time Known below threshold: Time Known 17.4 hours below 25 hours (dir-spec default)
      • Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
    • 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.

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.) 8 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 36.8% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 0.7 days ≥8 days (all authorities) BELOW - need 7.3 more days
Guard BW (Relay Reported) 8 bit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.8d ≥9.9d - 10.6d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 0 days ≥22.2d - 53.9d (typical)
[Stricter] moria1: ≥405.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 8 bit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		BELOW - need ≥100 KB/s
HSDir WFU (Dir. Auth., wfu) 36.8% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 0.7 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.8d 		BELOW - 0/9
IPv6 Reachable (Dir. Auth.) 0/0 tested ≥1/0 (majority) NOT TESTED

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 — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 36.8% | 98% 0.7d | 8d 0.3d | 49.8d 0.8d | 11.0d 36.8% | 98.0% 0.7d | 1.0d 2026-01-29 08:19:20 8 bit/s
dannenberg (DE) Yes Yes N Yes — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 39.0% | 98% 0.7d | 8d 0.3d | 22.2d 0.8d | 10.7d 39.0% | 98.0% 0.7d | 1.0d 2026-01-29 08:19:20 —
dizum (NL) Yes Yes N Yes — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 35.9% | 98% 0.7d | 8d 0.3d | 34.8d 0.8d | 10.6d 35.9% | 98.0% 0.7d | 1.0d 2026-01-29 08:19:20 —
faravahar (US) Yes Yes N Yes — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 36.0% | 98% 0.7d | 8d 0.3d | 47.5d 0.8d | 9.9d 36.0% | 98.0% 0.7d | 1.0d 2026-01-29 08:19:20 —
gabelmoo (DE) Yes Yes Y Yes — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 36.7% | 98% 0.7d | 8d 0.3d | 53.9d 0.8d | 10.6d 36.7% | 98.0% 0.7d | 1.0d 2026-01-29 08:19:20 8 bit/s
longclaw (US) Yes Yes Y Yes — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 37.4% | 98% 0.7d | 8d 0.3d | 55.1d 0.8d | 10.0d 37.4% | 98.0% 0.7d | 1.0d 2026-01-29 08:19:20 —
maatuska (SE) Yes Yes Y Yes — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 37.1% | 98% 0.7d | 8d 0.3d | 55.3d 0.8d | 10.0d 37.1% | 98.0% 0.7d | 1.0d 2026-01-29 08:19:20 8 bit/s
moria1 (US) Yes Yes Y Yes — Valid, V2Dir, Stable 0 bit/s | 8.4 Mbit/s 0 bit/s | 240.0 Mbit/s OR 16.0 Mbit/s 37.7% | 98% 0.7d | 8d 20482.0d | 405.2d 0.8d | 10.1d 37.7% | 98.0% 0.7d | 9.8d 2026-01-29 08:19:20 8 bit/s
tor26 (AT) Yes Yes Y Yes — Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 36.5% | 98% 0.7d | 8d 0.3d | 55.8d 0.8d | 11.3d 36.5% | 98.0% 0.7d | 1.0d 2026-01-29 08:19:20 8 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.