View Relay "unfug01"

Fingerprint: 0A8FB247EFCB0F4D4566613A464A6F0EC3EE0FF2 | Family: 1 relay | Unix User Group Furtwangen... | AS553 | Germany | Linux

Health Status

Consensus
In Consensus (8/8 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
3/5 BW Auths Measured
Stability
Not Overloaded | UP 14h 41m 40s ago | UP 6% (1M)
Reachability
IPv4: 8/9 | v6: 7/8 (Directory Auths)
First Seen
13h 45m 47s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.6 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: WFU below threshold : Weighted Fractional Uptime 4.2% 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 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.
  • HSDir: WFU below threshold : WFU 4.2% 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.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
141.28.77.189:443
[2001:7c0:f00:2077::189]:443
Reachability (Directory Authorities)
IPv4
8/9
IPv6
7/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS553
AS Name
Universitaet Stuttgart (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 3 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 1/8 | Stable: 0/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 0/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/8 DA) 8/8 authorities reached relay ≥5/8 DA ORPort reachable
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Meets (8/8 DA) 8/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (8/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Below (0/8 DA) 0 bit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/8 DA) Median: 1.0d (0/8 DA above threshold)
Min/Max: 0.0d / 1.1d (8/8 DA, Voting / Total Eligible)		 ≥16.6d - 58.6d (varies) (≥5/8 DA)
Uptime Below (0/8 DA) 0.6d (R) ≥10.4d - 10.7d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (1/8 DA) 1/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/8 DA) 0/8 DA assigned Stable ≥16.6d - 58.6d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 4.0% (0/8 DA above threshold)
Min/Max: 0.0% / 4.2% (8/8 DA, Voting / Total Eligible)		 ≥98.0% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 28.3d (7/8 DA above threshold)
Min/Max: 0.0d / 29.1d (8/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (1/8 DA) 1/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/8 DA) 0/8 DA assigned Stable ≥16.6d - 58.6d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 4.0% (0/8 DA above threshold)
Min/Max: 0.0% / 4.2% (8/8 DA, Voting / Total Eligible)		 ≥98% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 28.3d (7/8 DA above threshold)
Min/Max: 0.0d / 29.1d (8/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Below (0/8 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-04-29 03:45:03).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
8.19 Mbit/s
Burst Limit
16.38 Mbit/s
Total Data
714 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-29 03:45:03

Measured By
3/5 Bandwidth Authorities
Not measured by: longclaw, tor26
Median Measurement
0.0 bit/s
Min / Max
0 bit/s / 8 bit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 14h 41m 40s ago
Overall Uptime (1M/6M/1Y/5Y)
6.1%/43.3%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (6.1%/43.3%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
13h 45m 47s ago (2026-04-28 14:00:00)
Last Seen
1h 45m 47s ago (2026-04-29 02:00:00)
Last Restarted
14h 41m 40s ago (2026-04-28 13:04:07)
Last Changed Address
2026-04-28 14:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-28 20:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Unix User Group Furtwangen (https://www.unfug.hs-furtwangen.de/)
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
0A8FB247EFCB0F4D4566613A464A6F0EC3EE0FF2 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

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, 29 Apr 2026 03:45:46 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-04-29 03:45:03).

Per-Authority Details

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) No — — — N No — — — — — — — — — — — —
dannenberg (DE) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 4.2% | 98% 27.5d | 8d 1.0d | 46.1d 0.6d | 10.7d 4.2% | 98.0% 27.5d | 1.0d 2026-04-28 13:06:49 —
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 2.7% | 98% 29.1d | 8d 0.7d | 42.5d 0.6d | 10.4d 2.7% | 98.0% 29.1d | 1.0d 2026-04-28 13:06:49 —
faravahar (US) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 4.2% | 98% 27.5d | 8d 1.0d | 58.6d 0.6d | 10.7d 4.2% | 98.0% 27.5d | 1.0d 2026-04-28 13:06:49 —
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 4.0% | 98% 28.6d | 8d 1.0d | 56.9d 0.6d | 10.7d 4.0% | 98.0% 28.6d | 1.0d 2026-04-28 13:06:49 8 bit/s
longclaw (US) Yes Yes No — Y Yes — Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 248.0 Mbit/s OR 16.0 Mbit/s 4.1% | 98% 28.0d | 8d 1.0d | 63.4d 0.6d | 10.7d 4.1% | 98.0% 28.0d | 1.0d 2026-04-28 13:06:49 —
maatuska (SE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 328.0 Mbit/s OR 16.0 Mbit/s 3.9% | 98% 28.6d | 8d 0.9d | 16.6d 0.6d | 10.6d 3.9% | 98.0% 28.6d | 1.0d 2026-04-28 13:06:49 8 bit/s
moria1 (US) Yes Yes No — Y Yes Yes Valid, V2Dir 0 bit/s | 8.4 Mbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 292.0d 0.6d | 11.8d 0.0% | 98.0% 0.0d | 9.9d 2026-04-28 13:06:49 8 bit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 4.0% | 98% 28.9d | 8d 1.1d | 59.3d 0.6d | 10.8d 4.0% | 98.0% 28.9d | 1.0d 2026-04-28 13:06:49 —

— = 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.