NO BKKB NABOEN AS

NO-BKKB-NABOEN-AS
Registry
Cluster stats
Netblocks23
All fragments 8,116 blocks across 2,748 clusters
Cluster ID205663187
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
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

Footprint over time

4 weekly snapshots · JSON
23 0 netblocks since 2026-07-05
2026-07-05 peak 23 2026-07-13

IP Ranges (23)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.134.7.52/30 NO-BKKB-NABOEN-AS RIPE ASSIGNED PA ● low
82.134.25.40/30 NO-BKKB-NABOEN-AS RIPE ASSIGNED PA ● low
82.134.58.124/30 NO-BKKB-NABOEN-AS RIPE ASSIGNED PA ● low
82.134.58.188/30 NO-BKKB-NABOEN-AS RIPE ASSIGNED PA ● low
85.200.217.80/30 NO-BKKB-NABOEN-AS RIPE ASSIGNED PA ● low
85.200.230.240/30 NO-BKKB-NABOEN-AS RIPE ASSIGNED PA ● low
85.200.249.168/30 NO-BKKB-NABOEN-AS RIPE ASSIGNED PA ● low
2a00:14d8:1001:2f5::/64 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:1001:c6f::/64 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:1001:e4f::/64 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:1001:f34::/64 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:1001:f39::/64 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:1001:fa7::/64 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:1001:1092::/64 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:1001:1095::/64 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:43ef::/48 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:4df1::/48 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:4e0c::/48 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:4e74::/48 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:4eef::/48 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:5106::/48 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:5109::/48 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low
2a00:14d8:5110::/48 NO-BKKB-NABOEN-AS RIPE ASSIGNED ● low

Network trust

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

These blocks are registered to NO BKKB NABOEN AS 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:4df1::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4e0c::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4e74::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4eef::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:5106::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:5109::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:5110::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:43ef::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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