JM-Net
BGP inherited
Cluster stats
Netblocks8
All fragments 417 blocks across 82 clusters
Cluster ID191803439
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-06

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.0.20.168/32 JM-Net PEERINGDB ASSIGNED ● high
185.0.20.169/32 JM-Net PEERINGDB ASSIGNED ● high
2001:7f8:7f::168/128 JM-Net PEERINGDB ASSIGNED ● high
2001:7f8:7f::169/128 JM-Net PEERINGDB ASSIGNED ● high
80.71.195.224/27 JM-NET-NET RIPE ASSIGNED PA ● low
212.247.0.160/27 SE-JM-NET RIPE ASSIGNED PA ● low
2001:6f0:3406::/48 JM-NET RIPE ASSIGNED ● low
2a14:67c2:841::/48 JM RIPE ASSIGNED ● low

Network trust

what's this?
RPKI hygiene: D how networks compare →
37.5% of checked blocks have valid RPKI ROA coverage (3 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS62099 DUMY-RIPE DUMY-RIPE MNT-EPTE SWIPNET-LIR-MNT TDC-SE-MNT TIANJIN-JIANRONGWANGLUO-MNT