JM-Networks, s.r.o.
JMNET
BGP inherited
Cluster stats
| Netblocks | 4 |
| Cluster ID | 205149073 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 7 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 119.226.60.80/28 | JMNET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 124.30.133.208 – 124.30.133.219 | JMNET | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 185.47.220.0 – 185.47.222.255 | JMNET | RIPE | ASSIGNED PA | ● low |
| 185.47.223.0/24 | JMNET | RIPE | ASSIGNED PA | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to JMNET 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.
| 185.47.220.0 – 185.47.222.255 /22 | authorized for AS62099 — JM-Networks, s.r.o. |
| 185.47.223.0/24 /24 | authorized for AS62099 — JM-Networks, s.r.o. |
NIC Handles
DUMY-RIPE
DUMY-RIPE
HS51-AP
HS51-AP
MAINT-IN-IRINN
MAINT-IN-SIFY
MNT-JMNET