View Relay "rubberbootes"

Fingerprint: 1FCC3A2AD4BE7D2891A55A80EBA5E784B5485CD0 | Family: 1 relay | mail@domain.com | AS44869 | Denmark | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
6/6 BW Auths Measured 65 Kbit/s Median
Stability
Not Overloaded | UP 4d 11h 25m ago | UP 38% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 64 Mbit/s Observed By Relay
Version
0.4.8.10 Not 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 45.1% 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 45.1% 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.
  • Tor version not recommended : Running Tor version 0.4.8.10 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Addresses
OR Address
80.208.58.219.static.fibianet.dk
80.208.58.219:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Denmark Denmark
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS44869
AS Name
FIBIA P/S (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 3/9 | HSDir: 2/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) 65.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: 4.3d (1/9 DA above threshold)
Min/Max: 3.2d / 10292.5d (9/9 DA, Voting / Total Eligible)
≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Uptime Below (0/9 DA) 4.5d (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 (3/9 DA) 3/9 DA assigned Stable ≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
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: 45.1% (0/9 DA above threshold)
Min/Max: 44.0% / 68.4% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 19.0d (9/9 DA above threshold)
Min/Max: 9.9d / 19.6d (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 (3/9 DA) 3/9 DA assigned Stable ≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
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: 45.1% (0/9 DA above threshold)
Min/Max: 44.0% / 68.4% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 19.0d (9/9 DA above threshold)
Min/Max: 9.9d / 19.6d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 65.0 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
64.96 Mbit/s
Advertised Bandwidth
64.96 Mbit/s
Rate Limit
209.72 Mbit/s
Burst Limit
268.44 Mbit/s
Total Data
343 TB (1 year)
1mo: 800 GB | 6mo: 171 TB | 1y: 343 TB
Measurement (Directory Authority Verified)

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

Measured By
6/6 Bandwidth Authorities
Median Measurement
65.0 Kbit/s
Min / Max
48.8 Kbit/s / 96.0 Kbit/s
Deviation
47.2 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0039% of network (44th pctl) | Guard: N/A | Middle: 0.0117% (71th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 4d 11h 25m ago
Overall Uptime (1M/6M/1Y/5Y)
38.1%/76.2%/86.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
32.2%/75.3%/85.5%/—
Hibernating
No
Timestamps
First Seen
10mo 1w 1d ago (2025-07-10 00:00:00)
Last Seen
1h 15m 39s ago (2026-05-14 20:00:00)
Last Restarted
4d 11h 25m ago (2026-05-10 09:50:38)
Last Changed Address
2026-05-03 10:00:00
Overload Status: Not Overloaded — No overload conditions reported.

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
mail@domain.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
1FCC3A2AD4BE7D2891A55A80EBA5E784B5485CD0 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.8.10 on Linux
Version
0.4.8.10Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

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 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 65.0 Mbit/s | 816.0 Kbit/s 65.0 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 45.1% | 98% 19.0d | 8d 4.3d | 51.0d 4.5d | 6.5d 45.1% | 98.0% 19.0d | 1.0d 2026-05-14 05:22:27 88.0 Kbit/s
dannenberg (DE) Yes Yes No N Yes Running, Valid, V2Dir, Fast 65.0 Mbit/s | 816.0 Kbit/s 65.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 44.8% | 98% 18.9d | 8d 4.2d | 49.9d 4.5d | 6.6d 44.8% | 98.0% 18.9d | 1.0d 2026-05-14 05:22:27 65.0 Kbit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 65.0 Mbit/s | 816.0 Kbit/s 65.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 44.4% | 98% 18.6d | 8d 3.2d | 19.6d 4.5d | 6.6d 44.4% | 98.0% 18.6d | 1.0d 2026-05-14 05:22:27 65.0 Kbit/s
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir, Fast 65.0 Mbit/s | 816.0 Kbit/s 65.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 45.0% | 98% 19.0d | 8d 4.3d | 52.0d 4.5d | 6.6d 45.0% | 98.0% 19.0d | 1.0d 2026-05-14 05:22:27 65.0 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 65.0 Mbit/s | 816.0 Kbit/s 65.0 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 46.4% | 98% 19.4d | 8d 5.5d | 52.1d 4.5d | 6.6d 46.4% | 98.0% 19.4d | 1.0d 2026-05-14 05:22:27 59.2 Kbit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 65.0 Mbit/s | 816.0 Kbit/s 65.0 Mbit/s | 256.0 Mbit/s OR 16.0 Mbit/s 45.7% | 98% 18.7d | 8d 4.3d | 58.5d 4.5d | 6.6d 45.7% | 98.0% 18.7d | 1.0d 2026-05-14 05:22:27 49.6 Kbit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 65.0 Mbit/s | 816.0 Kbit/s 65.0 Mbit/s | 336.0 Mbit/s OR 16.0 Mbit/s 44.0% | 98% 19.6d | 8d 4.3d | 23.1d 4.5d | 6.6d 44.0% | 98.0% 19.6d | 1.0d 2026-05-14 05:22:27 96.0 Kbit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable 65.0 Mbit/s | 8.4 Mbit/s 65.0 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 68.4% | 98% 9.9d | 8d 10292.5d | 328.2d 4.5d | 6.6d 68.4% | 98.0% 9.91d | 9.89d 2026-05-14 05:22:27 48.8 Kbit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 65.0 Mbit/s | 816.0 Kbit/s 65.0 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 46.1% | 98% 19.4d | 8d 5.4d | 52.2d 4.5d | 6.6d 46.1% | 98.0% 19.4d | 1.0d 2026-05-14 05:22:27 59.2 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.