View Relay "thingyRelay"

Fingerprint: 914CFE7B96AE33D02914FBC53D8BCA1D0F4996BE | Family: 1 relay | pfoul@uom.edu.gr | AS12364 | Greece | Linux

Consensus
Not In Consensus (1/8 Directory Auths, need 5)
BW Verified
1/5 BW Auths Measured 72 bit/s Median
Stability
Not Overloaded | DOWN 18h 46m 3s ago
Reachability
IPv4: 1/9 | v6: 0/8 (Directory Auths)
BW Weight
0.00% of Network | 868 Kbit/s Observed By Relay
Version
0.4.9.6 Recommended
Issues Detected:
  • Not in consensus : Only 1/8 authorities voted for this relay (need 5)
    Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
  • IPv4 reachability issues : Only 1/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
  • IPv6 not reachable : 0/8 authorities that test IPv6 can reach your IPv6 address
    Suggestion: Verify IPv6 is correctly configured: 1) Check ORPort binding includes IPv6 address, 2) Firewall allows IPv6 traffic, 3) IPv6 address is publicly routable. Test with: curl -6 http://ipv6.icanhazip.com/
  • 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 0.1 MB/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: WFU below threshold : Weighted Fractional Uptime 70.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.
  • Guard: Time Known below threshold : Time Known 1.6 days is below 8 days requirement (6.4 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.
  • HSDir: WFU below threshold : WFU 70.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.
  • Low bandwidth authority measurements : Only 1/5 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • 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.

Addresses
OR Address
195-251-211-90.uom.gr
195.251.211.90:443
Reachability (Directory Authorities)
IPv4
1/9
IPv6
0/8 (1 don't test)
Location
Country
Greece Greece
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS12364
AS Name
University of Macedonia, Economic and Social Sciences (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (0): Running: 1/8 | Valid: 1/8 | V2Dir: 1/8 | Fast: 0/8 | Stable: 1/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 0/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Below (1/8 DA) 1/8 authorities reached relay ≥5/8 DA ORPort reachable
IPv6 Reachability Below (0/7 DA) 0/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Partial (1/8 DA) 1/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (1/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 868.4 Kbit/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 (1/8 DA) Median: 20564.7d (1/8 DA above threshold) ≥18.7d - 60.9d (varies) (≥5/8 DA)
Uptime Below (0/8 DA) 2.0d (R) ≥12.9d - 13.1d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (0/8 DA) 0/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 (1/8 DA) 1/8 DA assigned Stable ≥18.7d - 60.9d (varies) (≥5/8 DA)
Prereq: V2Dir Below (1/8 DA) 1/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 70.2% (0/8 DA above threshold) ≥98.0% (≥5/8 DA)
Time Known Below (0/8 DA) Median: 1.6d (0/8 DA above threshold) ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/8 DA) 0/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 (1/8 DA) 1/8 DA assigned Stable ≥18.7d - 60.9d (varies) (≥5/8 DA)
Prereq: V2Dir Below (1/8 DA) 1/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 70.2% (0/8 DA above threshold) ≥98% (≥5/8 DA)
Time Known Below (0/8 DA) (need 6.4 more days) Median: 1.6d (0/8 DA above threshold) ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 868.4 Kbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-22 09:45:07).

Capacity (Relay Reported)
Observed Bandwidth
868.35 Kbit/s
Advertised Bandwidth
819.20 Kbit/s
Rate Limit
819.20 Kbit/s
Burst Limit
1.64 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-22 09:45:07

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

Uptime Metrics
Current Status
DOWN 18h 46m 3s 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
2d 46m 3s ago (2026-04-20 10:00:00)
Last Seen
18h 46m 3s ago (2026-04-21 16:00:00)
Last Restarted
1d 23h 1m ago (2026-04-20 11:44:52)
Last Changed Address
2026-04-20 10:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-04-22 02:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
pfoul@uom.edu.gr
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
914CFE7B96AE33D02914FBC53D8BCA1D0F4996BE (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, 22 Apr 2026 10:46:01 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-04-22 09:45: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) No N No
dannenberg (DE) No N No
dizum (NL) No N No
faravahar (US) No N No
gabelmoo (DE) No Y No
longclaw (US) No Y No
maatuska (SE) No Y No
moria1 (US) Yes Yes No Y Yes Valid, V2Dir, Stable, StaleDesc 868.4 Kbit/s | 8.4 Mbit/s 868.4 Kbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 70.2% | 98% 1.6d | 8d 20564.7d | 303.2d 2.0d | 12.9d 70.2% | 98.0% 1.6d | 9.9d 2026-04-21 06:04:56 [Stale] 72 bit/s
tor26 (AT) No Y No

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