View Relay "cozybeardev"

Operator: shadowbrokers.eu (35 relays) ✓ Validated | Family: 35 relays | email:tor[]shadowbrokers.eu... | AS43317 | Russian Federation | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, V2Dir, Valid (4)
BW Verified
5/6 BW Auths Measured 74 Kbit/s Median
Stability
Not Overloaded | UP 1mo 3w 1d ago | UP 70% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
2y 7mo 4w ago
BW Weight
0.01% of Network | 74 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: WFU below threshold : Weighted Fractional Uptime 45.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 45.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.node18.shadowbrokers.eu
77.73.70.167:443
[2a00:1838:37:468::98b4]:443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Russian Federation Russian Federation
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS43317
AS Name
SIA VEESP (BGP.tools)

Flags and Eligibility

Current Flags (4): Fast, Running, V2Dir, Valid
Eligible Flags (4): Guard: 2/9 | Stable: 2/9 | Fast: 9/9 | HSDir: 2/9 | Running: 9/9 | V2Dir: 9/9 | Valid: 9/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Guard WFU Below 45.7% (DA) ≥98% (all authorities)
Time Known Meets 10.8 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 74.4 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 11 days (DA) ≥26.6d - 45.4d (varies)
Uptime Meets 52.5d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 74.4 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 45.7% (DA) ≥98.0%
Time Known Meets 10.8 days (DA) ≥1.0d (most) / 9.9d (max)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname
cozybeardev
Fingerprint
A3BC09219C2351376412D8736C7CAEE4A1639E3B
AROI (?)
shadowbrokers.eu
Contact
email:tor[]shadowbrokers.eu url:shadowbrokers.eu proof:dns-rsa btc:bc1qu9m2sy836pmyku0t3vnmpjxfjds8p2x5psyl6y ciissversion:2
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Members: 35 (View) 
016E12F1491EC71E2A1ABCBC4D450ACE0EA95E30
05C6FC1D969C096BB9655A34841B536898FD3D47
08BF9160082730C2440740571DBCEE0588B1B6E3
095855F752804827F3711261EE161789A60F43A9
0E3D7FC3C5601598723C0115B0410B3456870C10
1B13F5289BFC399FAE79F649F2C15DD30893B800
26E53DC2770535B785D20742C50A7458F8804758
28E0CEB505976BC045C19B28DC1430AB60282281
2F5F734609D350E0B13BD9CF7E46F9AC019B1186
31DEA0877BE529EF6716ECD22527A63B156C34E8
3D6F3CD0C8FAEF33655AA4D83F8BF1656723C991
56BC59E22C108EE2E3BC5E5712DB765CE0C975A4
62EE5ABE8986474E73B46DAABAC363944152A6D6
6D264FD6D54EAC6C5F22C99C4E27312FEF18AC64
7CF3BFD0DE5AD3772CB9D293BF9251813296924C
8054ABFDEF9E0FA479CD2BB749CFFE1026A7E30D
847B8B7C2A860225D5B1DBA01E4DB3CF1EFD7B20
91730B4425F986B7DC6E3CC72C78EAE85AFB438D
A1FC7772C7F27FE4ABC13B86AE50A46B0C283572
A3BC09219C2351376412D8736C7CAEE4A1639E3B
A4A98B4E4EBBAADE5C8226D041555E82B59342F3
A6A22343CA46D25B5F97A9E04324B7758FF10A98
AA5C46F66CB5863FA379F18081F9BEDC130AD601
AC7BDB39F81C4B364EA50B12B51C77C7A131EA7C
B089974A4D16FD9A283DCE67EF475BB0A2B2567A
B722DBEB2BDFB1F6167FBC9A8C87A4F73F39A78D
B7A6CE93A01F82E1866D451AF88D727E05E29388
BC896CC0A734F8B428B4190C6C32F045A1C88A4F
BCCB37B24EB188588569FB21C7F033812C7A3423
BD7872E0D3BA1E2DEA47F7E2394796863A1EFA85
C6A5595E659FAB33AEC04A94E9A741F1541B4296
D04FE78152A06AEAF950A2E58A11E9739B291C0A
DC4CC08CEEE04E8AC3302D2D0CFD9D7932BD8214
E0F96AFFCA58DEAE00FA28E82E013F9F5632B069
EB287818809452D230F1ED26A4EFDD7F1038105F
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
74.41 Mbit/s | 74.41 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.01% | N/A | 0.02% | N/A
OR Address
tor.node18.shadowbrokers.eu | 77.73.70.167:443, [2a00:1838:37:468::98b4]:443
Exit Address
none
Dir Address
none
Country
Russian Federation Russian Federation
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS43317 | SIA VEESP (BGP.tools)
Flags: 4
Fast Fast Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (70.5%/92.2%/96.1%/97.8%)
Uptime (1M/6M/1Y/5Y)
70.5%/92.2%/96.1%/97.8%
Uptime / Downtime
UP 1mo 3w 1d ago
Seen (First | Last)
2y 7mo 4w ago (2023-05-18 00:00:00) | 1h 54m 51s ago (2026-01-10 03:00:00)
Last Restarted
1mo 3w 1d ago (2025-11-18 17:18:21)
Last Changed Address or Port
2024-01-29 19: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-10 04:46:16).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Guard: 2/9 | Stable: 2/9 | Fast: 9/9 | HSDir: 2/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 74.4 Kbit/s | Min: 64.8 Kbit/s | Max: 160.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: WFU below threshold: Weighted Fractional Uptime 45.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 45.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.) 74.4 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 45.7% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 10.8 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 74.4 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 52.5d ≥19.1d - 19.7d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 11 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 2/9
Fast Speed (Relay Reported) 74.4 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) 45.7% ≥98.0% (from all auths) BELOW - 2/9
HSDir TK (Dir. Auth., tk) 10.8 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 2/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 Fast, V2Dir, Valid 74.4 Mbit/s | 816.0 Kbit/s 74.4 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 45.7% | 98% 10.8d | 8d 0.1d | 47.0d 52.5d | 19.7d 45.7% | 98.0% 10.8d | 1.0d 2026-01-09 21:22:53 80.0 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Fast, V2Dir, Valid 74.4 Mbit/s | 816.0 Kbit/s 74.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 22.9% | 98% 10.4d | 8d 0.0d | 35.7d 52.5d | 20.2d 22.9% | 98.0% 10.4d | 1.0d 2026-01-09 21:22:53 74.4 Kbit/s
dizum (NL) Yes Yes N Yes — Fast, V2Dir, Valid 74.4 Mbit/s | 816.0 Kbit/s 74.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 34.0% | 98% 10.2d | 8d 0.1d | 26.6d 52.5d | 20.4d 34.0% | 98.0% 10.2d | 1.0d 2026-01-09 21:22:53 74.4 Kbit/s
faravahar (US) Yes Yes N Yes Yes Fast, Running, V2Dir, Valid 74.4 Mbit/s | 816.0 Kbit/s 74.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 53.2% | 98% 10.9d | 8d 0.1d | 41.9d 52.5d | 19.1d 53.2% | 98.0% 10.9d | 1.0d 2026-01-09 21:22:53 74.4 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Fast, V2Dir, Valid 74.4 Mbit/s | 816.0 Kbit/s 74.4 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 56.3% | 98% 12.3d | 8d 0.1d | 45.4d 52.5d | 19.6d 56.3% | 98.0% 12.3d | 1.0d 2026-01-09 21:22:53 104.0 Kbit/s
longclaw (US) Yes Yes Y Yes — Fast, Running, V2Dir, Valid 74.4 Mbit/s | 816.0 Kbit/s 74.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 54.5% | 98% 11.9d | 8d 0.1d | 48.7d 52.5d | 19.5d 54.5% | 98.0% 11.9d | 1.0d 2026-01-09 21:22:53 74.4 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Fast, Guard, HSDir, Running, Stable, V2Dir, Valid 74.4 Mbit/s | 816.0 Kbit/s 74.4 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 31.9d | 8d 30.4d | 42.3d 52.5d | 19.4d 100.0% | 98.0% 31.9d | 1.0d 2026-01-09 21:22:53 160.0 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Fast, Running, Stable, V2Dir, Valid 74.4 Mbit/s | 8.4 Mbit/s 74.4 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 47.9% | 98% 9.8d | 8d 20140.3d | 376.2d 52.5d | 20.4d 47.9% | 98.0% 9.8d | 9.9d 2026-01-09 21:22:53 64.8 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Fast, Guard, HSDir, Running, Stable, V2Dir, Valid 74.4 Mbit/s | 816.0 Kbit/s 74.4 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 267.4d | 8d 267.4d | 51.8d 52.5d | 19.7d 100.0% | 98.0% 267.4d | 1.0d 2026-01-09 21:22:53 88.0 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.