View Relay "iDidEditTheConfig"

Fingerprint: 2FA57599B3B7314BDA3BE7370E1D7C027CD078C4 | Family: 1 relay | www.rubdos.be/about 0x1213DC10... | AS9031 | Belgium | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
6/7 BW Auths Measured 33 Kbit/s Median
Stability
Not Overloaded | UP 6h 50m 34s ago | UP 97% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
BW Weight
0.00% of Network | 39 Mbit/s Observed By Relay
Version
0.4.9.6 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 97.5% 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: 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
  • HSDir: WFU below threshold : WFU 97.5% 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.

Addresses
OR Address
94.105.105.23.dyn.edpnet.net
94.105.105.23:9002
[2a02:578:859d:700:8b44:5716:382d:a7da]:9002
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Belgium Belgium
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS9031
AS Name
EDPNET Belgium BV (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Current Flags (3): Running, Valid, 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
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 (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 39.3 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.7d (1/9 DA above threshold)
Min/Max: 2.9d / 13974.0d (9/9 DA, Voting / Total Eligible)
≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Uptime Below (0/9 DA) 0.3d (R) ≥13.4d - 13.7d (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 ≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 97.5% (0/9 DA above threshold)
Min/Max: 97.2% / 97.7% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.4d (9/9 DA above threshold)
Min/Max: 9.9d / 12.5d (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 (1/9 DA) 1/9 DA assigned Stable ≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 97.5% (0/9 DA above threshold)
Min/Max: 97.2% / 97.7% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.4d (9/9 DA above threshold)
Min/Max: 9.9d / 12.5d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 39.3 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-05-27 10:15:07).

Capacity (Relay Reported)
Observed Bandwidth
39.30 Mbit/s
Advertised Bandwidth
33.55 Mbit/s
Rate Limit
33.55 Mbit/s
Burst Limit
67.11 Mbit/s
Total Data
31 TB (1 year)
1mo: 3.3 TB | 6mo: 21 TB | 1y: 31 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-27 10:15:07

Measured By
6/7 Bandwidth Authorities
Not measured by: dannenberg
Median Measurement
33.6 Kbit/s
Min / Max
28.8 Kbit/s / 38.4 Kbit/s
Network Participation: Consensus Weight: 0.0020% of network (30th pctl) | Guard: N/A | Middle: 0.0061% (59th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 6h 50m 34s ago
Overall Uptime (1M/6M/1Y/5Y)
97.1%/97.6%/97.5%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (97.1%/97.6%/97.5%/0.0%)
Hibernating
No
Timestamps
First Seen
8mo 2w 5d ago (2025-09-10 00:00:00)
Last Seen
1h 15m 38s ago (2026-05-27 09:00:00)
Last Restarted
6h 50m 34s ago (2026-05-27 03:25:04)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-05-27 03:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
www.rubdos.be/about 0x1213DC10 <check-my AT website 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
2FA57599B3B7314BDA3BE7370E1D7C027CD078C4 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.6 on Linux
Version
0.4.9.6Recommended
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 Wed, 27 May 2026 10:15:37 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-05-27 10:15:07).

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 39.3 Mbit/s | 816.0 Kbit/s 39.3 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 97.5% | 98% 12.1d | 8d 2.9d | 50.5d 0.3d | 13.4d 97.5% | 98.0% 12.1d | 1.0d 2026-05-27 03:27:06 38.4 Kbit/s
dannenberg (DE) Yes Yes No Y Yes Yes Running, Valid, Fast 39.3 Mbit/s | 816.0 Kbit/s 39.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 12.4d | 8d 3.7d | 46.6d 0.3d | 13.7d 97.6% | 98.0% 12.4d | 1.0d 2026-05-27 03:27:06 33.6 Kbit/s
dizum (NL) Yes Yes No N Yes Yes Running, Valid, Fast 39.3 Mbit/s | 816.0 Kbit/s 39.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.3% | 98% 12.4d | 8d 3.7d | 21.2d 0.3d | 13.7d 97.3% | 98.0% 12.4d | 1.0d 2026-05-27 03:27:06 33.6 Kbit/s
faravahar (US) Yes Yes No N Yes Yes Running, Valid, Fast 39.3 Mbit/s | 816.0 Kbit/s 39.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.7% | 98% 12.5d | 8d 3.9d | 51.7d 0.3d | 13.7d 97.7% | 98.0% 12.5d | 1.0d 2026-05-27 03:27:06 33.6 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Yes Running, Valid, Fast 39.3 Mbit/s | 816.0 Kbit/s 39.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 12.5d | 8d 3.9d | 53.0d 0.3d | 13.8d 97.6% | 98.0% 12.5d | 1.0d 2026-05-27 03:27:06 28.8 Kbit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, Fast 39.3 Mbit/s | 816.0 Kbit/s 39.3 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 97.5% | 98% 12.1d | 8d 3.0d | 58.0d 0.3d | 13.7d 97.5% | 98.0% 12.1d | 1.0d 2026-05-27 03:27:06 38.4 Kbit/s
maatuska (SE) Yes Yes No Y Yes Yes Running, Valid, Fast 39.3 Mbit/s | 816.0 Kbit/s 39.3 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 97.3% | 98% 11.6d | 8d 2.9d | 24.6d 0.3d | 13.5d 97.3% | 98.0% 11.6d | 1.0d 2026-05-27 03:27:06 31.2 Kbit/s
moria1 (US) Yes Yes No Y Yes Yes Running, Valid, Fast, Stable 39.3 Mbit/s | 8.4 Mbit/s 39.3 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 97.2% | 98% 9.9d | 8d 13974.0d | 340.7d 0.3d | 14.2d 97.2% | 98.0% 9.91d | 9.89d 2026-05-27 03:27:06 28.8 Kbit/s
tor26 (AT) Yes Yes No Y Yes Yes Running, Valid, Fast 39.3 Mbit/s | 816.0 Kbit/s 39.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 97.7% | 98% 12.4d | 8d 3.9d | 54.0d 0.3d | 13.8d 97.7% | 98.0% 12.4d | 1.0d 2026-05-27 03:27:06 32.8 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.