WesCom LLC

BGP inherited
Cluster stats
Netblocks6 · 1,029 IPv4 addresses
Registered in Russia (2) · Germany (1) · Hong Kong (1)
All fragments 13 blocks across 3 clusters
Cluster ID205306326
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 11 shared RIR contact/maintainer handles
Registry names 4 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
193.33.10.0/23 WesCom LLC RIPE ASSIGNED PI ● high
193.33.10.0/23 WesCom LLC BGP ANNOUNCED ● high
59.148.224.61/32 WESCOM APNIC ASSIGNED NON-PORTABLE ● low
148.251.221.224/29 WESCOM-GMBH RIPE LEGACY ● low
2a01:4f8:212:55b::/64 WESCOM-GMBH RIPE ASSIGNED ● low
2a01:4f9:4b:1bb1::/64 WESCOM-GMBH RIPE ASSIGNED ● low

Possibly related to this organisation

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

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (3 of 6)
No discrepancies found among checked blocks.

NIC Handles

AS42247 CH134-AP DUMY-RIPE DUMY-RIPE HOS-GUN MAINT-HK-CTI ORG-VL30-RIPE RIPE-NCC-END-MNT SL113-AP WESCOM-MNT WESCOM-MNT