JMF Networks
Cluster stats
Netblocks12
All fragments 41 blocks across 4 clusters
Cluster ID193384316
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (12)

⬇ export CSV
CIDR Org name Registry Status Confidence
80.249.208.8/32 JMF Networks PEERINGDB ASSIGNED ● high
206.53.143.88/32 JMF Networks PEERINGDB ASSIGNED ● high
206.53.169.140/32 JMF Networks PEERINGDB ASSIGNED ● high
206.53.170.21/32 JMF Networks PEERINGDB ASSIGNED ● high
206.53.200.41/32 JMF Networks PEERINGDB ASSIGNED ● high
206.71.12.19/32 JMF Networks PEERINGDB ASSIGNED ● high
2001:504:40:12::1:19/128 JMF Networks PEERINGDB ASSIGNED ● high
2001:504:47::9f65:0:1/128 JMF Networks PEERINGDB ASSIGNED ● high
2001:504:59::41/128 JMF Networks PEERINGDB ASSIGNED ● high
2001:7f8:1::a504:805:1/128 JMF Networks PEERINGDB ASSIGNED ● high
2606:a980:0:3::15/128 JMF Networks PEERINGDB ASSIGNED ● high
2606:a980:0:a::c/128 JMF Networks PEERINGDB ASSIGNED ● high

Network trust

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

NIC Handles

AS40805