View Relay "sweetums"

Fingerprint: D4BEE74ED0FD4F99C40DBB4C02B9785EAC1AC2DA | Family: 1 relay | torrelay.3.axec@spamgourmet.org | AS3320 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast (3)
BW Verified
5/6 BW Auths Measured 10 Kbit/s Median
Stability
Overloaded | UP 14h 17m 45s ago | UP 99% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
5y 6mo 3w ago
BW Weight
0.00% of Network | 10 Mbit/s Observed By Relay
Version
0.4.9.5 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 : Observed bandwidth 1.3 MB/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.
  • Guard: WFU below threshold : Weighted Fractional Uptime 92.3% 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 92.3% 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.
  • Write Bandwidth Limit Hit : Write rate limit (10 Mbit/s) was hit 1,061 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (10 Mbit/s) was hit 1,189 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=10 Mbit/s, Burst=16 Mbit/s. Limits hit: Write=1,061, Read=1,189.

Connectivity and Location

Addresses
OR Address
p4ffbbe80.dip0.t-ipconnect.de
79.251.190.128:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS3320
AS Name
Deutsche Telekom AG (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.20% consensus weight, 53 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/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
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 Meets (9/9 DA) 10.3 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: 0.9d (1/9 DA above threshold)
Min/Max: 0.8d / 18553.7d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
Uptime Below (0/9 DA) 0.6d (R) ≥12.0d - 14.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
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: 92.3% (0/9 DA above threshold)
Min/Max: 92.0% / 92.7% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.2d (9/9 DA above threshold)
Min/Max: 9.4d / 10.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (9/9 DA) 9/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 ≥11.3d - 55.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥347.6d
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: 92.3% (0/9 DA above threshold)
Min/Max: 92.0% / 92.7% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.2d (9/9 DA above threshold)
Min/Max: 9.4d / 10.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 10.3 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-15 16:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
10.27 Mbit/s
Advertised Bandwidth
10.27 Mbit/s
Rate Limit
10.49 Mbit/s
Burst Limit
15.73 Mbit/s
Total Data
28 TB (5 years)
1mo: 353 GB | 6mo: 2.1 TB | 1y: 5.5 TB | 5y: 28 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-15 16:15:07

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
10.1 Kbit/s
Min / Max
3120 bit/s / 11.2 Kbit/s
Deviation
8.1 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0004% of network (15th pctl) | Guard: N/A | Middle: 0.0012% (26th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 14h 17m 45s ago
Overall Uptime (1M/6M/1Y/5Y)
99.7%/94.6%/92.4%/85.8%
Flag Uptime (1M/6M/1Y/5Y)
—/94.1%/91.9%/85.6%
Hibernating
No
Timestamps
First Seen
5y 6mo 3w ago (2020-08-21 00:00:00)
Last Seen
1h 45m 55s ago (2026-03-15 15:00:00)
Last Restarted
14h 17m 45s ago (2026-03-15 02:28:10)
Last Changed Address
2026-03-15 03:00:00
[Warning] OVERLOADED — Rate limits hit W:1061 R:1189 (limit: 10 Mbit/s)
General Overload (from /details)
Status
Not Reported

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)
Rate Limit
10.49 Mbit/s
Burst Limit
15.73 Mbit/s
Write Limit Hit
1,061 times
Read Limit Hit
1,189 times
Last Reported
16 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-15 09:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
torrelay.3.axec@spamgourmet.org
Family Configuration
Family Support
MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
D4BEE74ED0FD4F99C40DBB4C02B9785EAC1AC2DA (this relay)
Alleged Member: 1
(they don't list you back) 
A07B90C498B1A7BD0E3E73FE31DBE4DE9FE79E49
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.5 on Linux
Version
0.4.9.5 — 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 Sun, 15 Mar 2026 16:45:53 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-15 16:15:07).

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 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, Fast 10.3 Mbit/s | 816.0 Kbit/s 10.3 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 10.2d | 8d 0.9d | 59.7d 0.6d | 13.6d 92.3% | 98.0% 10.2d | 1.0d 2026-03-14 16:33:06 11.2 Kbit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, Fast 10.3 Mbit/s | 816.0 Kbit/s 10.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 10.1d | 8d 0.8d | 11.3d 0.6d | 14.3d 92.3% | 98.0% 10.1d | 1.0d 2026-03-14 16:33:06 10.1 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, Fast 10.3 Mbit/s | 816.0 Kbit/s 10.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.0% | 98% 10.2d | 8d 0.9d | 45.8d 0.6d | 12.0d 92.0% | 98.0% 10.2d | 1.0d 2026-03-14 16:33:06 10.1 Kbit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, Fast 10.3 Mbit/s | 816.0 Kbit/s 10.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.0% | 98% 10.6d | 8d 0.9d | 55.1d 0.6d | 14.5d 92.0% | 98.0% 10.6d | 1.0d 2026-03-14 16:33:06 10.1 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, Fast 10.3 Mbit/s | 816.0 Kbit/s 10.3 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 92.4% | 98% 10.2d | 8d 0.9d | 61.4d 0.6d | 14.4d 92.4% | 98.0% 10.2d | 1.0d 2026-03-14 16:33:06 3120 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, Fast 10.3 Mbit/s | 816.0 Kbit/s 10.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.7% | 98% 9.4d | 8d 0.9d | 62.0d 0.6d | 14.5d 92.7% | 98.0% 9.4d | 1.0d 2026-03-14 16:33:06 10.1 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, Fast 10.3 Mbit/s | 816.0 Kbit/s 10.3 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 92.4% | 98% 10.2d | 8d 0.9d | 40.2d 0.6d | 14.3d 92.4% | 98.0% 10.2d | 1.0d 2026-03-14 16:33:06 6080 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 10.3 Mbit/s | 8.4 Mbit/s 10.3 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 92.1% | 98% 9.9d | 8d 18553.7d | 347.6d 0.6d | 15.5d 92.1% | 98.0% 9.9d | 9.8d 2026-03-14 16:33:06 9.6 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, Fast 10.3 Mbit/s | 816.0 Kbit/s 10.3 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 10.3d | 8d 0.9d | 55.7d 0.6d | 14.5d 92.6% | 98.0% 10.3d | 1.0d 2026-03-14 16:33:06 3520 bit/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.