UKRAINIAN-AMERICAN-SWISS LIMITED LIABILITY PARTNERSHIP KANCOM

KANCOM-NET
BGP inherited
Cluster stats
Netblocks1
All fragments 7 blocks across 7 clusters
Cluster ID208865479
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (1)

⬇ export CSV
CIDR Org name Registry Status Confidence
217.25.192.0/24 KANCOM-NET RIPE ASSIGNED PA ● medium

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “KANCOM” — 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.
  • VIKANCOM via TDC Holding A/S sub-allocation
  • Kancom Ether via UKRAINIAN-AMERICAN-SWISS LIMITED LIABILITY PARTNERSHIP "KANCOM" sub-allocation
  • KANCOM-IP-NETWORK via UKRAINIAN-AMERICAN-SWISS LIMITED LIABILITY PARTNERSHIP "KANCOM" sub-allocation
  • Kancom-clients-leased-line-net7 via UKRAINIAN-AMERICAN-SWISS LIMITED LIABILITY PARTNERSHIP "KANCOM" sub-allocation
  • KANCOM-LEASED-LINE-NET3 via UKRAINIAN-AMERICAN-SWISS LIMITED LIABILITY PARTNERSHIP "KANCOM" sub-allocation
  • KANCOM-PPPOE-STATIC-POOL via UKRAINIAN-AMERICAN-SWISS LIMITED LIABILITY PARTNERSHIP "KANCOM" sub-allocation
  • BALKANCOM-NET via Drustvo za telekomunikacije Orion telekom doo Beograd-Zemun sub-allocation

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (1 of 1)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KANC-RIPE KANCOM-MNT