View Relay "tormiddleRvaultcc"

Family: 1 relay | tor@staff.rvault.cc | AS202053 | Singapore | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, Stable, V2Dir, Valid (5)
BW Verified
5/6 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | UP 16h 31m 19s ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
7mo 1w 4d ago
BW Weight
0.00% of Network | 15 Mbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 2.0 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • 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
213-163-196-82.sg-sin1.upcloud.host
213.163.196.82:443
[2a04:3543:1000:2310:6c6c:c2ff:fe58:62b1]:443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Singapore Singapore
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS202053
AS Name
UpCloud Ltd (BGP.tools)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Stable
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/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) 16.0 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 6.4d (1/9 DA above threshold)
Min/Max: 2.9d / 13549.6d (9/9 DA, Voting / Total Eligible)		 ≥22.1d - 54.1d (varies)
[Stricter] moria1: ≥406.1d
Uptime Below 0.7d (R) ≥9.2d - 9.8d (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 Meets Median: 99.6% (9/9 DA above threshold)
Min/Max: 98.7% / 99.8% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 13.8d (9/9 DA above threshold)
Min/Max: 9.8d / 18.9d (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 Meets Median: 99.6% (9/9 DA above threshold)
Min/Max: 98.7% / 99.8% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 13.8d (9/9 DA above threshold)
Min/Max: 9.8d / 18.9d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Below 16.0 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 17:45:07).

Last fetch was at Thu, 29 Jan 2026 17:46:08 GMT.

Nickname
tormiddleRvaultcc
Fingerprint
B5C8F3A6E5DDE3DAAA63EAF160C87808088C7EE0
AROI (?)
none
Contact
tor@staff.rvault.cc
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
B5C8F3A6E5DDE3DAAA63EAF160C87808088C7EE0
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
15.99 Mbit/s | 15.99 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.00% | N/A
OR Address
213-163-196-82.sg-sin1.upcloud.host | 213.163.196.82:443, [2a04:3543:1000:2310:6c6c:c2ff:fe58:62b1]:443
Exit Address
none
Dir Address
none
Country
Singapore Singapore
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS202053 | UpCloud Ltd (BGP.tools)
Flags: 5
Fast Fast Running Running Stable Stable V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
—/—/98.9%/—
Uptime (1M/6M/1Y/5Y)
99.9%/99.9%/99.9%/0.0%
Uptime / Downtime
UP 16h 31m 19s ago
Seen (First | Last)
7mo 1w 4d ago (2025-06-22 10:00:00) | 1h 47m 39s ago (2026-01-29 16:00:00)
Last Restarted
16h 32m 50s ago (2026-01-29 01:14:49)
Last Changed Address or Port
2025-06-22 10: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-01-29 17: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: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 8.8 Kbit/s | Min: 3040 bit/s | Max: 16.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 2.0 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
      • Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
    • 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.) 8.8 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 99.6% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 13.8 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 16.0 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.7d ≥9.2d - 9.8d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 6 days ≥22.1d - 54.1d (typical)
[Stricter] moria1: ≥406.1d 		BELOW - 1/9
Fast Speed (Relay Reported) 16.0 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) 99.6% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 13.8 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 Running, Valid, V2Dir, Fast 16.0 Mbit/s | 816.0 Kbit/s 16.0 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 99.4% | 98% 13.4d | 8d 4.5d | 49.9d 0.7d | 10.2d 99.4% | 98.0% 13.4d | 1.0d 2026-01-29 11:24:53 8.0 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 16.0 Mbit/s | 816.0 Kbit/s 16.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 13.4d | 8d 2.9d | 22.1d 0.7d | 9.8d 98.7% | 98.0% 13.4d | 1.0d 2026-01-29 11:24:53 16.0 Kbit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast, Stable 16.0 Mbit/s | 816.0 Kbit/s 16.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.7% | 98% 18.9d | 8d 9.2d | 34.3d 0.7d | 10.0d 99.7% | 98.0% 18.9d | 1.0d 2026-01-29 11:24:53 16.0 Kbit/s
faravahar (US) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 16.0 Mbit/s | 816.0 Kbit/s 16.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.4% | 98% 13.7d | 8d 3.9d | 47.1d 0.7d | 9.2d 99.4% | 98.0% 13.7d | 1.0d 2026-01-29 11:24:53 16.0 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable 16.0 Mbit/s | 816.0 Kbit/s 16.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.8% | 98% 16.4d | 8d 9.4d | 54.1d 0.7d | 10.0d 99.8% | 98.0% 16.4d | 1.0d 2026-01-29 11:24:53 3680 bit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast, Stable 16.0 Mbit/s | 816.0 Kbit/s 16.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.8% | 98% 15.2d | 8d 8.6d | 54.5d 0.7d | 9.3d 99.8% | 98.0% 15.2d | 1.0d 2026-01-29 11:24:53 16.0 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 16.0 Mbit/s | 816.0 Kbit/s 16.0 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 13.8d | 8d 4.8d | 54.9d 0.7d | 9.3d 99.6% | 98.0% 13.8d | 1.0d 2026-01-29 11:24:53 3040 bit/s
moria1 (US) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable 16.0 Mbit/s | 8.4 Mbit/s 16.0 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 99.3% | 98% 9.8d | 8d 13549.6d | 406.1d 0.7d | 9.8d 99.3% | 98.0% 9.8d | 9.9d 2026-01-29 11:24:53 8.8 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable 16.0 Mbit/s | 816.0 Kbit/s 16.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 14.1d | 8d 6.4d | 56.0d 0.7d | 10.3d 99.6% | 98.0% 14.1d | 1.0d 2026-01-29 11:24:53 3760 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.