View Relay "memcpy4"
Fingerprint: 7D15E51CC8AE6167EBDDC595CFA255E5667D881A |
Operator: memcpy.io v2
(1 relay)
⚠ Misconfigured
|
Family: 1 relay
|
email:tor[]memcpy.io... |
AS24940
|
Finland
|
Linux
- Consensus
- Not In Consensus (1/9 Directory Auths, need 5)
- BW Verified
- 1/7 BW Auths Measured 48 Kbit/s Median
- Stability
- Not Overloaded | DOWN 23h 7m 2s ago | UP 57% (1M)
- Reachability
- IPv4: 1/9 | v6: 1/9 (Directory Auths)
- BW Weight
- 0.00% of Network | 45 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not in consensus
: Only 1/9 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: dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1, 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. -
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 30.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. -
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 30.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/7 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.
Addresses
- OR Address
-
box4.memcpy.io
95.217.104.226:8081
[2a01:4f9:4a:264d::2]:8081
Reachability (Directory Authorities)
- IPv4
- 1/9
- IPv6
- 1/9
Location
- Country
-
Finland
- Interactive Map
- View in RouteFluxMap
Eligible Flags (0):
Running: 1/9 | Valid: 1/9 | V2Dir: 1/9 | Fast: 1/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Below (1/9 DA) | 1/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Partial (1/9 DA) | 1/9 tested authorities reached relay | ≥5/9 tested (majority) (≥5/9 DA) | |
| Valid | Descriptor | Partial (1/9 DA) | 1/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (1/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Meets (9/9 DA) | 46.0 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.2d (0/9 DA above threshold) | ≥3.2d - 11.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥6577.2d |
| Uptime | Below (0/9 DA) | 2.4d (R) | ≥3.3d - 3.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (1/9 DA) | 1/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 | ≥3.2d - 11.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥6577.2d |
|
| Prereq: V2Dir | Below (1/9 DA) | 1/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 30.2% (0/9 DA above threshold) | ≥98.0% (≥5/9 DA) | |
| Time Known | Below (1/9 DA) | Median: 15.1d (1/9 DA above threshold) | ≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d |
|
| Guard | Prereq: Fast | Below (1/9 DA) | 1/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 | ≥3.2d - 11.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥6577.2d |
|
| Prereq: V2Dir | Below (1/9 DA) | 1/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 30.2% (0/9 DA above threshold) | ≥98% (≥5/9 DA) | |
| Time Known | Meets (1/9 DA) | Median: 15.1d (1/9 DA above threshold) | ≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 46.0 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-280.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-11-08 08:01:41).
Capacity (Relay Reported)
- Observed Bandwidth
- 45.97 Mbit/s
- Advertised Bandwidth
- 45.97 Mbit/s
- Rate Limit
- 645.92 Mbit/s
- Burst Limit
- 687.87 Mbit/s
- Total Data
- 1.7 TB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-08 08:01:41
- Measured By
-
1/7
Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Median Measurement
- 48.0 Kbit/s
- Min / Max
- 48.0 Kbit/s / 48.0 Kbit/s
Network Participation:
Consensus Weight:
0.0034% of network
(43th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
Uptime Metrics
- Current Status
- DOWN 23h 7m 2s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 57.4%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- 53.6%/—/—/—
- Hibernating
- No
Timestamps
- First Seen
- 2w 5d 13h ago (2026-10-19 19:00:00)
- Last Seen
- 23h 7m 2s ago (2026-11-07 09:00:00)
- Last Restarted
- 2d 8h 47m ago (2026-11-05 23:19:11)
- Last Changed Address
- 2026-10-19 19:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-11-07 23:00 UTC
- AROI Domain (?)
- memcpy.io
- Operator Validation
- Unvalidated
- This Relay
-
Unvalidated
Error: URI-RSA: HTTP error 404 for memcpy.io at URL: https://memcpy.io/.well-known/tor-relay/rsa-fingerprint.txt; URI-RSA: HTTP redirect (301) to http://memcpy.io/.well-known/tor-relay/rsa-fingerprint.txt for www.memcpy.io at URL: https://www.memcpy.io/.well-known/tor-relay/rsa-fingerprint.txt — CIISS spec disallows redirects on proof URI - Contact
- email:tor[]memcpy.io url:http://memcpy.io proof:uri-rsa abuse:tor[]memcpy.io pgp:5EB426794D2AB10BBE5D0C90FC974D585706DA43 matrix:@robertfoss:matrix.org hoster:Hetzner cost:35USD uplinkbw:2000 autoupdate:y ciissversion:2 trafficacct:unmetered
Family Configuration
- Family Support
- MyFamily Only (1) — Legacy only. Consider migrating to Happy Families.
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
7D15E51CC8AE6167EBDDC595CFA255E5667D881A (this relay)
- Alleged Members: 2
-
(they don't list you back)
971DDE3C3E8AC4D424E541C454F359F1C776AAC8 B8D45E58E35F62201B906EC927795D33649AC10D
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Sun, 08 Nov 2026 08:06:52 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-08 08:01:41).
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) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast | 46.0 Mbit/s | 816.0 Kbit/s | 46.0 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s | 30.2% | 98% | 15.1d | 8d | 1.2d | 9.7d | 2.4d | 5.7d | 30.2% | 98.0% | 15.1d | 1.0d | 2026-11-05 23:19:24 | 48.0 Kbit/s |
| dannenberg (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| dizum (NL) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — | — | — |
| faravahar (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| longclaw (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| maatuska (SE) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — | — | — |
| moria1 (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| 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.
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.
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.