NO BKKB Websystemer As

NO-BKKB-Websystemer-As
Data as of 2026-09-27
Registry
This organisation
Netblocks6
IPv6 3 prefixes (largest 2a00:14d8:41fe::/48)
Also registered under this name 8,116 netblocks across 2,748 separate records
Record ID245861986
RegistryRIPE
Customerssee who runs inside 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 · report an issue

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.205.224/30 NO-BKKB-Websystemer-As RIPE ASSIGNED PA ● low
62.97.213.232/30 NO-BKKB-Websystemer-As RIPE ASSIGNED PA ● low
82.134.104.172/30 NO-BKKB-Websystemer-As RIPE ASSIGNED PA ● low
2a00:14d8:1001:101::/64 NO-BKKB-Websystemer-As RIPE ASSIGNED ● low
2a00:14d8:1001:ca4::/64 NO-BKKB-Websystemer-As RIPE ASSIGNED ● low
2a00:14d8:41fe::/48 NO-BKKB-Websystemer-As RIPE ASSIGNED ● low

IPv6 ranges (3)

Footprint over time

11 weekly snapshots · JSON
6 0 netblocks since 2026-07-05
2026-07-05 peak 6 2026-09-27

Network trust

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

These blocks are registered to NO BKKB Websystemer 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:41fe::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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