JM TELECOM LTDA
Cluster stats
| Netblocks | 17 |
| All fragments | 29 blocks across 2 clusters |
| Cluster ID | 191314657 |
| Registry | BGP |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 2 shared RIR contact/maintainer handles |
| Registry names | 3 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.68.74.103/32 | JM TELECOM LTDA | PEERINGDB | ASSIGNED | ● high |
| 45.164.202.0/23 | JM TELECOM LTDA | BGP | ANNOUNCED | ● high |
| 45.164.202.0/24 | JM TELECOM LTDA | BGP | ANNOUNCED | ● high |
| 45.164.203.0/24 | JM TELECOM LTDA | BGP | ANNOUNCED | ● 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 |
| 2804:8310::/33 | JM TELECOM LTDA | BGP | ANNOUNCED | ● high |
| 2804:8310::/32 | JM TELECOM LTDA | BGP | ANNOUNCED | ● high |
| 2804:8310:8000::/33 | JM TELECOM LTDA | BGP | ANNOUNCED | ● high |
| 45.164.203.192/27 | UNKNOWN | LACNIC | reassigned | ● medium |
| 45.164.203.224/28 | UNKNOWN | LACNIC | reassigned | ● medium |
| 2804:8310::/32 | UNKNOWN | LACNIC | allocated | ● medium |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(17 of 17)
No discrepancies found among checked blocks.
NIC Handles
AS272174
AS272174