View Relay "prxMiddle01"

Fingerprint: 0827E92E2236BC197663BCA9D0634C4A5C149ECD | Family: 1 relay | mch5600tor-relay@yahoo.com | AS6810 | Israel | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
6/6 BW Auths Measured 2480 bit/s Median
Stability
Overloaded | UP 2d 21h 6m ago | UP 61% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1mo 2w 5d ago
BW Weight
0.00% of Network | 5 Mbit/s Observed By Relay
Version
0.4.9.5 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: bandwidth below threshold : Observed bandwidth 0.7 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 52.3% 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 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 52.3% 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 (5 Mbit/s) was hit 48 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 (5 Mbit/s) was hit 57 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=5 Mbit/s, Burst=10 Mbit/s. Limits hit: Write=48, Read=57.

Connectivity and Location

Addresses
OR Address
bzq-109-67-142-70.red.bezeqint.net
109.67.142.70:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Israel Israel
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS6810
AS Name
"Bezeq"- THE ISRAEL TELECOMMUNICATION CORP. LTD. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/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) 5.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 (1/9 DA) Median: 4.1d (1/9 DA above threshold)
Min/Max: 2.4d / 8168.3d (9/9 DA, Voting / Total Eligible)		 ≥17.9d - 58.6d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 2.9d (R) ≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (7/9 DA) 7/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 ≥17.9d - 58.6d (varies) (≥5/9 DA)
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: 52.4% (0/9 DA above threshold)
Min/Max: 51.3% / 54.1% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 13.0d (9/9 DA above threshold)
Min/Max: 9.9d / 13.2d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (7/9 DA) 7/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 ≥17.9d - 58.6d (varies) (≥5/9 DA)
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: 52.4% (0/9 DA above threshold)
Min/Max: 51.3% / 54.1% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 13.0d (9/9 DA above threshold)
Min/Max: 9.9d / 13.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 5.6 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 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-03-29 11:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
5.59 Mbit/s
Advertised Bandwidth
5.24 Mbit/s
Rate Limit
5.24 Mbit/s
Burst Limit
10.49 Mbit/s
Total Data
116 GB (6 months)
1mo: 98 GB | 6mo: 116 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 11:15:07

Measured By
6/6 Bandwidth Authorities
Median Measurement
2480 bit/s
Min / Max
800 bit/s / 5240 bit/s
Deviation
4440 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (7th pctl) | Guard: N/A | Middle: 0.0003% (7th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 21h 6m ago
Overall Uptime (1M/6M/1Y/5Y)
61.2%/55.6%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
56.0%/48.1%/—/—
Hibernating
No
Timestamps
First Seen
1mo 2w 5d ago (2026-02-07 13:00:00)
Last Seen
2h 15m 38s ago (2026-03-29 09:00:00)
Last Restarted
2d 21h 6m ago (2026-03-26 14:09:07)
Last Changed Address
2026-02-07 13:00:00
[Warning] OVERLOADED — Rate limits hit W:48 R:57 (limit: 5 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
5.24 Mbit/s
Burst Limit
10.49 Mbit/s
Write Limit Hit
48 times
Read Limit Hit
57 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-03-29 04:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
mch5600tor-relay@yahoo.com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
0827E92E2236BC197663BCA9D0634C4A5C149ECD (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
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 Sun, 29 Mar 2026 11:15:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 11:15:07).

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, Fast 5.6 Mbit/s | 816.0 Kbit/s 5.6 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 52.3% | 98% 13.1d | 8d 4.1d | 63.4d 2.9d | 3.3d 52.3% | 98.0% 13.1d | 1.0d 2026-03-28 21:09:12 2560 bit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 5.6 Mbit/s | 816.0 Kbit/s 5.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 51.3% | 98% 13.0d | 8d 2.4d | 17.9d 2.9d | 3.3d 51.3% | 98.0% 13.0d | 1.0d 2026-03-28 21:09:12 5240 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 5.6 Mbit/s | 816.0 Kbit/s 5.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 51.7% | 98% 12.3d | 8d 3.8d | 42.9d 2.9d | 3.4d 51.7% | 98.0% 12.3d | 1.0d 2026-03-28 21:09:12 5240 bit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 5.6 Mbit/s | 816.0 Kbit/s 5.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 52.4% | 98% 13.1d | 8d 4.1d | 56.4d 2.9d | 3.4d 52.4% | 98.0% 13.1d | 1.0d 2026-03-28 21:09:12 5240 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 5.6 Mbit/s | 816.0 Kbit/s 5.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 52.4% | 98% 13.1d | 8d 4.2d | 62.1d 2.9d | 3.4d 52.4% | 98.0% 13.1d | 1.0d 2026-03-28 21:09:12 800 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 5.6 Mbit/s | 816.0 Kbit/s 5.6 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 54.1% | 98% 12.7d | 8d 4.1d | 62.6d 2.9d | 3.3d 54.1% | 98.0% 12.7d | 1.0d 2026-03-28 21:09:12 2160 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 5.6 Mbit/s | 816.0 Kbit/s 5.6 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 52.6% | 98% 13.2d | 8d 4.2d | 50.7d 2.9d | 3.3d 52.6% | 98.0% 13.2d | 1.0d 2026-03-28 21:09:12 1520 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 5.6 Mbit/s | 8.4 Mbit/s 5.6 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 52.5% | 98% 9.9d | 8d 8168.3d | 291.4d 2.9d | 4.1d 52.5% | 98.0% 9.86d | 9.90d 2026-03-28 21:09:12 2480 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 5.6 Mbit/s | 816.0 Kbit/s 5.6 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 53.4% | 98% 12.8d | 8d 4.2d | 58.6d 2.9d | 3.9d 53.4% | 98.0% 12.8d | 1.0d 2026-03-28 21:09:12 880 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.