View Relay "CGretski"

Fingerprint: 7ABA776A496C7B1D0C40F25ACA59F2EA60C3D429 | Operator: cellarnet.co.uk v2 (1 relay) ✓ Validated | 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
5/7 BW Auths Measured 232 Kbit/s Median
Stability
Not Overloaded | UP 3w 2d 10h ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.00% of Network | 2 Mbit/s Observed By Relay
Version
0.4.9.12 Recommended
Issues Detected:
  • Not getting the Fast flag : Only 3/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 216.0 Kbit/s – 688.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). faravahar judged it by bandwidth not shown in the votes. Its consensus weight, the median of the 5 bandwidth-scanner measurements, is 232.0 Kbit/s.
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • Guard: bandwidth below threshold : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 288.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 216.0 Kbit/s – 688.0 Kbit/s. dizum, longclaw and maatuska used the relay-reported 2.1 Mbit/s.
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • HSDir: requires Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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.
  • 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, 5 operators)

Current Flags (6): Running, Valid, V2Dir, Stable, Exit, BadExit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 8/9 | HSDir: 3/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 (3/9 DA) 216.0 Kbit/s – 688.0 Kbit/s (5 DA measured)
2.1 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (7/9 DA) Median: 21.5d (8/9 DA above threshold)
Min/Max: 4.7d / 4242.0d (9/9 DA, Voting / Total Eligible)
≥5.4d - 10.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9590.6d
Uptime Meets (9/9 DA) 23.4d (R) ≥3.9d - 4.0d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast
216.0 Kbit/s – 688.0 Kbit/s (5 DA measured)
2.1 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (8/9 DA) 8/9 DA assigned Stable ≥5.4d - 10.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9590.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Median: 98.7% (9/9 DA above threshold)
Min/Max: 98.6% / 98.9% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 25.0d (9/9 DA above threshold)
Min/Max: 9.9d / 25.7d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥10.0d
Guard Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast
216.0 Kbit/s – 688.0 Kbit/s (5 DA measured)
2.1 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (8/9 DA) 8/9 DA assigned Stable ≥5.4d - 10.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9590.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Median: 98.7% (9/9 DA above threshold)
Min/Max: 98.6% / 98.9% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 25.0d (9/9 DA above threshold)
Min/Max: 9.9d / 25.7d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 216.0 Kbit/s – 688.0 Kbit/s (5 DA measured)
2.1 Mbit/s (3 DA relay-reported)
faravahar: not published
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-288.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-10-13 08:45:07).

Capacity (Relay Reported)
Observed Bandwidth
2.15 Mbit/s
Advertised Bandwidth
2.10 Mbit/s
Rate Limit
2.10 Mbit/s
Burst Limit
3.15 Mbit/s
Total Data
597 GB (6 months)
1mo: 122 GB | 6mo: 597 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-13 08:45:07

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
232.0 Kbit/s (median of 5 measurements)
Measured Min / Max
216.0 Kbit/s / 688.0 Kbit/s
Deviation
472.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0000% (3th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime Metrics
Current Status
UP 3w 2d 10h ago
Overall Uptime (1M/6M/1Y/5Y)
99.4%/99.6%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.4%/99.6%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1mo 2w 1d ago (2026-08-29 04:00:00)
Last Seen
1h 45m 28s ago (2026-10-13 07:00:00)
Last Restarted
3w 2d 10h ago (2026-09-19 22:21:27)
Last Changed Address
2026-08-29 04:00:00
Overload Status: Not Overloaded — No overload conditions reported.
History
Uptime, last 6 months Uptime, last 30 days
1M 6M

Operator Identity

Source: AROI Validation API — 2026-10-13 00:00 UTC

AROI Domain (?)
cellarnet.co.uk
Operator Validation
Validated (1/1 relays)
This Relay
Validated (uri-rsa)
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.12 on Linux
Version
0.4.9.12 — Recommended
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 Tue, 13 Oct 2026 08:45:27 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-13 08:45:07).

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 (BW|T) Guard BW (BW|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 — Y Yes Yes Running, Valid, V2Dir, Stable, Exit 688.0 Kbit/s (M) | 816.0 Kbit/s 688.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 98.7% | 98% 25.0d | 8d 21.1d | 10.4d 23.4d | 4.1d 98.7% | 98.0% 25.0d | 1.0d 2026-10-12 14:22:00 688.0 Kbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 232.0 Kbit/s (M) | 816.0 Kbit/s 232.0 Kbit/s (M) | 288.0 Mbit/s OR 16.8 Mbit/s 98.6% | 98% 25.0d | 8d 4.7d | 5.4d 23.4d | 4.0d 98.6% | 98.0% 25.0d | 1.0d 2026-10-12 14:22:00 232.0 Kbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 2.1 Mbit/s (R) | 816.0 Kbit/s 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.7% | 98% 24.7d | 8d 19.8d | 10.6d 23.4d | 4.0d 98.7% | 98.0% 24.7d | 1.0d 2026-10-12 14:22:00 2.1 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Stable, Exit, BadExit not published | 816.0 Kbit/s not published | 280.0 Mbit/s OR 16.8 Mbit/s 98.7% | 98% 25.2d | 8d 21.5d | 11.4d 23.4d | 4.0d 98.7% | 98.0% 25.2d | 1.0d 2026-10-12 14:22:00 2.1 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Stable, Exit, BadExit 216.0 Kbit/s (M) | 816.0 Kbit/s 216.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 98.7% | 98% 25.2d | 8d 21.5d | 10.4d 23.4d | 4.0d 98.7% | 98.0% 25.2d | 1.0d 2026-10-12 14:22:00 216.0 Kbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Fast, Stable, HSDir, Exit, BadExit 2.1 Mbit/s (R) | 816.0 Kbit/s 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.8% | 98% 25.7d | 8d 21.5d | 10.9d 23.4d | 4.0d 98.8% | 98.0% 25.7d | 1.0d 2026-10-12 14:22:00 2.1 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 2.1 Mbit/s (R) | 816.0 Kbit/s 2.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.7% | 98% 25.0d | 8d 21.7d | 10.3d 23.4d | 4.0d 98.7% | 98.0% 25.0d | 1.0d 2026-10-12 14:22:00 2.1 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Stable, Exit, BadExit 600.0 Kbit/s (M) | 8.4 Mbit/s 600.0 Kbit/s (M) | 208.0 Mbit/s OR 16.8 Mbit/s 98.9% | 98% 9.9d | 8d 4242.0d | 9590.6d 23.4d | 3.9d 98.9% | 98.0% 9.9d | 10.0d 2026-10-12 14:22:00 600.0 Kbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Stable, Exit, BadExit 224.0 Kbit/s (M) | 816.0 Kbit/s 224.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 98.8% | 98% 25.0d | 8d 22.0d | 10.6d 23.4d | 4.0d 98.8% | 98.0% 25.0d | 1.0d 2026-10-12 14:22:00 224.0 Kbit/s (M)

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.