View Relay "phin"
Fingerprint: E489C5F18B2E266AEC0BDA5A42466DBAB0E9B64E |
Family: 1 relay
|
email:tor@child.pizza |
AS214677
|
Netherlands
|
Linux
- Consensus
- In Consensus (8/9 Directory Auths)
- DNS Health
- Healthy (16.8s, 57th percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/6 BW Auths Measured 8 bit/s Median
- Stability
- Not Overloaded | UP 1d 17h 4m ago | UP 4% (1M)
- Reachability
- IPv4: 8/9 | v6: 7/8 (Directory Auths)
- BW Weight
- 0.00% of Network | 53 Mbit/s Observed By Relay
- Version
- 0.4.8.17 Not 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.7 days is below 8 days requirement (6.3 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. -
Tor version not recommended
: Running Tor version 0.4.8.17 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
Notes:
- Partial IPv4 reachability: 8/9 authorities can reach this relay
Addresses
- OR Address
-
5.181.177.130:443
[2a12:bec4:1821:3a8::a]:443 - Exit Address
- 5.181.177.130
Reachability (Directory Authorities)
- IPv4
- 8/9
- IPv6
- 7/8 (1 don't test)
Location
- Country
-
Netherlands
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 3/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 8/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (8/9 DA) | 8/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Meets (7/8 DA) | 7/8 tested authorities reached relay | ≥5/8 tested (majority) (≥5/8 DA) | |
| Valid | Descriptor | Meets (8/9 DA) | 8/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (8/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Meets (9/9 DA) | 53.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 (0/9 DA) | Median: 1.7d (0/9 DA above threshold) Min/Max: 0.7d / 1.7d (8/9 DA, Voting / Total Eligible) |
≥38.3d - 62.2d (varies) (≥5/9 DA) |
| Uptime | Below (0/9 DA) | 1.7d (R) | ≥8.3d - 11.1d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (3/9 DA) | 3/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 | ≥38.3d - 62.2d (varies) (≥5/9 DA) | |
| Prereq: V2Dir | Meets (8/9 DA) | 8/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (8/9 DA) | Majority: 100.0% (8/9 DA) | ≥98.0% (≥5/9 DA) | |
| Time Known | Meets (6/9 DA) | Median: 1.7d (0/9 DA above threshold) Min/Max: 0.7d / 1.7d (8/9 DA, Voting / Total Eligible) |
≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d |
|
| Guard | Prereq: Fast | Below (3/9 DA) | 3/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 | ≥38.3d - 62.2d (varies) (≥5/9 DA) | |
| Prereq: V2Dir | Meets (8/9 DA) | 8/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (8/9 DA) | Majority: 100.0% (8/9 DA) | ≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) (need 6.3 more days) | Median: 1.7d (0/9 DA above threshold) Min/Max: 0.7d / 1.7d (8/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 53.9 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.0 Mbit/s (≥5/9 DA) | |
| Exit | Exit Policy | Meets (8/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-04-20 10:15:08).
Capacity (Relay Reported)
- Observed Bandwidth
- 53.87 Mbit/s
- Advertised Bandwidth
- 53.87 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
34 TB
(1 year)
1mo: 5.2 GB | 6mo: 5.2 GB | 1y: 34 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-04-20 10:15:08
- Measured By
-
5/6
Bandwidth Authorities
Not measured by: bastet - Median Measurement
- 8.0 bit/s
- Min / Max
- 8 bit/s / 53.9 Kbit/s
- Deviation
- 53.9 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 Metrics
- Current Status
- UP 1d 17h 4m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 4.0%/0.0%/11.4%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (4.0%/0.0%/11.4%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 1d 16h 46m ago (2026-04-18 18:00:00)
- Last Seen
- 1h 46m 39s ago (2026-04-20 09:00:00)
- Last Restarted
- 1d 17h 4m ago (2026-04-18 17:42:00)
- Last Changed Address
- 2026-04-18 18:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-04-20 03:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- email:tor@child.pizza
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
E489C5F18B2E266AEC0BDA5A42466DBAB0E9B64E (this relay)
- Alleged Members: 2
-
(they don't list you back)
8472F6E22A84DEE0807A181074E4110E34E540F8 8BED59DCB0F3F91117F4B139F41DCF17E00F7EC9
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.8.17 on Linux
- Version
- 0.4.8.17 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
- Status
- Healthy (avg. 16.8s, 57th percentile)
- Query Domain
c96f8c73d4f74608a171c00fd96d479b.e489c5f1.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Cross-Validation
- 4/4 instances succeeded
- First Hop
- ParadiseTorRelay2 (SE) AA1A48643697DAF18AF63294989FE48CC5CC49C4
- Exit Address Used
5.181.177.130- Per-Instance Results
-
Cross Validation Attempt 1: Success, 15.6s (cv1_w4) Cross Validation Attempt 2: Success, 10.8s (cv2_w4) Cross Validation Attempt 3: Success, 27.0s (cv3_w4) Cross Validation Attempt 4: Success, 13.6s (cv4_w4)
Tested: 2026-04-20 07:17:05 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 1-65535
IPv6 Exit Policy Summary
NoneFull 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 5.181.177.130:* accept *:*
Last fetch was at Mon, 20 Apr 2026 10:46:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-04-20 10:15:08).
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) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — | — | — |
| dannenberg (DE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 53.9 Mbit/s | 816.0 Kbit/s | 53.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 1.7d | 8d | 1.7d | 38.3d | 1.7d | 11.1d | 100.0% | 98.0% | 1.7d | 1.0d | 2026-04-20 05:42:45 | 53.9 Kbit/s |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 53.9 Mbit/s | 816.0 Kbit/s | 53.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 1.7d | 8d | 1.7d | 40.3d | 1.7d | 11.1d | 100.0% | 98.0% | 1.7d | 1.0d | 2026-04-20 05:42:45 | 53.9 Kbit/s |
| faravahar (US) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 53.9 Mbit/s | 816.0 Kbit/s | 53.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 1.7d | 8d | 1.7d | 61.2d | 1.7d | 11.1d | 100.0% | 98.0% | 1.7d | 1.0d | 2026-04-20 05:42:45 | 53.9 Kbit/s |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 53.9 Mbit/s | 816.0 Kbit/s | 53.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 1.7d | 8d | 1.7d | 63.0d | 1.7d | 11.1d | 100.0% | 98.0% | 1.7d | 1.0d | 2026-04-20 05:42:45 | 8 bit/s |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | — | Running, Valid, V2Dir, Exit | 53.9 Mbit/s | 816.0 Kbit/s | 53.9 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 1.7d | 8d | 1.7d | 62.3d | 1.7d | 11.1d | 100.0% | 98.0% | 1.7d | 1.0d | 2026-04-20 05:42:45 | 8 bit/s |
| maatuska (SE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 53.9 Mbit/s | 816.0 Kbit/s | 53.9 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 0.7d | 8d | 0.7d | 61.4d | 1.7d | 10.2d | 100.0% | 98.0% | 0.7d | 1.0d | 2026-04-18 17:42:40 | 8 bit/s |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 53.9 Mbit/s | 8.4 Mbit/s | 53.9 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 1.4d | 8d | 1.5d | 303.7d | 1.7d | 11.0d | 100.0% | 98.0% | 1.4d | 9.9d | 2026-04-20 05:42:45 | 8 bit/s |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Exit | 53.9 Mbit/s | 816.0 Kbit/s | 53.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 1.7d | 8d | 1.7d | 63.2d | 1.7d | 11.1d | 100.0% | 98.0% | 1.7d | 1.0d | 2026-04-20 05:42:45 | 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.
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.