NO-BKKB-BOB-BBL

Data as of 2026-09-13
BGP inherited
This organisation
Netblocks10
IPv6 5 prefixes (largest 2a00:14d8:47b2::/48)
Also registered under this name 8,116 netblocks across 2,748 separate records
Record ID240762397
RegistryRIPE
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.238.236/30 NO-BKKB-BOB-BBL RIPE ASSIGNED PA ● low
82.134.53.224/28 NO-BKKB-BOB-BBL RIPE ASSIGNED PA ● low
82.134.104.56/30 NO-BKKB-BOB-BBL RIPE ASSIGNED PA ● low
85.200.204.24/29 NO-BKKB-BOB-BBL RIPE ASSIGNED PA ● low
85.200.254.32/29 NO-BKKB-BOB-BBL RIPE ASSIGNED PA ● low
2a00:14d8:1001:7c0::/64 NO-BKKB-BOB-BBL RIPE ASSIGNED ● low
2a00:14d8:1001:7c6::/64 NO-BKKB-BOB-BBL RIPE ASSIGNED ● low
2a00:14d8:1001:bc0::/64 NO-BKKB-BOB-BBL RIPE ASSIGNED ● low
2a00:14d8:47b2::/48 NO-BKKB-BOB-BBL RIPE ASSIGNED ● low
2a00:14d8:4bbf::/48 NO-BKKB-BOB-BBL RIPE ASSIGNED ● low

IPv6 ranges (5)

Footprint over time

12 weekly snapshots · JSON
10 0 netblocks since 2026-07-05
2026-07-05 peak 10 2026-09-13

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (10 of 10)
Possible discrepancies (2)

These blocks are registered to NO-BKKB-BOB-BBL but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2a00:14d8:4bbf::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:47b2::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

BKKB-MNT DUMY-RIPE DUMY-RIPE LYSE-MNT