View Relay "sk4d9f2m8x1q7w3j"

Fingerprint: FDBEAC98530F2A4CF7FDF164695A93F6AC15BA18 | Family: 1 relay | diskstats@mailboxly.example | AS9044 | Switzerland | Linux

Consensus
Not In Consensus (2/9 Directory Auths, need 5)
BW Verified
1/7 BW Auths Measured 11 Kbit/s Median
Stability
Not Overloaded | DOWN 4d 20h 45m ago | UP 99% (1M)
Reachability
IPv4: 2/9 | v6: 2/9 (Directory Auths)
BW Weight
0.00% of Network | 17 Mbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • Not in consensus : Only 2/9 authorities voted for this relay (need 5)
    Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
  • IPv4 reachability issues : Only 2/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, faravahar, gabelmoo, longclaw, maatuska, moria1, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
  • 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).
  • 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: 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
  • 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.
  • Low bandwidth authority measurements : Only 1/7 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.
  • 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
34964.hostserv.eu
82.220.38.26:38417
[2001:1680:101:84a::1]:38417
Reachability (Directory Authorities)
IPv4
2/9
IPv6
2/9
Location
Country
Switzerland Switzerland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS9044
AS Name
BSE Software GmbH (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 3 operators)

Current Flags (2): Running, Valid
Eligible Flags (0): Running: 2/9 | Valid: 2/9 | V2Dir: 2/9 | Fast: 2/9 | Stable: 1/9 | HSDir: 1/9 | Guard: 1/9 | Exit: 1/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Below (2/9 DA) 2/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Partial (2/9 DA) 2/9 tested authorities reached relay ≥5/9 tested (majority) (≥5/9 DA)
Valid Descriptor Partial (2/9 DA) 2/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Below (1/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 17.6 Mbit/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 (1/9 DA) Median: 19.8d (1/9 DA above threshold)
Min/Max: 3.6d / 36.0d (2/9 DA, Voting / Total Eligible)
≥4.6d - 11.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8803.9d
Uptime Meets (9/9 DA) 5.6d (R) ≥2.7d - 3.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (2/9 DA) 2/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 ≥4.6d - 11.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8803.9d
Prereq: V2Dir Below (1/9 DA) 1/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (2/9 DA) Median: 99.9% (2/9 DA above threshold)
Min/Max: 99.8% / 100.0% (2/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Below (2/9 DA) Median: 30.4d (2/9 DA above threshold)
Min/Max: 24.1d / 36.8d (2/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (2/9 DA) 2/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 ≥4.6d - 11.1d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8803.9d
Prereq: V2Dir Below (1/9 DA) 1/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (2/9 DA) Median: 99.9% (2/9 DA above threshold)
Min/Max: 99.8% / 100.0% (2/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (2/9 DA) Median: 30.4d (2/9 DA above threshold)
Min/Max: 24.1d / 36.8d (2/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 17.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Partial (1/9 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly Restriction (by DA) Flagged (1/9 DA) 1/9 authorities assigned MiddleOnly Suspicious behavior, Sybil risk, or policy violation

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

Capacity (Relay Reported)
Observed Bandwidth
17.64 Mbit/s
Advertised Bandwidth
16.78 Mbit/s
Rate Limit
16.78 Mbit/s
Burst Limit
33.55 Mbit/s
Total Data
8.1 TB (6 months)
1mo: 6.5 TB | 6mo: 8.1 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-10 12:45:10

Measured By
1/7 Bandwidth Authorities
Not measured by: bastet, faravahar, gabelmoo, longclaw, moria1, tor26
Median Measurement
11.6 Kbit/s
Min / Max
6480 bit/s / 16.8 Kbit/s
Deviation
10.3 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0004% of network (12th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 4d 20h 45m ago
Overall Uptime (1M/6M/1Y/5Y)
99.9%/99.8%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.9%/99.8%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1mo 2w 1d ago (2026-08-25 16:00:00)
Last Seen
4d 20h 45m ago (2026-10-05 16:00:00)
Last Restarted
5d 14h 25m ago (2026-10-04 22:20:13)
Last Changed Address
2026-08-25 16:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

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

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
diskstats@mailboxly.example
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
FDBEAC98530F2A4CF7FDF164695A93F6AC15BA18 (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
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  465
  563
  587
  993
  995
  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 82.220.38.26:*
reject *:25
reject *:465
reject *:587
reject *:993
reject *:995
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Sat, 10 Oct 2026 12:45:46 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-10 12:45: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) No — — — Y No — — — — — — — — — — — —
dannenberg (DE) Yes Yes No Yes Y Yes Yes Running, Valid, Fast, MiddleOnly 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.8% | 98% 24.1d | 8d 3.6d | 4.6d 5.6d | 3.2d 99.8% | 98.0% 24.1d | 1.0d 2026-10-10 11:16:00 6480 bit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 17.6 Mbit/s | 816.0 Kbit/s 17.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 36.8d | 8d 36.0d | 11.1d 5.6d | 3.1d 100.0% | 98.0% 36.8d | 1.0d 2026-10-10 11:16:00 16.8 Kbit/s
faravahar (US) No — — — Y No — — — — — — — — — — — —
gabelmoo (DE) No — — — Y No — — — — — — — — — — — —
longclaw (US) No — — — Y No — — — — — — — — — — — —
maatuska (SE) No — — — N No — — — — — — — — — — — —
moria1 (US) No — — — Y No — — — — — — — — — — — —
tor26 (AT) No — — — Y No — — — — — — — — — — — —

— = 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.