Connect LP

Data as of 2026-08-09
BGP inherited
Cluster stats
Netblocks8
IPv6 4 prefixes (largest 2001:12f8:0:6::27:2549/128)
All fragments 9 blocks across 2 clusters
Cluster ID221219629
RegistryPEERINGDB
Customersfind 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 · report an issue

Footprint over time

2 weekly snapshots · JSON
8 0 netblocks since 2026-07-26
2026-07-26 peak 8 2026-08-09

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
177.52.38.196/32 Connect LP PEERINGDB ASSIGNED ● high
187.16.211.210/32 Connect LP PEERINGDB ASSIGNED ● high
187.16.214.199/32 Connect LP PEERINGDB ASSIGNED ● high
187.16.215.78/32 Connect LP PEERINGDB ASSIGNED ● high
2001:12f8::211:210/128 Connect LP PEERINGDB ASSIGNED ● high
2001:12f8::214:199/128 Connect LP PEERINGDB ASSIGNED ● high
2001:12f8::215:78/128 Connect LP PEERINGDB ASSIGNED ● high
2001:12f8:0:6::27:2549/128 Connect LP PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

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

AS272549