View Relay "s0yb3an"

Fingerprint: C4C462506D54EDC8EFC8E88E32F4AE014755035A | Family: 1 relay | no(at)info(dot)com | AS3320 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
4/7 BW Auths Measured 41 Kbit/s Median
Stability
Not Overloaded | UP 17h 59m 40s ago
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 44 Mbit/s Observed By Relay
Version
0.4.9.8 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 19.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 19.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.
  • 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.

Addresses
OR Address
p57ab4873.dip0.t-ipconnect.de
87.171.72.115:30001
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.17% consensus weight, 46 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 6/9 | Stable: 3/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) 44.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 (2/9 DA) Median: 3.7d (2/9 DA above threshold)
Min/Max: 2.7d / 4214.1d (9/9 DA, Voting / Total Eligible)
≥10.0d - 12.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8503.9d
Uptime Below (0/9 DA) 0.8d (R) ≥5.4d - 5.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (6/9 DA) 6/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 (3/9 DA) 3/9 DA assigned Stable ≥10.0d - 12.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8503.9d
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: 19.6% (0/9 DA above threshold)
Min/Max: 16.0% / 53.8% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 22.8d (9/9 DA above threshold)
Min/Max: 9.8d / 33.8d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (6/9 DA) 6/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 (3/9 DA) 3/9 DA assigned Stable ≥10.0d - 12.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8503.9d
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: 19.6% (0/9 DA above threshold)
Min/Max: 16.0% / 53.8% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 22.8d (9/9 DA above threshold)
Min/Max: 9.8d / 33.8d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 44.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-08-06 06:45:10).

Capacity (Relay Reported)
Observed Bandwidth
44.20 Mbit/s
Advertised Bandwidth
41.94 Mbit/s
Rate Limit
41.94 Mbit/s
Burst Limit
67.11 Mbit/s
Total Data
1.7 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-06 06:45:10

Measured By
4/7 Bandwidth Authorities
Not measured by: faravahar, gabelmoo, maatuska
Median Measurement
41.9 Kbit/s
Min / Max
312 bit/s / 60.0 Kbit/s
Deviation
59.7 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0021% of network (33th pctl) | Guard: N/A | Middle: 0.0063% (58th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 17h 59m 40s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
17h 45m 43s ago (2026-08-05 14:00:00)
Last Seen
1h 45m 43s ago (2026-08-06 06:00:00)
Last Restarted
17h 59m 40s ago (2026-08-05 13:46:03)
Last Changed Address
2026-08-05 14:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-08-05 23:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
no(at)info(dot)com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
C4C462506D54EDC8EFC8E88E32F4AE014755035A (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.8 on Linux
Version
0.4.9.8Recommended
Version Status
Recommended

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 Thu, 06 Aug 2026 07:45:41 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-08-06 06: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 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 N Yes Running, Valid, V2Dir, Fast 44.2 Mbit/s | 816.0 Kbit/s 44.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 19.6% | 98% 23.7d | 8d 3.7d | 12.3d 0.8d | 5.6d 19.6% | 98.0% 23.7d | 1.0d 2026-08-05 20:35:06 41.9 Kbit/s
dannenberg (DE) Yes Yes No Y Yes Running, Valid, V2Dir, Stable 44.2 Mbit/s | 816.0 Kbit/s 44.2 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 43.1% | 98% 33.8d | 8d 10.8d | 10.6d 0.8d | 5.6d 43.1% | 98.0% 33.8d | 1.0d 2026-08-05 20:35:06 312 bit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 44.2 Mbit/s | 816.0 Kbit/s 44.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 16.0% | 98% 22.8d | 8d 2.7d | 10.0d 0.8d | 5.4d 16.0% | 98.0% 22.8d | 1.0d 2026-08-05 20:35:06 41.9 Kbit/s
faravahar (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 44.2 Mbit/s | 816.0 Kbit/s 44.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 18.3% | 98% 22.4d | 8d 3.2d | 10.1d 0.8d | 5.5d 18.3% | 98.0% 22.4d | 1.0d 2026-08-05 20:35:06 41.9 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir, Stable 44.2 Mbit/s | 816.0 Kbit/s 44.2 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 53.8% | 98% 32.4d | 8d 14.7d | 13.4d 0.8d | 5.5d 53.8% | 98.0% 32.4d | 1.0d 2026-08-05 20:35:06 41.9 Kbit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 44.2 Mbit/s | 816.0 Kbit/s 44.2 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 23.4% | 98% 18.7d | 8d 3.7d | 17.4d 0.8d | 5.5d 23.4% | 98.0% 18.7d | 1.0d 2026-08-05 20:35:06 60.0 Kbit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir 44.2 Mbit/s | 816.0 Kbit/s 44.2 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 17.4% | 98% 23.2d | 8d 3.2d | 10.8d 0.8d | 5.5d 17.4% | 98.0% 23.2d | 1.0d 2026-08-05 20:35:06 41.9 Kbit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable 44.2 Mbit/s | 8.4 Mbit/s 44.2 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 18.2% | 98% 9.8d | 8d 4214.1d | 8503.9d 0.8d | 5.4d 18.2% | 98.0% 9.8d | 9.9d 2026-08-05 20:35:06 41.6 Kbit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 44.2 Mbit/s | 816.0 Kbit/s 44.2 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 19.9% | 98% 22.8d | 8d 3.6d | 12.7d 0.8d | 5.5d 19.9% | 98.0% 22.8d | 1.0d 2026-08-05 20:35:06 34.4 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.