VITEBSK-VITVAR

BGP inherited
Cluster stats
Netblocks8
Cluster ID209935806
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
82.209.207.20/32 VITEBSK-VITVAR RIPE ASSIGNED PA ● low
82.209.207.21/32 VITEBSK-VITVAR RIPE ASSIGNED PA ● low
82.209.207.116/32 VITEBSK-VITVAR RIPE ASSIGNED PA ● low
82.209.207.172/32 VITEBSK-VITVAR RIPE ASSIGNED PA ● low
82.209.227.26/32 VITEBSK-VITVAR RIPE ASSIGNED PA ● low
82.209.227.153/32 VITEBSK-VITVAR RIPE ASSIGNED PA ● low
86.57.182.42/32 VITEBSK-VITVAR RIPE ASSIGNED PA ● low
86.57.183.46/32 VITEBSK-VITVAR RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE VITEBSKOBLTELECOM-MNT