View Relay "Greyhound"

Fingerprint: F7A2585F207A64EEA8A8B0FC86DCFB699BFC88D1 | Family: 1 relay | prometheusnhm_(at)_proton_(dot)_me | AS3320 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
5/7 BW Auths Measured 39 Kbit/s Median
Stability
Overloaded | UP 8h 2m 22s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3d 21h 15m ago
BW Weight
0.00% of Network | 39 Mbit/s Observed By Relay
Version
0.4.9.9 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.8% 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 3.8 days is below 8 days requirement (4.2 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 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 97.8% 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.
  • Write Bandwidth Limit Hit : Write rate limit (42 Mbit/s) was hit 11 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (42 Mbit/s) was hit 21 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=42 Mbit/s, Burst=50 Mbit/s. Limits hit: Write=11, Read=21.

Connectivity and Location

Addresses
OR Address
p4fd22f11.dip0.t-ipconnect.de
79.210.47.17:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS3320
AS Name
Deutsche Telekom AG (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.22% consensus weight, 53 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/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
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) 39.9 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: 1.9d (1/9 DA above threshold)
Min/Max: 1.8d / 10308.6d (9/9 DA, Voting / Total Eligible)		 ≥29.0d - 53.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Uptime Below (0/9 DA) 0.3d (R) ≥6.9d - 7.0d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/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 ≥29.0d - 53.4d (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: 97.8% (0/9 DA above threshold)
Min/Max: 97.4% / 97.9% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 3.6d (0/9 DA above threshold)
Min/Max: 3.2d / 3.8d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (8/9 DA) 8/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 ≥29.0d - 53.4d (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: 97.8% (0/9 DA above threshold)
Min/Max: 97.4% / 97.9% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 4.4 more days) Median: 3.6d (0/9 DA above threshold)
Min/Max: 3.2d / 3.8d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 39.9 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.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-06-13 07:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
39.89 Mbit/s
Advertised Bandwidth
39.89 Mbit/s
Rate Limit
41.94 Mbit/s
Burst Limit
50.33 Mbit/s
Total Data
71 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-06-13 07:15:08

Measured By
5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement
39.9 Kbit/s
Min / Max
35.2 Kbit/s / 53.6 Kbit/s
Network Participation: Consensus Weight: 0.0027% of network (38th pctl) | Guard: N/A | Middle: 0.0081% (65th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 8h 2m 22s 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
3d 21h 15m ago (2026-06-09 11:00:00)
Last Seen
1h 15m 39s ago (2026-06-13 07:00:00)
Last Restarted
8h 2m 22s ago (2026-06-13 00:13:17)
Last Changed Address
2026-06-13 03:00:00
[Warning] OVERLOADED — Rate limits hit W:11 R:21 (limit: 42 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
41.94 Mbit/s
Burst Limit
50.33 Mbit/s
Write Limit Hit
11 times
Read Limit Hit
21 times
Last Reported
15 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-06-13 00:00 UTC

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

Software and Version

Platform
Linux — Tor 0.4.9.9 on Linux
Version
0.4.9.9 — 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 Sat, 13 Jun 2026 08:15:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-06-13 07:15:08).

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 No — Y Yes Running, Valid, V2Dir 39.9 Mbit/s | 816.0 Kbit/s 39.9 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 3.8d | 8d 1.9d | 54.9d 0.3d | 7.8d 97.8% | 98.0% 3.8d | 1.0d 2026-06-13 01:53:18 39.9 Kbit/s
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 39.9 Mbit/s | 816.0 Kbit/s 39.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.5% | 98% 3.6d | 8d 1.8d | 30.0d 0.3d | 7.3d 97.5% | 98.0% 3.6d | 1.0d 2026-06-13 01:53:18 39.9 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 39.9 Mbit/s | 816.0 Kbit/s 39.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.8% | 98% 3.8d | 8d 1.9d | 32.2d 0.3d | 7.0d 97.8% | 98.0% 3.8d | 1.0d 2026-06-13 01:53:18 39.9 Kbit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 39.9 Mbit/s | 816.0 Kbit/s 39.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 97.9% | 98% 3.6d | 8d 1.8d | 50.8d 0.3d | 7.0d 97.9% | 98.0% 3.6d | 1.0d 2026-06-13 01:53:18 39.9 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 39.9 Mbit/s | 816.0 Kbit/s 39.9 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 97.9% | 98% 3.8d | 8d 1.9d | 53.4d 0.3d | 7.2d 97.9% | 98.0% 3.8d | 1.0d 2026-06-13 01:53:18 44.0 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 39.9 Mbit/s | 816.0 Kbit/s 39.9 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 97.9% | 98% 3.6d | 8d 1.8d | 58.1d 0.3d | 7.0d 97.9% | 98.0% 3.6d | 1.0d 2026-06-13 01:53:18 44.0 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 39.9 Mbit/s | 816.0 Kbit/s 39.9 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 97.7% | 98% 3.8d | 8d 1.9d | 29.0d 0.3d | 7.0d 97.7% | 98.0% 3.8d | 1.0d 2026-06-13 01:53:18 53.6 Kbit/s
moria1 (US) Yes Yes No — Y Yes Valid, V2Dir, Fast, Stable 39.9 Mbit/s | 8.4 Mbit/s 39.9 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 97.4% | 98% 3.2d | 8d 10308.6d | 328.2d 0.3d | 7.3d 97.4% | 98.0% 3.2d | 9.9d 2026-06-13 01:53:18 35.2 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 39.9 Mbit/s | 816.0 Kbit/s 39.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 97.9% | 98% 3.6d | 8d 1.8d | 55.4d 0.3d | 6.9d 97.9% | 98.0% 3.6d | 1.0d 2026-06-13 01:53:18 47.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.