View Relay "torbogen2"

Fingerprint: 448F821108ED29AA408F281625F66BE1D4BC19F4 | Operator: schmeling-ol.de v2 (5 relays) ✓ Validated | Family: 5 relays | email:rotor[]schmeling-ol.de... | AS9145 | Germany | SunOS

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
5/7 BW Auths Measured 16 Kbit/s Median
Stability
Overloaded | UP 8h 39m 34s ago | UP 94% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
5y 3w 6d ago
BW Weight
0.00% of Network | 17 Mbit/s Observed By Relay
Version
0.4.9.11 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: WFU below threshold : Weighted Fractional Uptime 92.6% 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 92.6% 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.
  • Write Bandwidth Limit Hit : Write rate limit (17 Mbit/s) was hit 3 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 (17 Mbit/s) was hit 16 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=17 Mbit/s, Burst=17 Mbit/s. Limits hit: Write=3, Read=16.

Connectivity and Location

Addresses
OR Address
dyndsl-085-016-193-038.ewe-ip-backbone.de
85.16.178.105:9002
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS9145
AS Name
EWE TEL GmbH (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, 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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 17.9 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.6d (1/9 DA above threshold)
Min/Max: 0.6d / 19136.5d (9/9 DA, Voting / Total Eligible)		 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Uptime Below (0/9 DA) 0.4d (R) ≥4.3d - 5.2d (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 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
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: 92.3% (0/9 DA above threshold)
Min/Max: 83.9% / 94.5% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.1d (9/9 DA above threshold)
Min/Max: 9.9d / 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 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
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: 92.3% (0/9 DA above threshold)
Min/Max: 83.9% / 94.5% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.1d (9/9 DA above threshold)
Min/Max: 9.9d / 10.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 17.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-07-03 03:02:32).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
17.91 Mbit/s
Advertised Bandwidth
16.78 Mbit/s
Rate Limit
16.78 Mbit/s
Burst Limit
16.78 Mbit/s
Total Data
244 TB (5 years)
1mo: 913 GB | 6mo: 4.9 TB | 1y: 12 TB | 5y: 244 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-03 03:02:32

Measured By
5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement
16.8 Kbit/s
Min / Max
11.2 Kbit/s / 19.2 Kbit/s
Network Participation: Consensus Weight: 0.0011% of network (24th pctl) | Guard: N/A | Middle: 0.0033% (37th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 8h 39m 34s ago
Overall Uptime (1M/6M/1Y/5Y)
94.6%/95.8%/96.6%/78.8%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (94.6%/95.8%/96.6%/78.8%)
Hibernating
No
Timestamps
First Seen
5y 3w 6d ago (2021-06-06 21:00:00)
Last Seen
2h 11m 26s ago (2026-07-03 01:00:00)
Last Restarted
8h 39m 34s ago (2026-07-02 18:31:52)
Last Changed Address
2026-07-02 21:00:00
[Warning] OVERLOADED — Rate limits hit W:3 R:16 (limit: 17 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
16.78 Mbit/s
Burst Limit
16.78 Mbit/s
Write Limit Hit
3 times
Read Limit Hit
16 times
Last Reported
10 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

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

AROI Domain (?)
schmeling-ol.de
Operator Validation
Validated (5/5 relays)
This Relay
Validated (uri-rsa)
Contact
email:rotor[]schmeling-ol.de url:https://www.schmeling-ol.de proof:uri-rsa abuse:rotor[]schmeling-ol.de pgp:5947E8F7992599E87FBD9C144E776B87256EB7BD xmpp:svschmel[]conversations.im os:SunOS autoupdate:y ciissversion:2
Family Configuration
Family Support
Happy Families (5) — Has family-cert in server descriptor (guide) | View Full Family (5)
MyFamily (legacy declarations) — none

Software and Version

Platform
SunOS — Tor 0.4.9.11 on SunOS
Version
0.4.9.11 — 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 Fri, 03 Jul 2026 03:11:23 GMT.

Consensus Evaluation

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

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, Fast 17.9 Mbit/s | 816.0 Kbit/s 17.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 10.1d | 8d 0.6d | 48.4d 0.4d | 5.1d 92.6% | 98.0% 10.1d | 1.0d 2026-07-02 18:53:53 16.8 Kbit/s
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 17.9 Mbit/s | 816.0 Kbit/s 17.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.1% | 98% 10.1d | 8d 0.6d | 10.1d 0.4d | 5.2d 92.1% | 98.0% 10.1d | 1.0d 2026-07-02 18:53:53 16.8 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 17.9 Mbit/s | 816.0 Kbit/s 17.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 9.9d | 8d 0.6d | 25.9d 0.4d | 5.2d 92.3% | 98.0% 9.9d | 1.0d 2026-07-02 18:53:53 16.8 Kbit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 17.9 Mbit/s | 816.0 Kbit/s 17.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 83.9% | 98% 10.6d | 8d 0.7d | 28.4d 0.4d | 5.2d 83.9% | 98.0% 10.6d | 1.0d 2026-07-02 18:53:53 16.8 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 17.9 Mbit/s | 816.0 Kbit/s 17.9 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 94.5% | 98% 10.0d | 8d 0.9d | 60.1d 0.4d | 4.3d 94.5% | 98.0% 10.0d | 1.0d 2026-06-29 12:50:37 11.2 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 17.9 Mbit/s | 816.0 Kbit/s 17.9 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 92.4% | 98% 10.5d | 8d 0.6d | 57.2d 0.4d | 5.4d 92.4% | 98.0% 10.5d | 1.0d 2026-07-02 18:53:53 19.2 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 17.9 Mbit/s | 816.0 Kbit/s 17.9 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 89.5% | 98% 10.1d | 8d 0.6d | 30.6d 0.4d | 5.3d 89.5% | 98.0% 10.1d | 1.0d 2026-07-02 18:53:53 16.8 Kbit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable 17.9 Mbit/s | 8.4 Mbit/s 17.9 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 89.3% | 98% 9.9d | 8d 19136.5d | 1364.1d 0.4d | 5.4d 89.3% | 98.0% 9.9d | 9.8d 2026-07-02 18:53:53 16.8 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 17.9 Mbit/s | 816.0 Kbit/s 17.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 92.6% | 98% 10.4d | 8d 0.6d | 53.1d 0.4d | 5.4d 92.6% | 98.0% 10.4d | 1.0d 2026-07-02 18:53:53 12.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.