View Relay "wrogregpx2"

Fingerprint: `EB5DF0124A5EC281E82F0038B2F45FA7EC7C7C75` | Family: 1 relay | px2@funetia.pl | AS59444 | Poland | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Exit (3)
DNS Health: Healthy (17.5s, 79th percentile) (via exitdnshealth.1aeo.com)
BW Verified: 5/7 BW Auths Measured 2480 bit/s Median
Stability: Overloaded | UP 4d 13h 51m ago | UP 44% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 11y 4mo 1d ago
BW Weight: 0.00% of Network | 4 Mbit/s Observed By Relay
Version: 0.4.9.12 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: bandwidth below threshold : Observed bandwidth 5 Mbit/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 59.6% 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: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
HSDir: WFU below threshold : WFU 59.6% 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.
Write Bandwidth Limit Hit : Write rate limit (4 Mbit/s) was hit 114 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 (4 Mbit/s) was hit 111 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=4 Mbit/s, Burst=1.0 MB. Limits hit: Write=114, Read=111.

Connectivity and Location

Addresses

OR Address: host-176-121-81-51.amsnet.pl
176.121.81.51:1443
Exit Address: 176.121.81.51

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Poland
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS59444
AS Name: Andrzej Szreter AMSNET (BGP.tools)
AS Rarity: Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (3): Running, Valid, Exit

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	Below (0/9 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Meets (9/9 DA)	4.6 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 (2/9 DA)	Median: 3.7d (1/9 DA above threshold) Min/Max: 3.6d / 10330.4d (9/9 DA, Voting / Total Eligible)	≥3.1d - 12.1d (varies) (≥5/9 DA) [Stricter] moria1: ≥8370.7d
Stable	Uptime	Below (0/9 DA)	4.6d (R)	≥8.2d - 8.5d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (4/9 DA)	4/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 (2/9 DA)	2/9 DA assigned Stable	≥3.1d - 12.1d (varies) (≥5/9 DA) [Stricter] moria1: ≥8370.7d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 59.7% (0/9 DA above threshold) Min/Max: 59.2% / 60.7% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 12.6d (9/9 DA above threshold) Min/Max: 9.5d / 12.7d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below (4/9 DA)	4/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 (2/9 DA)	2/9 DA assigned Stable	≥3.1d - 12.1d (varies) (≥5/9 DA) [Stricter] moria1: ≥8370.7d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 59.7% (0/9 DA above threshold) Min/Max: 59.2% / 60.7% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 12.6d (9/9 DA above threshold) Min/Max: 9.5d / 12.7d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	4.6 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.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-09-20 10:45:09).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 4.60 Mbit/s
Advertised Bandwidth: 4.19 Mbit/s
Rate Limit: 4.19 Mbit/s
Burst Limit: 8.39 Mbit/s
Total Data: 11 TB (5 years)
1mo: 138 GB | 6mo: 1.1 TB | 1y: 2.1 TB | 5y: 11 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-09-20 10:45:09

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement: 2480 bit/s
Min / Max: 616 bit/s / 4192 bit/s
Deviation: 3576 bit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0002% (1th pctl)

Uptime and Stability

Uptime Metrics

Current Status: UP 4d 13h 51m ago
Overall Uptime (1M/6M/1Y/5Y): 44.8%/69.6%/79.9%/71.4%
Flag Uptime (1M/6M/1Y/5Y): —/—/—/71.9%
Hibernating: No

Timestamps

First Seen: 11y 4mo 1d ago (2015-05-25 02:00:00)
Last Seen: 1h 15m 45s ago (2026-09-20 10:00:00)
Last Restarted: 4d 13h 51m ago (2026-09-15 21:24:03)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — Rate limits hit W:114 R:111 (limit: 4 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: 4.19 Mbit/s
Burst Limit: 1.0 MB
Write Limit Hit: 114 times
Read Limit Hit: 111 times
Last Reported: 21 hours ago

Recommendations

Consider increasing RelayBandwidthRate
Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-09-20 03:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: px2@funetia.pl

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

EB5DF0124A5EC281E82F0038B2F45FA7EC7C7C75 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.12 on Linux
Version: 0.4.9.12 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Status

Healthy (avg. 17.5s, 79th percentile)

Query Domain

0ce7e407a38f434dae6164d416389bed.eb5df012.tor.exit.validator.1aeo.com

DNS Result

Resolved to 64.65.4.1

Cross-Validation

4/4 instances succeeded

First Hop

KllxTest (DE) ABC481E950876FD267A626C5E881768C34D6CD3D

Exit Address Used

176.121.81.51

Per-Instance Results

Cross Validation Attempt 1:	Success, 20.0s	(cv1_w4)
Cross Validation Attempt 2:	Success, 21.9s	(cv2_w4)
Cross Validation Attempt 3:	Success, 10.4s	(cv3_w4)
Cross Validation Attempt 4:	Success, 17.8s	(cv4_w4)

Tested: 2026-09-19 19:22:16 UTC

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

accept: 
  53
  80
  443
  6660-6667

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 176.121.81.51:*
accept *:53
accept *:443
accept *:80
accept *:6660-6667
reject *:*

Last fetch was at Sun, 20 Sep 2026 11:15:42 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-09-20 10:45:09).

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, Fast, Exit	4.6 Mbit/s \| 816.0 Kbit/s	4.6 Mbit/s \| 208.0 Mbit/s OR 16.0 Mbit/s	59.6% \| 98%	12.7d \| 8d	3.7d \| 12.0d	4.6d \| 8.6d	59.6% \| 98.0%	12.7d \| 1.0d	2026-09-20 09:24:21	2480 bit/s
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Stable, Exit	4.6 Mbit/s \| 816.0 Kbit/s	4.6 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	59.2% \| 98%	12.5d \| 8d	3.6d \| 3.1d	4.6d \| 8.5d	59.2% \| 98.0%	12.5d \| 1.0d	2026-09-20 09:24:21	616 bit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Running, Valid, Fast, Exit	4.6 Mbit/s \| 816.0 Kbit/s	4.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	59.9% \| 98%	12.7d \| 8d	3.7d \| 11.6d	4.6d \| 8.4d	59.9% \| 98.0%	12.7d \| 1.0d	2026-09-20 09:24:21	4192 bit/s
faravahar (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Exit	4.6 Mbit/s \| 816.0 Kbit/s	4.6 Mbit/s \| 328.0 Mbit/s OR 16.0 Mbit/s	59.6% \| 98%	12.6d \| 8d	3.7d \| 13.0d	4.6d \| 9.1d	59.6% \| 98.0%	12.6d \| 1.0d	2026-09-20 09:24:21	4192 bit/s
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Exit	4.6 Mbit/s \| 816.0 Kbit/s	4.6 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	59.7% \| 98%	12.7d \| 8d	3.7d \| 12.1d	4.6d \| 8.5d	59.7% \| 98.0%	12.7d \| 1.0d	2026-09-20 09:24:21	720 bit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Fast, Exit	4.6 Mbit/s \| 816.0 Kbit/s	4.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	59.7% \| 98%	12.6d \| 8d	3.7d \| 13.2d	4.6d \| 8.5d	59.7% \| 98.0%	12.6d \| 1.0d	2026-09-20 09:24:21	4192 bit/s
maatuska (SE)	Yes	Yes	Yes	—	N	Yes	Running, Valid, Fast, Exit	4.6 Mbit/s \| 816.0 Kbit/s	4.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	60.7% \| 98%	12.4d \| 8d	3.7d \| 11.0d	4.6d \| 8.4d	60.7% \| 98.0%	12.4d \| 1.0d	2026-09-20 09:24:21	4192 bit/s
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Stable, Exit	4.6 Mbit/s \| 8.4 Mbit/s	4.6 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	60.0% \| 98%	9.5d \| 8d	10330.4d \| 8370.7d	4.6d \| 8.8d	60.0% \| 98.0%	9.5d \| 9.8d	2026-09-20 09:24:21	1920 bit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, Exit	4.6 Mbit/s \| 816.0 Kbit/s	4.6 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	59.7% \| 98%	12.6d \| 8d	3.7d \| 12.3d	4.6d \| 8.2d	59.7% \| 98.0%	12.6d \| 1.0d	2026-09-20 09:24:21	784 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.