BUKVA

BGP inherited
Cluster stats
Netblocks9
Cluster ID210604014
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 6 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
85.195.88.174/31 BUKVA RIPE ASSIGNED PA ● high
85.195.92.156/30 BUKVA RIPE ASSIGNED PA ● high
85.195.100.112/31 BUKVA RIPE ASSIGNED PA ● high
92.42.104.216/29 BUKVA RIPE ASSIGNED PA ● high
134.119.179.8/29 BUKVA RIPE ASSIGNED PA ● high
146.0.226.230/31 BUKVA RIPE ASSIGNED PA ● high
146.0.226.248/31 BUKVA RIPE ASSIGNED PA ● high
2a01:7a0:2:154f::/64 BUKVA RIPE ASSIGNED ● high
2a01:7a7:2:413d::/64 BUKVA RIPE ASSIGNED ● high

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 (9 of 9)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE FGK-MNT FGK10-RIPE ORG-BA1813-RIPE ORG-SP242-RIPE