View Relay "sexytiem"

Fingerprint: 882698B2CA1C3CC8B34751478BFB90CE84C72F36 | Family: 1 relay | 1024D/F796C534 ABSTornode... | AS24940 | Germany | FreeBSD

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (18.8s, 93rd percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 48 bit/s Median
Stability
Overloaded | UP 3d 13h 10m ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.00% of Network | 2 Mbit/s Observed By Relay
Version
0.4.9.17 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 2 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: Time Known below threshold : Time Known 3.4 days is below 8 days requirement (4.6 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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.
  • 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.
  • General Overload Active : Relay reported general overload at 2026-11-21 23: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.

Addresses
OR Address
sexytiem.internationalconspiracy.org
95.216.107.148:19731
[2a01:4f9:2b:75d::124:148]:19731
Exit Address
95.216.107.148
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
AS24940
AS Name
Hetzner Online GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 8.34% consensus weight, 250 operators)

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 1/9 | HSDir: 1/9 | Guard: 0/9 | Exit: 9/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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 2.0 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: 3.5d (0/9 DA above threshold)
Min/Max: 3.4d / 3.5d (9/9 DA, Voting / Total Eligible)
≥2.7d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥11610.2d
Uptime Below (0/9 DA) 3.6d (R) ≥6.2d - 6.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/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 ≥2.7d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥11610.2d
Prereq: V2Dir Meets (9/9 DA) 9/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: 3.5d (0/9 DA above threshold)
Min/Max: 3.0d / 3.5d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.4d
Guard Prereq: Fast Below (3/9 DA) 3/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 ≥2.7d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥11610.2d
Prereq: V2Dir Meets (9/9 DA) 9/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 4.5 more days) Median: 3.5d (0/9 DA above threshold)
Min/Max: 3.0d / 3.5d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 2.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (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-11-22 12:00:48).

Capacity (Relay Reported)
Observed Bandwidth
2.01 Mbit/s
Advertised Bandwidth
819.20 Kbit/s
Rate Limit
819.20 Kbit/s
Burst Limit
1.64 Mbit/s
Total Data
7.3 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-22 12:00:48

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Median Measurement
48 bit/s
Min / Max
8 bit/s / 816 bit/s
Deviation
808 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime Metrics
Current Status
UP 3d 13h 10m 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
3d 12h 2m ago (2026-11-19 01:00:00)
Last Seen
2h 2m 32s ago (2026-11-22 11:00:00)
Last Restarted
3d 13h 10m ago (2026-11-18 23:52:23)
Last Changed Address
2026-11-19 01:00:00
[Warning] OVERLOADED — General overload at 2026-11-21 23:00 UTC
General Overload (from /details)
Status
Reported
When
2026-11-21 23:00 UTC (14 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)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc

Operator Identity

Source: AROI Validation API — 2026-11-22 05:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
1024D/F796C534 ABSTornode <removethisbitincludingthedot.sexytiem.tornode.alex@trull.org>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
882698B2CA1C3CC8B34751478BFB90CE84C72F36 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
FreeBSD — Tor 0.4.9.17 on FreeBSD
Version
0.4.9.17 — Recommended
Version Status
Recommended

DNS Health
Status
Healthy (avg. 18.8s, 93rd percentile)
Query Domain
26127f66502e4042a8b84b347ebc05a0.882698b2.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
dreamachine (NL) FA8C7C4B6658B5008C86ACD5078214CD943DC511
Exit Address Used
95.216.107.148
Per-Instance Results
Cross Validation Attempt 1: Success, 16.7s (cv1_w2)
Cross Validation Attempt 2: Success, 20.8s (cv2_w2)
Cross Validation Attempt 3: Success, 20.1s (cv3_w2)
Cross Validation Attempt 4: Success, 17.8s (cv4_w2)
Tested: 2026-11-22 08:11:26 UTC
IPv4 Exit Policy Summary
accept: 
  80
  443
IPv6 Exit Policy Summary
None
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 95.216.107.148:*
accept *:80
accept *:443
reject *:*

Last fetch was at Sun, 22 Nov 2026 13:02:10 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-22 12:00:48).

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)
E30CF7B3 Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 2.0 Mbit/s | 816.0 Kbit/s 2.0 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.4d | 7d 3.4d | 5.3d 3.6d | 6.2d 100.0% | 98.0% 3.4d | 1.0d 2026-11-21 23:53:21 128 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 2.0 Mbit/s | 816.0 Kbit/s 2.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 9.0d 3.6d | 6.2d 100.0% | 98.0% 3.5d | 1.0d 2026-11-21 23:53:21 48 bit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 2.0 Mbit/s | 816.0 Kbit/s 2.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 7.6d 3.6d | 6.2d 100.0% | 98.0% 3.5d | 1.0d 2026-11-21 23:53:21 816 bit/s
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Exit 2.0 Mbit/s | 816.0 Kbit/s 2.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 7.9d 3.6d | 6.2d 100.0% | 98.0% 3.5d | 1.0d 2026-11-21 23:53:21 816 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 2.0 Mbit/s | 816.0 Kbit/s 2.0 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 9.0d 3.6d | 6.2d 100.0% | 98.0% 3.5d | 1.0d 2026-11-21 23:53:21 40 bit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Exit 2.0 Mbit/s | 816.0 Kbit/s 2.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 9.9d 3.6d | 6.2d 100.0% | 98.0% 3.5d | 1.0d 2026-11-21 23:53:21 40 bit/s
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 2.0 Mbit/s | 816.0 Kbit/s 2.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 2.7d 3.6d | 6.2d 100.0% | 98.0% 3.5d | 1.0d 2026-11-21 23:53:21 816 bit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 2.0 Mbit/s | 8.4 Mbit/s 2.0 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.0d | 8d 3.5d | 11610.2d 3.6d | 6.2d 100.0% | 98.0% 3.0d | 9.4d 2026-11-21 23:53:21 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 2.0 Mbit/s | 816.0 Kbit/s 2.0 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.5d | 8d 3.5d | 8.9d 3.6d | 6.2d 100.0% | 98.0% 3.5d | 1.0d 2026-11-21 23:53:21 40 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.