View Relay "S1lentRelay"

Fingerprint: 78F15746534B6FC94EA63CA307590A8F1950F880 | Family: 1 relay | Cellum <contact@cellum.dev> | AS216188 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
6/6 BW Auths Measured 40 Kbit/s Median
Stability
Overloaded | UP 4d 10h 1m ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.00% of Network | 40 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: Time Known below threshold : Time Known 4.9 days is below 8 days requirement (3.1 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • 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
  • 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.
  • StaleDesc flag assigned : Relay descriptor is older than 18 hours
    Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
  • Write Bandwidth Limit Hit : Write rate limit (34 Mbit/s) was hit 22 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 (34 Mbit/s) was hit 29 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=34 Mbit/s, Burst=84 Mbit/s. Limits hit: Write=22, Read=29.

Addresses
OR Address
s1lent.dev
152.89.239.31:9001
[2a13:fd40:1:2::9997]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS216188
AS Name
Bieber IT GmbH (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Current Flags (3): Running, Valid, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 0/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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Meets (9/9 DA) 9/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Below (2/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 40.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 (0/9 DA) Median: 4.9d (0/9 DA above threshold)
Min/Max: 4.8d / 4.9d (9/9 DA, Voting / Total Eligible)
≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Uptime Below (0/9 DA) 4.4d (R) ≥6.5d - 6.6d (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 (0/9 DA) 0/9 DA assigned Stable ≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Prereq: V2Dir Below (2/9 DA) 2/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 4.9d (0/9 DA above threshold)
Min/Max: 3.9d / 4.9d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
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 (0/9 DA) 0/9 DA assigned Stable ≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Prereq: V2Dir Below (2/9 DA) 2/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 3.1 more days) Median: 4.9d (0/9 DA above threshold)
Min/Max: 3.9d / 4.9d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 40.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-336.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-05-14 21:15:08).

Capacity (Relay Reported)
Observed Bandwidth
40.91 Mbit/s
Advertised Bandwidth
40.91 Mbit/s
Rate Limit
100.66 Mbit/s
Burst Limit
209.72 Mbit/s
Total Data
182 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-14 21:15:08

Measured By
6/6 Bandwidth Authorities
Median Measurement
40.9 Kbit/s
Min / Max
33.6 Kbit/s / 57.6 Kbit/s
Deviation
24.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0029% of network (37th pctl) | Guard: N/A | Middle: 0.0087% (66th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 4d 10h 1m 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
4d 21h 15m ago (2026-05-10 00:00:00)
Last Seen
1h 15m 39s ago (2026-05-14 20:00:00)
Last Restarted
4d 10h 1m ago (2026-05-10 11:14:39)
Last Changed Address
2026-05-10 00:00:00
[Warning] OVERLOADED — Rate limits hit W:22 R:29 (limit: 34 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
33.55 Mbit/s
Burst Limit
83.89 Mbit/s
Write Limit Hit
22 times
Read Limit Hit
29 times
Last Reported
22 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator Identity

Source: AROI Validation API — 2026-05-14 14:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Cellum <contact@cellum.dev>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
78F15746534B6FC94EA63CA307590A8F1950F880 (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, 14 May 2026 21:15:38 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-05-14 21:15:08).

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 v6 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 Yes Running, Valid, Fast 40.9 Mbit/s | 816.0 Kbit/s 40.9 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.9d | 8d 4.9d | 51.0d 4.4d | 6.5d 100.0% | 98.0% 4.9d | 1.0d 2026-05-14 17:34:30 46.4 Kbit/s
dannenberg (DE) Yes Yes No N Yes Yes Running, Valid, Fast 40.9 Mbit/s | 816.0 Kbit/s 40.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.9d | 8d 4.9d | 49.9d 4.4d | 6.6d 100.0% | 98.0% 4.9d | 1.0d 2026-05-14 17:34:30 40.9 Kbit/s
dizum (NL) Yes Yes No N Yes Yes Running, Valid, V2Dir, Fast, StaleDesc 40.9 Mbit/s | 816.0 Kbit/s 40.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.9d | 8d 4.9d | 19.6d 4.4d | 6.6d 100.0% | 98.0% 4.9d | 1.0d 2026-05-13 23:23:49 [Stale] 33.6 Kbit/s
faravahar (US) Yes Yes No N Yes Yes Running, Valid, Fast 40.9 Mbit/s | 816.0 Kbit/s 40.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.8d | 8d 4.8d | 52.0d 4.4d | 6.6d 100.0% | 98.0% 4.8d | 1.0d 2026-05-14 17:34:30 40.9 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Yes Running, Valid, Fast 40.9 Mbit/s | 816.0 Kbit/s 40.9 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.9d | 8d 4.9d | 52.1d 4.4d | 6.6d 100.0% | 98.0% 4.9d | 1.0d 2026-05-14 17:34:30 37.6 Kbit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, StaleDesc 40.9 Mbit/s | 816.0 Kbit/s 40.9 Mbit/s | 256.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.9d | 8d 4.9d | 58.5d 4.4d | 6.6d 100.0% | 98.0% 4.9d | 1.0d 2026-05-13 23:23:49 [Stale] 57.6 Kbit/s
maatuska (SE) Yes Yes No Y Yes Yes Running, Valid, Fast 40.9 Mbit/s | 816.0 Kbit/s 40.9 Mbit/s | 336.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.8d | 8d 4.8d | 23.1d 4.4d | 6.6d 100.0% | 98.0% 4.8d | 1.0d 2026-05-14 17:34:30 44.0 Kbit/s
moria1 (US) Yes Yes No Y Yes Yes Running, Valid, Fast 40.9 Mbit/s | 8.4 Mbit/s 40.9 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.9d | 8d 4.9d | 328.2d 4.4d | 6.6d 100.0% | 98.0% 3.9d | 9.9d 2026-05-14 17:34:30 48.0 Kbit/s
tor26 (AT) Yes Yes No Y Yes Yes Running, Valid, Fast 40.9 Mbit/s | 816.0 Kbit/s 40.9 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.8d | 8d 4.8d | 52.2d 4.4d | 6.6d 100.0% | 98.0% 4.8d | 1.0d 2026-05-14 17:34:30 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.