Muilties Network
Cluster stats
| Netblocks | 41 |
| Cluster ID | 191481003 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 12 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
41
0 netblocks since 2026-07-05
2026-07-05
peak 41
2026-07-06
IP Ranges (41)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.158.187.68/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 149.112.50.56/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 149.112.98.16/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 185.0.30.68/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 185.1.125.234/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 185.1.147.120/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 185.1.160.58/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 185.1.167.142/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 185.1.222.219/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 185.1.240.185/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 193.239.119.31/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 203.163.222.44/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 206.81.82.16/32 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16::3:2211/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:16:1::3:2211/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:504:125:e1::56/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:13::a520:5329:1/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:b7::a520:5329:1/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:ca:1::120/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:d0::3:2211:1/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:f2:e1:0:20:5329:1/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:10f::3:2211:58/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:11c:1:0:20:5329:1/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:7f8:12a::185/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2001:ded:c000::20/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2404:f4c0:f70e:1980::205:329/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2406:840:1f:1000:0:20:5329:1/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2406:d400:1:133:203:163:222:44/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2602:f9f6:7f0:5:0:20:5329:1/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2a0f:5707:ffe3::68/128 | Muilties Network | PEERINGDB | ASSIGNED | ● high |
| 2a0c:9a40:8440::/48 | Muilties_Network_Internal_Use | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8441::/48 | Muilties_Network_HongKong_01 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8442::/48 | Muilties_Network_Tokyo_01 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8443::/48 | Muilties_Network_Frankfurt_01 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8444::/48 | Muilties_Network_Kansas_01 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8445::/48 | Muilties_Network_Fremont_01 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8446::/48 | Muilties_Network_Toronto_01 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8447::/48 | Muilties_Network_Amsterdam_01 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8448::/48 | Muilties_Network_Amsterdam_02 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:8449::/48 | Muilties_Network_Taiwan_01 | RIPE | ASSIGNED | ● low |
| 2a0c:9a40:844a::/48 | Muilties_Network_Manchester_01 | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
78.0%
of checked blocks have valid RPKI ROA coverage
(32 of 41)
Possible discrepancies (11)
These blocks are registered to Muilties Network but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a0c:9a40:8440::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8442::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8441::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8443::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8444::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8445::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8446::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8447::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8448::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:8449::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
| 2a0c:9a40:844a::/48 /48 | authorized for AS205329 — Kai-Jung Chen |
NIC Handles
AS205329
DUMY-RIPE
DUMY-RIPE
MUILTIES-MNT