View Relay "9g4net1"

Fingerprint: 6CFBB403418932B5208E39A80B3F12952C454C61 | Family: 4 relays | tor@9g4.net | AS49683 | Germany | Linux

Consensus
In Consensus (7/7 Directory Auths)
BW Verified
2/6 BW Auths Measured 10 Kbit/s Median
Stability
Overloaded | UP 1mo 1w 2d ago | UP 97% (1M)
Reachability
IPv4: 7/7 (Directory Auths)
BW Weight
0.00% of Network | 10 Mbit/s Observed By Relay
Version
0.4.8.10 Not Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 11 Mbit/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • 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 2/6 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.8.10 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.
  • General Overload Active : Relay reported general overload at 2026-07-17 18:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Addresses
OR Address
171.22.173.221:4040
Reachability (Directory Authorities)
IPv4
7/7
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS49683
AS Name
MASSIVEGRID LTD (BGP.tools)
AS Rarity
Epic (score: 3/5, <0.05% consensus weight, 11 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Stable
Eligible Flags (5): Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 4/7 | Stable: 6/7 | HSDir: 1/7 | Guard: 0/7 | Exit: 0/7
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (7/7 DA) 7/7 authorities reached relay ≥4/7 DA ORPort reachable
Valid Descriptor Meets (7/7 DA) 7/7 authorities assigned Valid Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir DirPort Available Meets (7/7 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast Speed Meets (7/7 DA) 10.8 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/7 DA) Median: 5.7d (1/7 DA above threshold)
Min/Max: 4.6d / 11794.1d (7/7 DA, Voting / Total Eligible)
≥8.2d - 14.9d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9062.0d
Uptime Meets (7/7 DA) 39.7d (R) ≥8.4d - 8.6d (varies) (≥4/7 DA)
HSDir Prereq: Fast Meets (4/7 DA) 4/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (6/7 DA) 6/7 DA assigned Stable ≥8.2d - 14.9d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9062.0d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (6/7 DA) Median: 99.0% (6/7 DA above threshold)
Min/Max: 98.0% / 99.3% (7/7 DA, Voting / Total Eligible)
≥98.0% (≥4/7 DA)
Time Known Meets (6/7 DA) Median: 18.1d (7/7 DA above threshold)
Min/Max: 9.7d / 18.6d (7/7 DA, Voting / Total Eligible)
≥1.0d (most) (≥4/7 DA)
[Stricter] moria1: ≥9.7d
Guard Prereq: Fast Meets (4/7 DA) 4/7 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (6/7 DA) 6/7 DA assigned Stable ≥8.2d - 14.9d (varies) (≥4/7 DA)
[Stricter] moria1: ≥9062.0d
Prereq: V2Dir Meets (7/7 DA) 7/7 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥4/7 DA)
WFU Meets (6/7 DA) Median: 99.0% (6/7 DA above threshold)
Min/Max: 98.0% / 99.3% (7/7 DA, Voting / Total Eligible)
≥98% (≥4/7 DA)
Time Known Meets (7/7 DA) Median: 18.1d (7/7 DA above threshold)
Min/Max: 9.7d / 18.6d (7/7 DA, Voting / Total Eligible)
≥8 days (≥4/7 DA)
Bandwidth Below (0/7 DA) 10.8 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.0 Mbit/s (≥4/7 DA)
Exit Exit Policy Below (0/7 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-20 00:00:25).

Capacity (Relay Reported)
Observed Bandwidth
10.84 Mbit/s
Advertised Bandwidth
10.84 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
143 TB (5 years)
1mo: 931 GB | 6mo: 4.4 TB | 1y: 91 TB | 5y: 143 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-20 00:00:25

Measured By
2/6 Bandwidth Authorities
Not measured by: bastet, faravahar, moria1, tor26
Median Measurement
10.8 Kbit/s
Min / Max
4320 bit/s / 10.8 Kbit/s
Deviation
6512 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0000% (2th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 1mo 1w 2d ago
Overall Uptime (1M/6M/1Y/5Y)
97.9%/94.0%/70.9%/78.6%
Flag Uptime (1M/6M/1Y/5Y)
92.1%/92.5%/70.2%/78.2%
Hibernating
No
Timestamps
First Seen
1y 4mo 2w ago (2025-03-01 21:00:00)
Last Seen
2h 2m 32s ago (2026-07-19 22:00:00)
Last Restarted
1mo 1w 2d ago (2026-06-10 08:27:00)
Last Changed Address
2026-04-06 23:00:00
[Warning] OVERLOADED — General overload at 2026-07-17 18:00 UTC
General Overload (from /details)
Status
Reported
When
2026-07-17 18:00 UTC (2 days ago)

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Not Reported
Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc

Operator Identity

Source: AROI Validation API — 2026-07-19 16:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
tor@9g4.net
Family Configuration
Family Support
MyFamily Only (4) — Legacy only. Consider migrating to Happy Families. | View Full Family (4)
Happy Families (family-cert)
Effective Members: 0
none

Platform
Linux — Tor 0.4.8.10 on Linux
Version
0.4.8.10Not 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: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Mon, 20 Jul 2026 00:02:22 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-07-20 00:00:25).

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 (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) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable 10.8 Mbit/s | 816.0 Kbit/s 10.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.1% | 98% 18.6d | 8d 5.7d | 21.1d 39.7d | 8.4d 99.1% | 98.0% 18.6d | 1.0d 2026-07-19 10:47:31 10.8 Kbit/s
dannenberg (DE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable 10.8 Mbit/s | 816.0 Kbit/s 10.8 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 18.2d | 8d 5.5d | 8.2d 39.7d | 8.6d 99.0% | 98.0% 18.2d | 1.0d 2026-07-19 10:47:31 5040 bit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 10.8 Mbit/s | 816.0 Kbit/s 10.8 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.8% | 98% 14.2d | 8d 4.6d | 13.2d 39.7d | 8.6d 98.8% | 98.0% 14.2d | 1.0d 2026-07-19 10:47:31 10.8 Kbit/s
faravahar (US) Yes Yes No Y Yes Running, Valid, V2Dir, Stable 10.8 Mbit/s | 816.0 Kbit/s 10.8 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 98.0% | 98% 17.2d | 8d 5.1d | 14.4d 39.7d | 8.6d 98.0% | 98.0% 17.2d | 1.0d 2026-07-19 10:47:31 10.8 Kbit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 10.8 Mbit/s | 816.0 Kbit/s 10.8 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 18.2d | 8d 7.7d | 14.9d 39.7d | 8.6d 99.2% | 98.0% 18.2d | 1.0d 2026-07-19 10:47:31 4320 bit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir, Stable 10.8 Mbit/s | 8.4 Mbit/s 10.8 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 98.5% | 98% 9.7d | 8d 11794.1d | 9062.0d 39.7d | 8.6d 98.5% | 98.0% 9.71d | 9.75d 2026-07-19 10:47:31 10.8 Kbit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir, Stable 10.8 Mbit/s | 816.0 Kbit/s 10.8 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 99.3% | 98% 18.1d | 8d 7.6d | 21.0d 39.7d | 8.6d 99.3% | 98.0% 18.1d | 1.0d 2026-07-19 10:47:31 10.8 Kbit/s

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