View Relay "bl4ckc4tsec"

Family: 2 relays | @bl4ckc4tsec | AS212655 | United Kingdom of Great Britain and Northern Ireland | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 72 Kbit/s Median
Stability
Not Overloaded | UP 1d 6h 55m ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1w 4d 17m ago
BW Weight
0.00% of Network | 68 Mbit/s Observed By Relay
Version
0.4.8.10 Not Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 95.3% 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.8 days is below 8 days requirement (1.2 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 95.3% 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.
  • Tor version not recommended : Running Tor version 0.4.8.10 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
83.217.161.176:443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS212655
AS Name
YouFibre Limited (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) 68.3 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below Median: 1.0d (1/9 DA above threshold)
Min/Max: 0.7d / 17420.5d (9/9 DA, Voting / Total Eligible)		 ≥22.2d - 53.9d (varies)
[Stricter] moria1: ≥405.2d
Uptime Below 1.3d (R) ≥9.9d - 10.6d (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: 96.5% (2/9 DA above threshold)
Min/Max: 95.3% / 99.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0%
Time Known Below Median: 7.3d (1/9 DA above threshold)
Min/Max: 6.5d / 8.1d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most)
[Stricter] moria1: ≥9.8d
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: 96.5% (2/9 DA above threshold)
Min/Max: 95.3% / 99.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (all authorities)
Time Known Below (need 0.7 more days) Median: 7.3d (1/9 DA above threshold)
Min/Max: 6.5d / 8.1d (9/9 DA, Voting / Total Eligible)		 ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 68.3 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
bl4ckc4tsec
Fingerprint
111BE5F1152016E983945F186064A3B927B2FF0E
AROI (?)
none
Contact
@bl4ckc4tsec
IPv4 Exit Policy Summary 
accept: 
  6660-6667
IPv6 Exit Policy Summary 
none
Exit Policy 
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 83.217.161.176:*
accept *:6660-6667
reject *:*
Effective Family Members: 2 (View) 
111BE5F1152016E983945F186064A3B927B2FF0E
C48903B8297F3E646AF5E0536396252ACA15F759
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
68.32 Mbit/s | 68.32 Mbit/s| 81.92 Mbit/s| 163.84 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | 0.01% | N/A
OR Address
83.217.161.176:443
Exit Address
none
Dir Address
none
Country
United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS212655 | YouFibre Limited (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 1d 6h 55m ago
Seen (First | Last)
1w 4d 17m ago (2026-01-18 13:00:00) | 1h 17m 11s ago (2026-01-29 12:00:00)
Last Restarted
1d 6h 56m ago (2026-01-28 06:20:16)
Last Changed Address or Port
2026-01-18 13:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.10 on Linux
Version (Running | Recommended | Status)
0.4.8.10 | 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: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9
  • Reachability: IPv4: 9/9
  • Consensus Weight (Dir. Auth.): Median: 72.8 Kbit/s | Min: 68.3 Kbit/s | Max: 88.0 Kbit/s
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 95.3% 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.8 days is below 8 days requirement (1.2 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 95.3% 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.
    • Tor version not recommended: Running Tor version 0.4.8.10 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.) 72.8 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 96.5% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 7.3 days ≥8 days (all authorities) BELOW - need 0.7 more days
Guard BW (Relay Reported) 68.3 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.3d ≥9.9d - 10.6d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 1 days ≥22.2d - 53.9d (typical)
[Stricter] moria1: ≥405.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 68.3 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.5% ≥98.0% (from all auths) BELOW - 0/9
HSDir TK (Dir. Auth., tk) 7.3 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) Yes Yes Y Yes Running, Valid, V2Dir, Fast 68.3 Mbit/s | 816.0 Kbit/s 68.3 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 95.3% | 98% 6.8d | 8d 1.0d | 49.8d 1.3d | 11.0d 95.3% | 98.0% 6.8d | 1.0d 2026-01-29 00:40:21 72.8 Kbit/s
dannenberg (DE) Yes Yes N Yes Running, Valid, V2Dir, Fast 68.3 Mbit/s | 816.0 Kbit/s 68.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.5% | 98% 7.3d | 8d 0.7d | 22.2d 1.3d | 10.7d 95.5% | 98.0% 7.3d | 1.0d 2026-01-29 00:40:21 68.3 Kbit/s
dizum (NL) Yes Yes N Yes Running, Valid, V2Dir, Fast 68.3 Mbit/s | 816.0 Kbit/s 68.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.2% | 98% 7.2d | 8d 0.8d | 34.8d 1.3d | 10.6d 96.2% | 98.0% 7.2d | 1.0d 2026-01-29 00:40:21 68.3 Kbit/s
faravahar (US) Yes Yes N Yes Running, Valid, V2Dir, Fast 68.3 Mbit/s | 816.0 Kbit/s 68.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.5% | 98% 7.3d | 8d 0.7d | 47.5d 1.3d | 9.9d 95.5% | 98.0% 7.3d | 1.0d 2026-01-29 00:40:21 68.3 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Running, Valid, V2Dir, Fast 68.3 Mbit/s | 816.0 Kbit/s 68.3 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 8.1d | 8d 2.3d | 53.9d 1.3d | 10.6d 99.0% | 98.0% 8.1d | 1.0d 2026-01-29 00:40:21 88.0 Kbit/s
longclaw (US) Yes Yes Y Yes Running, Valid, V2Dir, Fast 68.3 Mbit/s | 816.0 Kbit/s 68.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.1% | 98% 7.4d | 8d 1.4d | 55.1d 1.3d | 10.0d 98.1% | 98.0% 7.4d | 1.0d 2026-01-29 00:40:21 68.3 Kbit/s
maatuska (SE) Yes Yes Y Yes Running, Valid, V2Dir, Fast 68.3 Mbit/s | 816.0 Kbit/s 68.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 96.5% | 98% 7.1d | 8d 0.9d | 55.3d 1.3d | 10.0d 96.5% | 98.0% 7.1d | 1.0d 2026-01-29 00:40:21 88.0 Kbit/s
moria1 (US) Yes Yes Y Yes Running, Valid, V2Dir, Fast, Stable 68.3 Mbit/s | 8.4 Mbit/s 68.3 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 96.8% | 98% 6.5d | 8d 17420.5d | 405.2d 1.3d | 10.1d 96.8% | 98.0% 6.5d | 9.8d 2026-01-29 00:40:21 80.0 Kbit/s
tor26 (AT) Yes Yes Y Yes Running, Valid, V2Dir, Fast 68.3 Mbit/s | 816.0 Kbit/s 68.3 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 97.1% | 98% 7.6d | 8d 1.1d | 55.8d 1.3d | 11.3d 97.1% | 98.0% 7.6d | 1.0d 2026-01-29 00:40:21 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.