View Relay "hands"

Fingerprint: 261FC1359C92D19875CED3BC9CDFB83006CBFB87 | Family: 1 relay | 4096R/0125D5C0 Philip Hands... | AS20860 | United Kingdom of Great Britain and Northern Ireland | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (15.2s, 51st percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 656 Kbit/s Median
Stability
Not Overloaded | UP 1mo 1w 3d ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.00% of Network | 4 Mbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • 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 – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 496.0 Kbit/s – 2.1 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 4.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.
  • 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.
  • Tor version not recommended : Running Tor version 0.4.9.11 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.

Addresses
OR Address
tor-exit-readme.hands.com
109.169.33.163:443
Exit Address
109.169.33.163
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
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
AS20860
AS Name
IOMART CLOUD SERVICES LIMITED (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.54% consensus weight, 6 operators)

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Exit
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 9/9 | HSDir: 5/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
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 Partial (5/9 DA) 496.0 Kbit/s – 2.1 Mbit/s (5 DA measured)
4.1 Mbit/s (4 DA relay-reported)
≥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 (8/9 DA) Median: 71.3d (9/9 DA above threshold)
Min/Max: 9.7d / 93.5d (9/9 DA, Voting / Total Eligible)
≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7621.1d
Uptime Meets (9/9 DA) 40.4d (R) ≥5.2d - 5.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast
496.0 Kbit/s – 2.1 Mbit/s (5 DA measured)
4.1 Mbit/s (4 DA relay-reported)
≥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 (9/9 DA) 9/9 DA assigned Stable ≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7621.1d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Meets (9/9 DA) 40.4d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard Prereq: Fast Meets (5/9 DA) 5/9 DA assigned Fast
496.0 Kbit/s – 2.1 Mbit/s (5 DA measured)
4.1 Mbit/s (4 DA relay-reported)
≥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 (9/9 DA) 9/9 DA assigned Stable ≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7621.1d
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: 100.0% (9/9 DA above threshold)
Min/Max: 99.3% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.87300000000001% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 37.0d (9/9 DA above threshold)
Min/Max: 9.9d / 71.5d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 496.0 Kbit/s – 2.1 Mbit/s (5 DA measured)
4.1 Mbit/s (4 DA relay-reported)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-04 18:45:05).

Capacity (Relay Reported)
Observed Bandwidth
4.10 Mbit/s
Advertised Bandwidth
4.10 Mbit/s
Rate Limit
4.19 Mbit/s
Burst Limit
5.03 Mbit/s
Total Data
24 TB (5 years)
1mo: 1.3 TB | 6mo: 5.7 TB | 1y: 8.3 TB | 5y: 24 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 18:45:05

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
656.0 Kbit/s (median of 5 measurements)
Measured Min / Max
496.0 Kbit/s / 2.1 Mbit/s
Deviation
1.6 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0001% (1th pctl)
History

Uptime Metrics
Current Status
UP 1mo 1w 3d ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/99.8%/99.9%/99.4%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/99.8%/99.9%/99.4%)
Hibernating
No
Timestamps
First Seen
3y 4mo 1d ago (2023-07-07 00:00:00)
Last Seen
1h 45m 9s ago (2026-11-04 18:00:00)
Last Restarted
1mo 1w 3d ago (2026-09-25 09:04:07)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded. Historical rate-limit report outside the 24-hour window

Evaluated 2026-11-04 19:45 UTC. /details snapshot 2026-11-04 18:00:00 UTC (cached 13s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 12h ago).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
Status
Historical report — outside the 24-hour window
Rate Limit
4.19 Mbit/s
Burst Limit
629 KB
Write counter
27,434
Read counter
24,105
Reported
2026-11-03 17:00 UTC (1 day ago)

Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.

About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.

curl http://127.0.0.1:9035/metrics
History

Operator Identity

Source: AROI Validation API — 2026-11-04 10:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
4096R/0125D5C0 Philip Hands <phil-tor@hands.com>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
261FC1359C92D19875CED3BC9CDFB83006CBFB87 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

DNS Health
Status
Healthy (avg. 15.2s, 51st percentile)
Query Domain
7020bce7e2a64217bf34e70e9d48f845.261fc135.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Not enough data
Local AS 100% (~16 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
4194mAletschhorn (CH) FA01576E6B5CB77DF2330DEC999A7259BA3A48A3
Exit Address Used
109.169.33.163
Per-Instance Results
Cross Validation Attempt 1: Success, 13.5s (cv1_w1)
Cross Validation Attempt 2: Success, 14.5s (cv2_w1)
Cross Validation Attempt 3: Success, 19.7s (cv3_w1)
Cross Validation Attempt 4: Success, 13.0s (cv4_w1)
Tested: 2026-11-03 20:05:50 UTC
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
None
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 109.169.33.163:*
reject 188.126.64.4:*
reject 188.126.64.5:*
reject 192.121.121.30:*
reject 195.211.72.103:*
reject 195.82.146.5:*
reject 208.83.20.164:*
reject 208.94.116.204:*
reject 209.85.229.141:*
reject 212.48.192.26:*
reject 217.199.218.103:*
reject 66.102.13.141:*
reject 74.125.77.121:*
reject 77.120.115.137:*
reject 79.159.231.211:*
reject 81.39.108.235:*
reject 84.243.213.54:*
reject 84.243.213.93:*
reject 85.112.112.6:*
reject 85.17.121.160:*
reject 85.17.80.246:*
reject 85.17.80.248:*
reject 91.203.172.2:*
reject 95.143.192.240:*
reject 95.143.192.30:*
reject 95.161.0.203:*
reject 95.211.88.49:*
reject 95.211.88.51:*
reject 95.211.88.54:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Wed, 04 Nov 2026 19:45:09 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-04 18:45:05).

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 Flags Fast (BW|T) Guard BW (BW|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 2.1 Mbit/s (M) | 816.0 Kbit/s 2.1 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 23.2d | 8d 15.1d | 8.4d 40.4d | 5.2d 2026-11-03 17:04:59 2.1 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 656.0 Kbit/s (M) | 816.0 Kbit/s 656.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 71.3d | 8d 71.3d | 9.5d 40.4d | 5.5d 2026-11-04 11:05:01 656.0 Kbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 4.1 Mbit/s (R) | 816.0 Kbit/s 4.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 37.0d | 8d 25.1d | 6.8d 40.4d | 5.5d 2026-11-04 11:05:01 4.1 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 4.1 Mbit/s (R) | 816.0 Kbit/s 4.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 35.3d | 8d 22.0d | 6.6d 40.4d | 5.5d 2026-11-04 11:05:01 4.1 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 624.0 Kbit/s (M) | 816.0 Kbit/s 624.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 71.5d | 8d 71.4d | 10.9d 40.4d | 5.5d 2026-11-04 11:05:01 624.0 Kbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 4.1 Mbit/s (R) | 816.0 Kbit/s 4.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 71.5d | 8d 71.4d | 11.1d 40.4d | 5.5d 2026-11-04 11:05:01 4.1 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 4.1 Mbit/s (R) | 816.0 Kbit/s 4.1 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 34.9d | 8d 9.7d | 2.4d 40.4d | 5.5d 2026-11-04 11:05:01 4.1 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 1.8 Mbit/s (M) | 8.4 Mbit/s 1.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 9.9d | 8d 93.5d | 7621.1d 40.4d | 5.5d 2026-11-04 11:05:01 1.8 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 496.0 Kbit/s (M) | 816.0 Kbit/s 496.0 Kbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 71.5d | 8d 71.4d | 10.8d 40.4d | 5.5d 2026-11-04 11:05:01 496.0 Kbit/s (M)

N/T = this authority does not test IPv6 • — = not in this vote • 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.