BOLNISABOLASHA

BGP inherited
Cluster stats
Netblocks10
Cluster ID210629689
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
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-07-19

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
92.46.249.204/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
95.59.25.200/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
95.59.27.76/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
95.59.29.76/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
95.59.29.152/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
95.59.29.156/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
95.59.29.160/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
95.59.29.164/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
185.35.17.120/30 BOLNISABOLASHA RIPE ASSIGNED PA ● low
185.35.17.124/30 BOLNISABOLASHA 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 (10 of 10)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT