VCOM-SOLUTIONS

VCOM-SOLUTIONS-GTT
BGP inherited
Cluster stats
Netblocks8
All fragments 12 blocks across 4 clusters
Cluster ID210072105
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 shared RIR contact/maintainer handles
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
77.77.158.56/29 VCOM-SOLUTIONS-GTT RIPE ASSIGNED PA ● low
87.119.101.176/29 VCOM-SOLUTIONS-GTT RIPE ASSIGNED PA ● low
154.14.82.120/29 VCOM-SOLUTIONS-GTT RIPE LEGACY ● low
154.14.184.208/29 VCOM-SOLUTIONS-GTT RIPE LEGACY ● low
154.14.214.48/28 VCOM-SOLUTIONS-GTT RIPE LEGACY ● low
154.14.214.64/28 VCOM-SOLUTIONS-GTT RIPE LEGACY ● low
154.14.254.8/29 VCOM-SOLUTIONS-GTT RIPE LEGACY ● low
212.222.20.152/29 VCOM-SOLUTIONS-GTT RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “VCOM SOLUTIONS” — 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: D how networks compare →
37.5% of checked blocks have valid RPKI ROA coverage (3 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS3257-IPAM-MNT DUMY-RIPE DUMY-RIPE