JMC
Cluster stats
Netblocks12
All fragments 34 blocks across 10 clusters
Cluster ID191925901
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 5 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
61.49.17.64/27 JMC-CO APNIC ASSIGNED NON-PORTABLE ● high
176.94.171.0/24 JMC-NET RIPE ASSIGNED PA ● low
176.95.31.136/29 JMC-NET RIPE ASSIGNED PA ● low
188.111.54.192/29 JMC-NET RIPE ASSIGNED PA ● low
194.165.143.192/28 JMC RIPE ASSIGNED PA ● low
194.165.148.248/29 JMC RIPE ASSIGNED PA ● low
194.165.149.144/28 JMC RIPE ASSIGNED PA ● low
194.165.153.120/29 JMC RIPE ASSIGNED PA ● low
194.165.153.252/30 JMC RIPE ASSIGNED PA ● low
213.47.217.152/29 JMC-GmbH RIPE ASSIGNED PA ● low
213.186.167.248/30 JMC RIPE ASSIGNED PA ● low
220.245.189.104/29 JMC_PTY_LTD APNIC ASSIGNED NON-PORTABLE ● low

Network trust

what's this?
RPKI hygiene: B how networks compare →
91.7% of checked blocks have valid RPKI ROA coverage (11 of 12)
Possible discrepancies (1)

These blocks are registered to JMC 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.

176.94.171.0/24 /24 authorized for AS3209 — Vodafone GmbH

NIC Handles

ARCOR-MNT DL985-AP DL985-AP DUMY-RIPE DUMY-RIPE GO-JOR MAINT-AU-TPGCOM MAINT-CNCGROUP-BJ PRIO-MNT TH178-AP TH178-AP