JM TELECOM LTDA

Data as of 2026-08-30
BGP inherited
Cluster stats
Netblocks9 · 516 IPv4 addresses
IPv6 4 prefixes (largest 2001:12f8:0:10::226/128)
All fragments 21 blocks across 2 clusters
Cluster ID233786284
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

10 weekly snapshots · JSON
9 -8 netblocks since 2026-07-05
2026-07-05 peak 17 2026-08-30

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.74.103/32 JM TELECOM LTDA PEERINGDB ASSIGNED ● high
45.227.1.56/32 JM TELECOM LTDA PEERINGDB ASSIGNED ● high
187.16.222.141/32 JM TELECOM LTDA PEERINGDB ASSIGNED ● high
200.219.147.226/32 JM TELECOM LTDA PEERINGDB ASSIGNED ● high
2001:12f8::222:141/128 JM TELECOM LTDA PEERINGDB ASSIGNED ● high
2001:12f8:0:9::146:103/128 JM TELECOM LTDA PEERINGDB ASSIGNED ● high
2001:12f8:0:10::226/128 JM TELECOM LTDA PEERINGDB ASSIGNED ● high
2001:12f8:0:31::56/128 JM TELECOM LTDA PEERINGDB ASSIGNED ● high
45.164.202.0/23 JM TELECOM LTDA ARIN ALLOCATED ● low

IPv6 ranges (4)

CIDR
2001:12f8:0:10::226/128
2001:12f8:0:31::56/128
2001:12f8:0:9::146:103/128
2001:12f8::222:141/128

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (9 of 9)
Possible discrepancies (1)

These blocks are registered to JM TELECOM LTDA 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.

45.164.202.0/23 /23 authorized for AS272174 — AS272174

NIC Handles

26773682000169 AS272174 JAVSI86 JOFSI1022 JOFSI1022