VTB24

BGP inherited
Cluster stats
Netblocks8
All fragments 43 blocks across 17 clusters
Cluster ID209447693
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 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
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
81.1.237.96/29 VTB24 RIPE ASSIGNED PA ● low
82.208.110.168/29 VTB24 RIPE ASSIGNED PA ● low
95.167.76.120/29 VTB24 RIPE ASSIGNED PA ● low
188.247.38.0/27 vtb24_net RIPE ASSIGNED PA ● low
188.247.39.120/29 vtb24_net RIPE ASSIGNED PA ● low
188.247.39.128/27 vtb24_net RIPE ASSIGNED PA ● low
195.144.214.192/29 VTB24-NET RIPE ASSIGNED PA ● low
213.150.80.48/29 vtb24-net RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “VTB24” — 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.
Combined view of all 17 name-family clusters →
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 →
75.0% of checked blocks have valid RPKI ROA coverage (6 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE ROSTELECOM-MNT SAMTEL-MNT SOVINTEL-MNT TOTCOM-MNT UNICO-MNT ZSTTK-MNT