UAB Balticum TV

BALTICUM-TV-VLN
BGP inherited
Cluster stats
Netblocks9 · 3,319 IPv4 addresses
All fragments 45 blocks across 9 clusters
Cluster ID209300838
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
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
86.100.240.0/22 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low
86.100.244.0/23 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low
86.100.246.0/24 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low
86.100.247.0/24 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low
86.100.248.0/24 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low
86.100.251.0/24 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low
86.100.252.0/24 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low
86.100.253.0/24 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low
86.100.254.0/24 BALTICUM-TV-VLN RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

BALTICUM-TV-MNT DUMY-RIPE DUMY-RIPE