JM TELECOM LTDA
BGP inherited
Cluster stats
| Netblocks | 8 |
| All fragments | 20 blocks across 2 clusters |
| Cluster ID | 207724934 |
| Registry | PEERINGDB |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 | |
Footprint over time
4 weekly snapshots · JSON
8
-9 netblocks since 2026-07-05
2026-07-05
peak 17
2026-07-13
IP Ranges (8)
⬇ 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 |
Possibly related to this organisation
what's this?Same name family
Separately-registered clusters whose names share “JM TELECOM” — often
per-country or per-system registrations of the same brand, occasionally a different
organisation sharing the name. Not counted in this organisation's own footprint.
- JM-TELECOM 12 blocks
Sub-allocations under carriers
IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own
naming convention, not a direct registration.
- JSC "CREDO-TELECOM" sub-allocation
- JSC "CREDO-TELECOM" sub-allocation
- JSC "CREDO-TELECOM" sub-allocation
- JSC "CREDO-TELECOM" sub-allocation
- JSC "CREDO-TELECOM" sub-allocation
- JSC "CREDO-TELECOM" sub-allocation
- JSC "CREDO-TELECOM" sub-allocation
- JSC "CREDO-TELECOM" sub-allocation
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(8 of 8)
No discrepancies found among checked blocks.
NIC Handles
AS272174