View Relay "CGretski"

Fingerprint: 7ABA776A496C7B1D0C40F25ACA59F2EA60C3D429 | Operator: cellarnet.co.uk v2 (1 relay) ⚠ Misconfigured | Family: 1 relay | email:cgretski[]hotmail.com... | AS13037 | United Kingdom of Great Britain and Northern Ireland | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
0/6 BW Auths Measured 584 bit/s Median
Stability
Not Overloaded | UP 2h 3m 55s ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.00% of Network | 589 Kbit/s Observed By Relay
Version
0.4.9.6 Recommended
Issues Detected:
  • 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.
  • 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: bandwidth below threshold : Observed bandwidth 590 Kbit/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.
  • Guard: WFU below threshold : Weighted Fractional Uptime 2.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.
  • 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: requires Fast flag : HSDir 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.
  • HSDir: requires Stable flag : HSDir 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). Avoid restarts.
  • HSDir: WFU below threshold : WFU 2.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.
  • Low bandwidth authority measurements : Only 0/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • BadExit flag assigned : This relay has been flagged as a bad exit by directory authorities. BadExit means authorities detected malicious behavior (traffic modification, SSL stripping, etc.).
    Suggestion: Contact bad-relays@lists.torproject.org to understand and resolve this issue.

Addresses
OR Address
tor-exit.cellarnet.co.uk
82.71.108.163:21
[2a02:8010:677e:f9d0:215:5dff:fe01:210c]:21
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
United Kingdom of Great Britain and Northern Ireland United Kingdom of Great Britain and Northern Ireland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS13037
AS Name
Zen Internet Ltd (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Current Flags (5): Running, Valid, V2Dir, Exit, BadExit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (9/9 DA) 9/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Below (0/9 DA) 589.8 Kbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 0.8d (1/9 DA above threshold)
Min/Max: 0.7d / 1523.6d (9/9 DA, Voting / Total Eligible)
≥10.2d - 15.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥5983.4d
Uptime Below (0/9 DA) 0.1d (R) ≥9.5d - 9.9d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥10.2d - 15.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥5983.4d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 2.7% (0/9 DA above threshold)
Min/Max: 2.5% / 8.5% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 31.6d (9/9 DA above threshold)
Min/Max: 9.8d / 32.0d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥10.2d - 15.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥5983.4d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 2.7% (0/9 DA above threshold)
Min/Max: 2.5% / 8.5% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 31.6d (9/9 DA above threshold)
Min/Max: 9.8d / 32.0d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 589.8 Kbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
BadExit Restriction (by DA) Flagged (5/9 DA) 5/9 authorities assigned BadExit Exit traffic manipulation, SSL stripping, or policy violation

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-08-29 05:15:10).

Capacity (Relay Reported)
Observed Bandwidth
589.82 Kbit/s
Advertised Bandwidth
589.82 Kbit/s
Rate Limit
2.10 Mbit/s
Burst Limit
3.15 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-29 05:15:10

Measured By
0/6 Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26
Median Measurement
584 bit/s
Min / Max
584 bit/s / 584 bit/s
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0000% (3th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 2h 3m 55s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
1h 16m ago (2026-08-29 04:00:00)
Last Seen
1h 16m ago (2026-08-29 04:00:00)
Last Restarted
2h 3m 55s ago (2026-08-29 03:12:05)
Last Changed Address
2026-08-29 04:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-08-28 22:00 UTC

AROI Domain (?)
cellarnet.co.uk
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: Not yet processed by validator (relay may be new)
Contact
email:cgretski[]hotmail.com url:https://cellarnet.co.uk proof:uri-rsa pgp:7CD532DF0E045797CC3EDC37F84FDEC04669EE18 ciissversion:2
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
7ABA776A496C7B1D0C40F25ACA59F2EA60C3D429 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.6 on Linux
Version
0.4.9.6Recommended
Version Status
Recommended

DNS Health
Status
Not Tested
IPv4 Exit Policy Summary
accept: 
  20-22
  80-81
  110-119
  143
  443-444
  563
  873
  989-995
  3690
  4242
  5000-5999
  6463-6472
  8000-8100
  9418
  11371
IPv6 Exit Policy Summary
accept: 
  20-22
  80-81
  110-119
  143
  443-444
  563
  873
  989-995
  3690
  4242
  5000-5999
  6463-6472
  8000-8100
  9418
  11371
Full 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 82.71.108.163:*
reject 91.19.0.0/15:*
reject 87.255.51.229:*
reject 82.165.47.44:*
reject 85.159.128.0/24:*
reject 84.163.0.0/16:*
accept *:20-22
accept *:80-81
accept *:110-119
accept *:143
accept *:443-444
accept *:563
accept *:873
accept *:989-995
accept *:3690
accept *:4242
accept *:5000-5999
accept *:6463-6472
accept *:8000-8100
accept *:9418
accept *:11371
reject *:*

Last fetch was at Sat, 29 Aug 2026 05:15:58 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-08-29 05:15:10).

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority Running Valid Exit MiddleOnly 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 Yes N Yes Yes Running, Valid, V2Dir, Exit 589.8 Kbit/s | 816.0 Kbit/s 589.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 2.7% | 98% 31.7d | 8d 0.8d | 14.0d 0.1d | 9.5d 2.7% | 98.0% 31.7d | 1.0d 2026-08-29 03:12:07 584 bit/s
dannenberg (DE) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Exit 589.8 Kbit/s | 816.0 Kbit/s 589.8 Kbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 2.6% | 98% 31.7d | 8d 0.8d | 15.9d 0.1d | 11.3d 2.6% | 98.0% 31.7d | 1.0d 2026-08-29 03:12:07 584 bit/s
dizum (NL) Yes Yes Yes N Yes Yes Running, Valid, V2Dir, Exit 589.8 Kbit/s | 816.0 Kbit/s 589.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 2.7% | 98% 31.5d | 8d 0.8d | 15.2d 0.1d | 9.9d 2.7% | 98.0% 31.5d | 1.0d 2026-08-29 03:12:07 584 bit/s
faravahar (US) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Exit, BadExit 589.8 Kbit/s | 816.0 Kbit/s 589.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 2.5% | 98% 31.6d | 8d 0.7d | 15.1d 0.1d | 9.9d 2.5% | 98.0% 31.6d | 1.0d 2026-08-29 03:12:07 584 bit/s
gabelmoo (DE) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Exit, BadExit 589.8 Kbit/s | 816.0 Kbit/s 589.8 Kbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 3.1% | 98% 31.8d | 8d 0.9d | 15.5d 0.1d | 9.9d 3.1% | 98.0% 31.8d | 1.0d 2026-08-29 03:12:07 584 bit/s
longclaw (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Exit, BadExit 589.8 Kbit/s | 816.0 Kbit/s 589.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 8.5% | 98% 32.0d | 8d 2.6d | 18.4d 0.1d | 9.9d 8.5% | 98.0% 32.0d | 1.0d 2026-08-29 03:12:07 584 bit/s
maatuska (SE) Yes Yes Yes N Yes Yes Running, Valid, V2Dir, Exit 589.8 Kbit/s | 816.0 Kbit/s 589.8 Kbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 2.7% | 98% 31.5d | 8d 0.8d | 10.2d 0.1d | 9.9d 2.7% | 98.0% 31.5d | 1.0d 2026-08-29 03:12:07 584 bit/s
moria1 (US) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Stable, Exit, BadExit 589.8 Kbit/s | 8.4 Mbit/s 589.8 Kbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 4.3% | 98% 9.8d | 8d 1523.6d | 5983.4d 0.1d | 9.9d 4.3% | 98.0% 9.82d | 9.84d 2026-08-29 03:12:07 584 bit/s
tor26 (AT) Yes Yes Yes Y Yes Yes Running, Valid, V2Dir, Exit, BadExit 589.8 Kbit/s | 816.0 Kbit/s 589.8 Kbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 2.8% | 98% 30.1d | 8d 0.8d | 16.6d 0.1d | 9.8d 2.8% | 98.0% 30.1d | 1.0d 2026-08-29 03:12:07 584 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). Self-reported uptime from 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.