LTC Connect
Cluster stats
Netblocks16
All fragments 54 blocks across 10 clusters
Cluster ID191605295
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution unresolved
Shared handles clustered on 12 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (16)

⬇ export CSV
CIDR Org name Registry Status Confidence
66.38.6.0/23 LTC Connect BGP ANNOUNCED ● high
66.38.20.0/22 LTC Connect BGP ANNOUNCED ● high
66.38.24.0/22 LTC Connect BGP ANNOUNCED ● high
66.38.27.0/24 LTC Connect BGP ANNOUNCED ● high
66.38.28.0/24 LTC Connect BGP ANNOUNCED ● high
66.38.63.0/24 LTC Connect BGP ANNOUNCED ● high
66.38.82.0/24 LTC Connect BGP ANNOUNCED ● high
74.50.32.0/21 LTC Connect BGP ANNOUNCED ● high
74.50.32.0/21 LTC Connect ARIN ● high
74.50.47.0/24 LTC Connect BGP ANNOUNCED ● high
116.12.142.152/29 LTC-SG APNIC ASSIGNED NON-PORTABLE ● high
119.73.210.112/28 LTC-SG APNIC ASSIGNED NON-PORTABLE ● high
209.46.24.0/22 LTC Connect BGP ANNOUNCED ● high
209.46.96.0/22 LTC Connect BGP ANNOUNCED ● high
210.12.58.0/24 LTC-CN APNIC ASSIGNED NON-PORTABLE ● high
216.245.148.0/22 LTC Connect BGP ANNOUNCED ● high

Network trust

what's this?
RPKI hygiene: F how networks compare →
18.8% of checked blocks have valid RPKI ROA coverage (3 of 16)
Possible discrepancies (1)

These blocks are registered to LTC Connect 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.

210.12.58.0/24 /24 authorized for AS4808 — China Unicom

NIC Handles

AS400589 KP235-AP LTC-128 MAINT-CHINAGBN-AP MAINT-SG-SINGNET NETWO9151-ARIN NETWO9151-ARIN NETWO9151-ARIN NZW1-AP SH9-AP WT44-AP WT44-AP