Lan-Telecom

Handle
Cluster stats
Netblocks8
Registered in Ukraine (7) · Poland (1)
All fragments 14 blocks across 2 clusters
Cluster ID208805132
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution RIR handle
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

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
185.0.29.11/32 Lan-Telecom PEERINGDB ASSIGNED ● high
185.0.42.190/32 Lan-Telecom PEERINGDB ASSIGNED ● high
185.1.62.162/32 Lan-Telecom PEERINGDB ASSIGNED ● high
185.1.85.12/32 Lan-Telecom PEERINGDB ASSIGNED ● high
185.1.196.33/32 Lan-Telecom PEERINGDB ASSIGNED ● high
185.1.213.190/32 Lan-Telecom PEERINGDB ASSIGNED ● high
193.25.180.203/32 Lan-Telecom PEERINGDB ASSIGNED ● high
193.34.196.156/32 Lan-Telecom PEERINGDB ASSIGNED ● high

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “Lan 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.
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.

NIC Handles

AS31633