TELECABLE RESIDENCIAL
Data as of 2026-08-09
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 512 IPv4 addresses |
| Cluster ID | 219775949 |
| Registry | LACNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 8 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 170.150.56.0/25 | TELECABLE RESIDENCIAL | LACNIC | REALLOCATED | ● low |
| 170.246.156.0/25 | TELECABLE RESIDENCIAL | LACNIC | REALLOCATED | ● low |
| 177.93.0.0/24 | TELECABLE RESIDENCIAL | LACNIC | REALLOCATED | ● low |
Domains hosted in this network
what's this?Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to TELECABLE RESIDENCIAL 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.
| 177.93.0.0/24 /24 | authorized for AS52263 — AS52263 |
NIC Handles
CCL224
CCL224
CR-TERE-LACNIC
CR-TERE-LACNIC
JCM11
JCM11
JCM11
JCM11