View Relay "middy"

Fingerprint: 474AEA3228AA680ABEA78CF13E44EACBBBCEFC6D | Family: 1 relay | admin@sum1.nz | AS64073 | New Zealand | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast (3)
BW Verified
5/7 BW Auths Measured 1 Mbit/s Median
Stability
Not Overloaded | UP 1d 21h 6m ago | UP 85% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
1mo 2w 1d ago
BW Weight
0.00% of Network | 10 Mbit/s Observed By Relay
Version
0.4.9.14 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).
  • 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 1.2 Mbit/s – 5.8 Mbit/s. dizum, longclaw and maatuska used the relay-reported 9.6 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.
  • Guard: WFU below threshold : Weighted Fractional Uptime 96.9% 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 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: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • HSDir: WFU below threshold : WFU 96.9% 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
mail.sum1.nz
118.67.199.221:25565
[2407:8b00:1168:6801:face:b00c:d3ad:beef]:25565
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
New Zealand New Zealand
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS64073
AS Name
VETTA TRADING LIMITED (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (3): Running, Valid, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 2/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Partial (8/9 DA) 1.2 Mbit/s – 5.8 Mbit/s (5 DA measured)
9.6 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 Below (1/9 DA) Median: 4.7d (1/9 DA above threshold)
Min/Max: 2.2d / 16772.7d (9/9 DA, Voting / Total Eligible)		 ≥5.8d - 10.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9751.5d
Uptime Below (0/9 DA) 1.9d (R) ≥4.3d - 4.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
1.2 Mbit/s – 5.8 Mbit/s (5 DA measured)
9.6 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 Below (2/9 DA) 2/9 DA assigned Stable ≥5.8d - 10.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9751.5d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 96.9% (0/9 DA above threshold)
Min/Max: 94.6% / 97.2% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 16.6d (9/9 DA above threshold)
Min/Max: 9.7d / 18.2d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
1.2 Mbit/s – 5.8 Mbit/s (5 DA measured)
9.6 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 Below (2/9 DA) 2/9 DA assigned Stable ≥5.8d - 10.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9751.5d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 96.9% (0/9 DA above threshold)
Min/Max: 94.6% / 97.2% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 16.6d (9/9 DA above threshold)
Min/Max: 9.7d / 18.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.2 Mbit/s – 5.8 Mbit/s (5 DA measured)
9.6 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 Below (0/9 DA) Port 80: No | Port 443: No (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-10-14 14:15:30).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
10.39 Mbit/s
Advertised Bandwidth
9.65 Mbit/s
Rate Limit
9.65 Mbit/s
Burst Limit
20.97 Mbit/s
Total Data
3.7 TB (6 months)
1mo: 3.1 TB | 6mo: 3.7 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-14 14:15:30

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
1.4 Mbit/s (median of 5 measurements)
Measured Min / Max
1.2 Mbit/s / 5.8 Mbit/s
Deviation
4.6 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (7th pctl) | Guard: N/A | Middle: 0.0003% (8th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 21h 6m ago
Overall Uptime (1M/6M/1Y/5Y)
85.1%/84.4%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/84.0%/—/—
Hibernating
No
Timestamps
First Seen
1mo 2w 1d ago (2026-08-30 09:00:00)
Last Seen
1h 16m ago (2026-10-14 13:00:00)
Last Restarted
1d 21h 6m ago (2026-10-12 17:09:04)
Last Changed Address
2026-08-30 09:00:00
Overload Status: Not Overloaded — No overload conditions reported.
History
Uptime, last 6 months Uptime, last 30 days
1M 6M

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-14 06:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
admin@sum1.nz
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
474AEA3228AA680ABEA78CF13E44EACBBBCEFC6D (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 14 Oct 2026 14:15:59 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-14 14:15:30).

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) HSDir WFU (M|T) HSDir TK (M|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes No — Y Yes Yes Running, Valid, Fast 5.8 Mbit/s (M) | 816.0 Kbit/s 5.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 96.9% | 98% 16.6d | 8d 4.7d | 10.0d 1.9d | 4.7d 96.9% | 98.0% 16.6d | 1.0d 2026-10-14 09:23:09 5.8 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, Fast 1.2 Mbit/s (M) | 816.0 Kbit/s 1.2 Mbit/s (M) | 288.0 Mbit/s OR 16.8 Mbit/s 96.9% | 98% 17.4d | 8d 2.2d | 5.8d 1.9d | 4.4d 96.9% | 98.0% 17.4d | 1.0d 2026-10-14 09:23:09 1.2 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, Fast 9.6 Mbit/s (R) | 816.0 Kbit/s 9.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.9% | 98% 16.6d | 8d 4.7d | 10.1d 1.9d | 4.4d 96.9% | 98.0% 16.6d | 1.0d 2026-10-14 09:23:09 9.6 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, Fast not published | 816.0 Kbit/s not published | 288.0 Mbit/s OR 16.8 Mbit/s 97.0% | 98% 17.4d | 8d 3.7d | 10.9d 1.9d | 4.5d 97.0% | 98.0% 17.4d | 1.0d 2026-10-14 09:23:09 9.6 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, Fast 1.4 Mbit/s (M) | 816.0 Kbit/s 1.4 Mbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 96.9% | 98% 16.6d | 8d 4.6d | 10.0d 1.9d | 4.4d 96.9% | 98.0% 16.6d | 1.0d 2026-10-14 09:23:09 1.4 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes — Running, Valid, Fast, Stable 9.6 Mbit/s (R) | 816.0 Kbit/s 9.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 97.2% | 98% 18.2d | 8d 6.9d | 10.4d 1.9d | 4.4d 97.2% | 98.0% 18.2d | 1.0d 2026-10-14 09:23:09 9.6 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, Fast 9.6 Mbit/s (R) | 816.0 Kbit/s 9.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.9% | 98% 16.6d | 8d 4.7d | 9.8d 1.9d | 4.4d 96.9% | 98.0% 16.6d | 1.0d 2026-10-14 09:23:09 9.6 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, Stable 3.8 Mbit/s (M) | 8.4 Mbit/s 3.8 Mbit/s (M) | 208.0 Mbit/s OR 16.8 Mbit/s 94.6% | 98% 9.7d | 8d 16772.7d | 9751.5d 1.9d | 4.3d 94.6% | 98.0% 9.7d | 9.8d 2026-10-14 09:23:09 3.8 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, Fast 1.4 Mbit/s (M) | 816.0 Kbit/s 1.4 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 96.8% | 98% 16.7d | 8d 3.7d | 10.3d 1.9d | 4.5d 96.8% | 98.0% 16.7d | 1.0d 2026-10-14 09:23:09 1.4 Mbit/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.