View Relay "Unnamed"

Fingerprint: 5D947419DF366CAED357601771944E1DD2606A00 | Family: 1 relay | AS204957 | Switzerland | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Healthy (14.2s, 37th percentile) (via exitdnshealth.1aeo.com)
BW Verified
5/6 BW Auths Measured 6560 bit/s Median
Stability
Overloaded | UP 1d 5h 13m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1d 4h 46m ago
BW Weight
0.00% of Network | 16 Mbit/s Observed By Relay
Version
0.4.9.5 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: Time Known below threshold : Time Known 1.1 days is below 8 days requirement (6.9 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.
  • Read Bandwidth Limit Hit : Read rate limit (17 Mbit/s) was hit 1 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=17 Mbit/s, Burst=34 Mbit/s. Limits hit: Write=0, Read=1.

Connectivity and Location

Addresses
OR Address
vps.hostry.com
45.90.57.27:4443
Exit Address
45.90.57.27
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Switzerland Switzerland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS204957
AS Name
GREEN FLOID LLC (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 7 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 0/9 | HSDir: 0/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
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) 16.5 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 (0/9 DA) Median: 1.1d (0/9 DA above threshold)
Min/Max: 0.5d / 1.1d (9/9 DA, Voting / Total Eligible)		 ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
Uptime Below (0/9 DA) 1.2d (R) ≥13.7d - 14.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 97.4% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 1.1d (0/9 DA above threshold)
Min/Max: 1.1d / 1.1d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥11.5d - 55.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥356.4d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 97.4% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 6.9 more days) Median: 1.1d (0/9 DA above threshold)
Min/Max: 1.1d / 1.1d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 16.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-13 23:45:02).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
16.54 Mbit/s
Advertised Bandwidth
16.54 Mbit/s
Rate Limit
16.78 Mbit/s
Burst Limit
33.55 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-13 23:45:02

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
6560 bit/s
Min / Max
8 bit/s / 16.5 Kbit/s
Deviation
16.5 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (0th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 5h 13m 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
1d 4h 46m ago (2026-03-12 19:00:00)
Last Seen
5h 46m 38s ago (2026-03-13 18:00:00)
Last Restarted
1d 5h 13m ago (2026-03-12 18:33:35)
Last Changed Address
2026-03-12 19:00:00
[Warning] OVERLOADED — Rate limits hit W:0 R:1 (limit: 17 Mbit/s)
General Overload (from /details)
Status
Not Reported

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)
Rate Limit
16.78 Mbit/s
Burst Limit
33.55 Mbit/s
Write Limit Hit
0 times
Read Limit Hit
1 times
Last Reported
1 days ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-13 16:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
none
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
5D947419DF366CAED357601771944E1DD2606A00 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 14.2s, 37th percentile)
Query Domain
ae155eb1f6294c7eaa71dc454535196a.5d947419.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
3/3 instances succeeded
First Hop
giesskanne (DE) 72270EB58EDEBE727AA29E67417628DBCE889FAE
Exit Address Used
45.90.57.27
Per-Instance Results
Cross Validation Attempt 1: Success, 18.6s (cv2_w2)
Cross Validation Attempt 2: Success, 12.7s (cv3_w2)
Cross Validation Attempt 3: Success, 11.4s (cv4_w2)
Tested: 2026-03-13 19:11:15 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  465
  563
  587
  993
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
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 45.90.57.27:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:465
reject *:563
reject *:587
reject *:993
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Fri, 13 Mar 2026 23:46:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-13 23:45:02).

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 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 Yes — Y Yes Running, Valid, V2Dir, Exit 16.5 Mbit/s | 816.0 Kbit/s 16.5 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.1d | 8d 1.1d | 58.0d 1.2d | 14.6d 100.0% | 98.0% 1.1d | 1.0d 2026-03-13 17:52:49 8 bit/s
dannenberg (DE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 16.5 Mbit/s | 816.0 Kbit/s 16.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.4% | 98% 1.1d | 8d 0.5d | 11.5d 1.2d | 14.7d 97.4% | 98.0% 1.1d | 1.0d 2026-03-13 17:52:49 16.5 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 16.5 Mbit/s | 816.0 Kbit/s 16.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.1d | 8d 1.1d | 46.2d 1.2d | 13.7d 100.0% | 98.0% 1.1d | 1.0d 2026-03-13 17:52:49 16.5 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 16.5 Mbit/s | 816.0 Kbit/s 16.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.1d | 8d 1.1d | 53.2d 1.2d | 14.7d 100.0% | 98.0% 1.1d | 1.0d 2026-03-13 17:52:49 16.5 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 16.5 Mbit/s | 816.0 Kbit/s 16.5 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.1d | 8d 1.1d | 59.7d 1.2d | 14.7d 100.0% | 98.0% 1.1d | 1.0d 2026-03-13 17:52:49 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 16.5 Mbit/s | 816.0 Kbit/s 16.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.1d | 8d 1.1d | 59.2d 1.2d | 14.7d 100.0% | 98.0% 1.1d | 1.0d 2026-03-13 17:52:49 16.5 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 16.5 Mbit/s | 816.0 Kbit/s 16.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.1d | 8d 1.1d | 39.2d 1.2d | 14.7d 100.0% | 98.0% 1.1d | 1.0d 2026-03-13 17:52:49 6560 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 16.5 Mbit/s | 8.4 Mbit/s 16.5 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.1d | 8d 1.1d | 356.4d 1.2d | 16.6d 100.0% | 98.0% 1.1d | 9.8d 2026-03-13 17:52:49 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 16.5 Mbit/s | 816.0 Kbit/s 16.5 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.1d | 8d 1.1d | 55.6d 1.2d | 15.3d 100.0% | 98.0% 1.1d | 1.0d 2026-03-13 17:52:49 8 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.