View Relay "rofltor05"

Operator: rofl.cat (8 relays) ✓ Validated | Family: 8 relays | email:tor[]rofl.cat... | AS24940 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 80 Kbit/s Median
Stability
Not Overloaded | UP 3h 23m 5s ago | UP 93% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
6y 11mo 2w ago
BW Weight
0.00% of Network | 82 Mbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 95.7% 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: 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 95.7% 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
tor-relay5.rofl.cat
178.63.19.126:9001
[2a00:1908:ffff:fffe:4c60:4fff:fef5:5cec]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS24940
AS Name
Hetzner Online GmbH (BGP.tools)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/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 Meets (≥100 KB/s) 83.0 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 3.7d (1/9 DA above threshold)
Min/Max: 2.5d / 14489.9d (9/9 DA, Voting / Total Eligible)		 ≥22.1d - 53.8d (varies)
[Stricter] moria1: ≥406.0d
Uptime Below 0.1d (R) ≥10.5d - 11.3d (varies)
HSDir Prereq: Stable Below 1/9 authorities assigned Stable flag ≥5/9 authorities
Prereq: Fast Meets 9/9 authorities assigned Fast flag ≥5/9 authorities
WFU Below Median: 95.5% (0/9 DA above threshold)
Min/Max: 94.3% / 95.8% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Meets Median: 12.9d (9/9 DA above threshold)
Min/Max: 10.0d / 14.0d (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 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: 95.5% (0/9 DA above threshold)
Min/Max: 94.3% / 95.8% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Meets Median: 12.9d (9/9 DA above threshold)
Min/Max: 10.0d / 14.0d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 83.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 08:45:07).

Last fetch was at Thu, 29 Jan 2026 09:15:37 GMT.

Nickname
rofltor05
Fingerprint
A7C5B40EC0FB5175E884075DDC87531D353F679C
AROI (?)
rofl.cat
Contact
email:tor[]rofl.cat btc:17bD7EWsSXrqrqk2ibbprPxhegMqecsaCy url:rofl.cat proof:dns-rsa autoupdate:y confmgmt:puppet ciissversion:2
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Members: 8 (View) 
04E3B5925EB5F66C6EC810A3D7702E0CA3F9D5E7
0D2D4B1D27468806BB1EDFB02715EEE91E1AB94E
3CB4193EF4E239FCEDC4DC43468E0B0D6B67ACC3
706A7674A217BA905FE677E82236B7B968A23DB7
8970A3544290D671DCBD9B96C0EDD658E16F7428
90A5D1355C4B5840E950EB61E673863A6AE3ACA1
A7C5B40EC0FB5175E884075DDC87531D353F679C
D76110E770FB5F6D09CB801D6379C33A1A6C0CC3
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
82.96 Mbit/s | 82.96 Mbit/s| 419.43 Mbit/s| 838.86 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.01% | N/A
OR Address
tor-relay5.rofl.cat | 178.63.19.126:9001, [2a00:1908:ffff:fffe:4c60:4fff:fef5:5cec]:9001
Exit Address
none
Dir Address
none
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS24940 | Hetzner Online GmbH (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
—/89.6%/91.4%/—
Uptime (1M/6M/1Y/5Y)
93.3%/89.8%/91.5%/92.4%
Uptime / Downtime
UP 3h 23m 5s ago
Seen (First | Last)
6y 11mo 2w ago (2019-02-18 00:00:00) | 1h 17m 3s ago (2026-01-29 08:00:00)
Last Restarted
3h 24m 30s ago (2026-01-29 05:52:33)
Last Changed Address or Port
2024-05-30 18: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 08: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: 1/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 80.0 Kbit/s | Min: 65.6 Kbit/s | Max: 120.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 95.7% 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: 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 95.7% 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.) 80.0 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 95.5% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 12.9 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 83.0 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-312.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 0.1d ≥10.5d - 11.3d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 4 days ≥22.1d - 53.8d (typical)
[Stricter] moria1: ≥406.0d 		BELOW - 1/9
Fast Speed (Relay Reported) 83.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) 95.5% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 12.9 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 83.0 Mbit/s | 816.0 Kbit/s 83.0 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 95.7% | 98% 13.1d | 8d 3.7d | 50.2d 0.1d | 12.0d 95.7% | 98.0% 13.1d | 1.0d 2026-01-29 05:52:35 65.6 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 83.0 Mbit/s | 816.0 Kbit/s 83.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.2% | 98% 12.6d | 8d 2.9d | 22.1d 0.1d | 11.4d 95.2% | 98.0% 12.6d | 1.0d 2026-01-29 05:52:35 80.0 Kbit/s
dizum (NL) Yes Yes N Yes — Running, Valid, V2Dir, Fast 83.0 Mbit/s | 816.0 Kbit/s 83.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.6% | 98% 13.5d | 8d 3.3d | 34.4d 0.1d | 11.3d 95.6% | 98.0% 13.5d | 1.0d 2026-01-29 05:52:35 80.0 Kbit/s
faravahar (US) Yes Yes N Yes Yes Running, Valid, V2Dir, Fast 83.0 Mbit/s | 816.0 Kbit/s 83.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.4% | 98% 12.7d | 8d 2.5d | 47.2d 0.1d | 10.5d 95.4% | 98.0% 12.7d | 1.0d 2026-01-29 05:52:35 80.0 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 83.0 Mbit/s | 816.0 Kbit/s 83.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 95.5% | 98% 13.0d | 8d 3.7d | 53.8d 0.1d | 11.4d 95.5% | 98.0% 13.0d | 1.0d 2026-01-29 05:52:35 120.0 Kbit/s
longclaw (US) Yes Yes Y Yes — Running, Valid, V2Dir, Fast 83.0 Mbit/s | 816.0 Kbit/s 83.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.6% | 98% 12.7d | 8d 3.8d | 54.5d 0.1d | 10.7d 95.6% | 98.0% 12.7d | 1.0d 2026-01-29 05:52:35 80.0 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 83.0 Mbit/s | 816.0 Kbit/s 83.0 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 95.8% | 98% 14.0d | 8d 4.1d | 54.6d 0.1d | 10.6d 95.8% | 98.0% 14.0d | 1.0d 2026-01-29 05:52:35 112.0 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast, Stable 83.0 Mbit/s | 8.4 Mbit/s 83.0 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 94.3% | 98% 10.0d | 8d 14489.9d | 406.0d 0.1d | 10.8d 94.3% | 98.0% 10.0d | 9.9d 2026-01-29 05:52:35 67.2 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Running, Valid, V2Dir, Fast 83.0 Mbit/s | 816.0 Kbit/s 83.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 95.4% | 98% 12.9d | 8d 3.1d | 55.6d 0.1d | 12.0d 95.4% | 98.0% 12.9d | 1.0d 2026-01-29 05:52:35 79.2 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.