View Relay "SwiftCamp"

Fingerprint: 28C480D3FEE56BEB3F0574F840D21C8BDB0AE680 | Family: 1 relay | LO <lars789852 AT yahoo dot de> | AS13101 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
5/7 BW Auths Measured 4096 bit/s Median
Stability
Overloaded | UP 21h 57m 6s ago | UP 86% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2w 1d 8h ago
BW Weight
0.00% of Network | 5 Mbit/s Observed By Relay
Version
0.4.9.11 Not 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 5 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.
  • Guard: WFU below threshold : Weighted Fractional Uptime 86.0% 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: WFU below threshold : WFU 86.0% 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.
  • 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.
  • General Overload Active : Relay reported general overload at 2026-09-20 08: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.
  • Write Bandwidth Limit Hit : Write rate limit (4 Mbit/s) was hit 173 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 (4 Mbit/s) was hit 11,996 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=4 Mbit/s, Burst=2.1 MB. Limits hit: Write=173, Read=11,996.

Connectivity and Location

Addresses
OR Address
46.22.159.29:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS13101
AS Name
TNG Stadtnetz GmbH (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 5.2 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 / 17453.0d (9/9 DA, Voting / Total Eligible)		 ≥3.0d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8429.7d
Uptime Below (0/9 DA) 0.9d (R) ≥8.3d - 8.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (7/9 DA) 7/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 ≥3.0d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8429.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 85.9% (0/9 DA above threshold)
Min/Max: 85.8% / 86.3% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 8.0d (7/9 DA above threshold)
Min/Max: 7.8d / 8.4d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (7/9 DA) 7/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 ≥3.0d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8429.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 85.9% (0/9 DA above threshold)
Min/Max: 85.8% / 86.3% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 8.0d (7/9 DA above threshold)
Min/Max: 7.8d / 8.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 5.2 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.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-09-20 15:00:35).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
5.17 Mbit/s
Advertised Bandwidth
4.10 Mbit/s
Rate Limit
4.10 Mbit/s
Burst Limit
16.78 Mbit/s
Total Data
755 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-09-20 15:00:35

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
4096 bit/s
Min / Max
168 bit/s / 35.2 Kbit/s
Deviation
35.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (5th pctl) | Guard: N/A | Middle: 0.0002% (6th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 21h 57m 6s ago
Overall Uptime (1M/6M/1Y/5Y)
86.1%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
100.0%/—/—/—
Hibernating
No
Timestamps
First Seen
2w 1d 8h ago (2026-09-05 07:00:00)
Last Seen
2h 2m 56s ago (2026-09-20 13:00:00)
Last Restarted
21h 57m 6s ago (2026-09-19 17:05:50)
Last Changed Address
2026-09-19 18:00:00
[Warning] OVERLOADED — General overload at 2026-09-20 08:00 UTC; Rate limits hit W:173 R:11996 (limit: 4 Mbit/s)
General Overload (from /details)
Status
Reported
When
2026-09-20 08:00 UTC (7 hours 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)
Rate Limit
4.10 Mbit/s
Burst Limit
2.1 MB
Write Limit Hit
173 times
Read Limit Hit
11,996 times
Last Reported
23 hours ago
Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-09-20 07:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
LO <lars789852 AT yahoo dot de>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
28C480D3FEE56BEB3F0574F840D21C8BDB0AE680 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

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, 20 Sep 2026 15:02:34 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-09-20 15:00:35).

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, V2Dir 5.2 Mbit/s | 816.0 Kbit/s 5.2 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 86.0% | 98% 8.0d | 8d 0.9d | 12.0d 0.9d | 8.5d 86.0% | 98.0% 8.0d | 1.0d 2026-09-20 11:06:49 168 bit/s
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 5.2 Mbit/s | 816.0 Kbit/s 5.2 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 85.8% | 98% 7.9d | 8d 0.8d | 3.0d 0.9d | 8.5d 85.8% | 98.0% 7.9d | 1.0d 2026-09-20 11:06:49 344 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 5.2 Mbit/s | 816.0 Kbit/s 5.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 85.9% | 98% 8.0d | 8d 0.9d | 11.6d 0.9d | 8.3d 85.9% | 98.0% 8.0d | 1.0d 2026-09-20 11:06:49 4096 bit/s
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 5.2 Mbit/s | 816.0 Kbit/s 5.2 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 85.9% | 98% 8.4d | 8d 0.9d | 13.1d 0.9d | 9.1d 85.9% | 98.0% 8.4d | 1.0d 2026-09-20 11:06:49 4096 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 5.2 Mbit/s | 816.0 Kbit/s 5.2 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 86.0% | 98% 8.0d | 8d 0.9d | 12.2d 0.9d | 8.4d 86.0% | 98.0% 8.0d | 1.0d 2026-09-20 11:06:49 1200 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 5.2 Mbit/s | 816.0 Kbit/s 5.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 85.9% | 98% 8.4d | 8d 0.9d | 13.3d 0.9d | 8.4d 85.9% | 98.0% 8.4d | 1.0d 2026-09-20 11:06:49 4096 bit/s
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 5.2 Mbit/s | 816.0 Kbit/s 5.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 85.9% | 98% 8.0d | 8d 0.9d | 11.1d 0.9d | 8.3d 85.9% | 98.0% 8.0d | 1.0d 2026-09-20 11:06:49 4096 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable 5.2 Mbit/s | 8.4 Mbit/s 5.2 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 86.3% | 98% 7.8d | 8d 17453.0d | 8429.7d 0.9d | 8.8d 86.3% | 98.0% 7.8d | 9.8d 2026-09-20 11:06:49 35.2 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 5.2 Mbit/s | 816.0 Kbit/s 5.2 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 85.9% | 98% 8.4d | 8d 0.9d | 12.3d 0.9d | 8.3d 85.9% | 98.0% 8.4d | 1.0d 2026-09-20 11:06:49 8.0 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.