View Relay "mycontribution"

Fingerprint: 51AE5656C81CD417479253A6363A123A007A2233 | Family: 2 relays | <gerard@g3wip.uk> | AS8560 | United Kingdom of Great Britain and Northern Ireland | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (18.7s, 94th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 432 Mbit/s Median
Stability
Not Overloaded | UP 6d 15h 53m ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen
9y 2mo 3w ago
BW Weight
0.03% of Network | 230 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
Issues Detected:
  • 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 : 4/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). dannenberg, faravahar, gabelmoo, maatuska and moria1 do not.
    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 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.
  • 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
uk.cloud-ip.cc
87.106.76.226:443
[2a00:da00:f460:f800::1]:443
Exit Address
87.106.76.226
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
AS8560
AS Name
IONOS SE (BGP.tools)
AS Rarity
Emerging (score: 1/5, 3.69% consensus weight, 149 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 5/9 | HSDir: 4/9 | Guard: 5/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 Meets (9/9 DA) 208.0 Mbit/s – 520.0 Mbit/s (5 DA measured)
80.0 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 Below (4/9 DA) Median: 12.4d (5/9 DA above threshold)
Min/Max: 0.8d / 1164.0d (9/9 DA, Voting / Total Eligible)		 ≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7613.3d
Uptime Meets (9/9 DA) 6.7d (R) ≥5.2d - 5.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
208.0 Mbit/s – 520.0 Mbit/s (5 DA measured)
80.0 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 (5/9 DA) 5/9 DA assigned Stable ≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7613.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Partial (8/9 DA) 6.7d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
208.0 Mbit/s – 520.0 Mbit/s (5 DA measured)
80.0 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 (5/9 DA) 5/9 DA assigned Stable ≥2.4d - 9.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7613.3d
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: 99.5% (9/9 DA above threshold)
Min/Max: 98.2% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.879% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 20.6d (9/9 DA above threshold)
Min/Max: 9.6d / 31.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 208.0 Mbit/s – 520.0 Mbit/s (5 DA measured)
80.0 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 Partial (9/9 DA) (only port 443) Port 80: No | 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 20:15:05).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
230.05 Mbit/s
Advertised Bandwidth
230.05 Mbit/s
Rate Limit
1.05 Gbit/s
Burst Limit
12.88 Gbit/s
Total Data
533 TB (5 years)
1mo: 58 TB | 6mo: 354 TB | 1y: 514 TB | 5y: 533 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 20:15:05

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
432.0 Mbit/s (median of 5 measurements)
Measured Min / Max
208.0 Mbit/s / 520.0 Mbit/s
Deviation
312.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0280% of network (90th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0887% (93th pctl)
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 5 years Throughput and write/read, last 30 days
1M 6M 1Y 5Y

Uptime and Stability

Uptime Metrics
Current Status
UP 6d 15h 53m ago
Overall Uptime (1M/6M/1Y/5Y)
99.5%/99.8%/72.4%/15.6%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.5%/99.8%/72.4%/15.6%)
Hibernating
No
Timestamps
First Seen
9y 2mo 3w ago (2017-08-13 21:00:00)
Last Seen
1h 45m 9s ago (2026-11-04 19:00:00)
Last Restarted
6d 15h 53m ago (2026-10-29 04:52:05)
Last Changed Address
2026-10-29 00:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 20:45 UTC. /details snapshot 2026-11-04 19:00:00 UTC (cached 10s ago). /bandwidth snapshot 2026-11-04 19:00:00 UTC (cached 30m ago).

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
No rate-limit report in available data
Rate Limit
—
Burst Limit
—
Write counter
—
Read counter
—
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
Uptime, last 6 months Uptime, last year Uptime, last 5 years Uptime, last 30 days
1M 6M 1Y 5Y

Operator and Family

Operator Identity

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

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
<gerard@g3wip.uk>
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
51AE5656C81CD417479253A6363A123A007A2233 (this relay)
97AF9CDBEEFDFDF0632845A14319BFE6B4454794
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 18.7s, 94th percentile)
Query Domain
2ebe6bac38c74e7d9116c54d60ed8601.51ae5656.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Local AS (exit's own network)
Local AS 100% (~60 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
prsv (GB) 7B972B75D36CA2CC83B2C817D309977B845A67A2
Exit Address Used
87.106.76.226
Per-Instance Results
Cross Validation Attempt 1: Success, 19.2s (cv1_w2)
Cross Validation Attempt 2: Success, 10.0s (cv2_w2)
Cross Validation Attempt 3: Success, 21.8s (cv3_w2)
Cross Validation Attempt 4: Success, 23.8s (cv4_w2)
Tested: 2026-11-04 08:10:27 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  43
  53
  143
  220
  389
  443-466
  531
  636
  706
  873
  989-995
  1194
  1293
  1723
  1755
  1863
  2001
  2086-2087
  2524-2526
  3690
  5000-5051
  5190
  5222-5223
  5228
  5555
  8082
  8332-8333
  8884-8892
  9418
  11371
  11964-12966
  19294
  64738
IPv6 Exit Policy Summary
accept: 
  43
  53
  143
  220
  389
  443-466
  531
  636
  706
  873
  989-995
  1194
  1293
  1723
  1755
  1863
  2001
  2086-2087
  2524-2526
  3690
  5000-5051
  5190
  5222-5223
  5228
  5555
  8082
  8332-8333
  8884-8892
  9418
  11371
  11964-12966
  19294
  64738
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 87.106.76.226:*
accept *:43
accept *:53
accept 133.0.0.0/8:80
accept *:143
accept *:220
accept *:389
accept *:443-466
accept *:531
accept *:636
accept *:706
accept *:873
accept *:989-995
accept *:1194
accept *:1293
accept *:1723
accept *:1755
accept *:1863
accept *:2001
accept *:2086-2087
accept *:2524-2526
accept *:3690
accept *:5190
accept *:5228
accept *:5000-5051
accept *:5222-5223
accept *:5555
accept *:8082
accept *:8332-8333
accept *:8884-8892
accept *:9418
accept *:11371
accept *:11964-12966
accept *:19294
accept *:64738
reject *:*

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

Consensus Evaluation

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

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 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) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 384.0 Mbit/s (M) | 816.0 Kbit/s 384.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.8% | 98% 20.6d | 8d 15.6d | 8.4d 6.7d | 5.2d 2026-11-04 04:52:36 384.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 520.0 Mbit/s (M) | 816.0 Kbit/s 520.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 22.4d | 8d 1.4d | 9.5d 6.7d | 5.5d 2026-11-04 04:52:36 520.0 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.7% | 98% 19.1d | 8d 12.4d | 6.8d 6.7d | 5.5d 2026-11-04 04:52:36 80.0 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 16.9d | 8d 1.0d | 6.6d 6.7d | 5.5d 2026-11-04 04:52:36 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 456.0 Mbit/s (M) | 816.0 Kbit/s 456.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 23.0d | 8d 1.4d | 10.9d 6.7d | 5.5d 2026-11-04 04:52:36 456.0 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 30.1d | 8d 28.5d | 11.1d 6.7d | 5.5d 2026-11-04 04:52:36 80.0 Mbit/s (R)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.2% | 98% 16.3d | 8d 0.8d | 2.4d 6.7d | 5.5d 2026-11-04 04:52:36 80.0 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Fast, Stable, Guard, Exit 208.0 Mbit/s (M) | 8.4 Mbit/s 208.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 9.6d | 8d 1164.0d | 7613.3d 6.7d | 5.5d 2026-11-04 04:52:36 208.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 432.0 Mbit/s (M) | 816.0 Kbit/s 432.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 31.2d | 8d 29.6d | 10.9d 6.7d | 5.5d 2026-11-04 04:52:36 432.0 Mbit/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.