View Relay "MP1G"

Fingerprint: E4E9E8CBB8B46FDD7F36BC0229493B43BDF4D017 | Family: 1 relay | AS53667 | Luxembourg | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
6/6 BW Auths Measured 8 bit/s Median
Stability
Not Overloaded | UP 10h 47m 25s ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
10h 15m 40s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.8 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 0.4 days is below 8 days requirement (7.6 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.
  • HSDir: Time Known below threshold : Time Known 9.4 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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.

Connectivity and Location

Addresses
OR Address
104.244.76.121:9001
[2605:6400:30:f298::67]:9001
Exit Address
104.244.76.121
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Luxembourg Luxembourg
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS53667
AS Name
FranTech Solutions (BGP.tools)
AS Rarity
Emerging (score: 1/5, 1.99% consensus weight, 75 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
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 Below (0/9 DA) 8 bit/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: 0.4d (0/9 DA above threshold)
Min/Max: 0.4d / 0.4d (9/9 DA, Voting / Total Eligible)		 ≥19.7d - 51.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.3d
Uptime Below (0/9 DA) 0.4d (R) ≥6.6d - 6.6d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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 ≥19.7d - 51.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.4d (0/9 DA above threshold)
Min/Max: 0.4d / 0.4d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (0/9 DA) 0/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 ≥19.7d - 51.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.6 more days) Median: 0.4d (0/9 DA above threshold)
Min/Max: 0.4d / 0.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-336.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-05-14 22:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
838.86 Mbit/s
Burst Limit
4.19 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-14 22:45:07

Measured By
6/6 Bandwidth Authorities
Median Measurement
8 bit/s
Min / Max
0 bit/s / 8 bit/s
Deviation
8 bit/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 and Stability

Uptime Metrics
Current Status
UP 10h 47m 25s 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
10h 15m 40s ago (2026-05-14 13:00:00)
Last Seen
1h 15m 40s ago (2026-05-14 22:00:00)
Last Restarted
10h 47m 25s ago (2026-05-14 12:28:15)
Last Changed Address
2026-05-14 13:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-14 15:00 UTC

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

Software and Version

Platform
Linux — Tor 0.4.9.8 on Linux
Version
0.4.9.8 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  465
  587
  6660-6667
  6697
IPv6 Exit Policy Summary
reject: 
  25
  465
  587
  6660-6667
  6697
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 104.244.76.121:*
reject *:25
reject *:465
reject *:587
reject *:6660-6667
reject *:6697
accept *:*

Last fetch was at Thu, 14 May 2026 23:15:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-14 22:45: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 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 Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 51.0d 0.4d | 6.6d 100.0% | 98.0% 0.4d | 1.0d 2026-05-14 12:28:17 8 bit/s
dannenberg (DE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 49.9d 0.4d | 6.6d 100.0% | 98.0% 0.4d | 1.0d 2026-05-14 12:28:17 —
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 19.7d 0.4d | 6.6d 100.0% | 98.0% 0.4d | 1.0d 2026-05-14 12:28:17 —
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 51.8d 0.4d | 6.6d 100.0% | 98.0% 0.4d | 1.0d 2026-05-14 12:28:17 —
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 320.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 52.3d 0.4d | 6.6d 100.0% | 98.0% 0.4d | 1.0d 2026-05-14 12:28:17 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 256.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 58.6d 0.4d | 6.6d 100.0% | 98.0% 0.4d | 1.0d 2026-05-14 12:28:17 8 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 336.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 23.2d 0.4d | 6.6d 100.0% | 98.0% 0.4d | 1.0d 2026-05-14 12:28:17 8 bit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 328.3d 0.4d | 6.6d 100.0% | 98.0% 0.4d | 9.8d 2026-05-14 12:28:17 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.4d | 8d 0.4d | 55.0d 0.4d | 6.7d 100.0% | 98.0% 0.4d | 1.0d 2026-05-14 12:28:17 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.
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.