NO BKKB Leroen Datapartner AS

NO-BKKB-Leroen-Datapartner-AS
Data as of 2026-10-11
Registry
This organisation
Netblocks17
IPv6 11 prefixes (largest 2a00:14d8:44e5::/48)
Also registered under this name 28 netblocks across 3 separate records
Record ID246092445
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 (17)

⬇ export CSV
CIDR Org name Registry Status Confidence
82.134.2.72/30 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED PA ● low
82.134.69.48/30 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED PA ● low
82.134.93.104/30 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED PA ● low
85.200.200.80/30 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED PA ● low
85.200.203.88/30 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED PA ● low
85.200.249.188/30 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED PA ● low
2a00:14d8:1001:869::/64 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:1001:a03::/64 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:1001:a0e::/64 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:1001:a14::/64 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:1001:b7f::/64 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:1001:cc0::/64 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:44e5::/48 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:485b::/48 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:4a06::/48 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:4a20::/48 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low
2a00:14d8:4cca::/48 NO-BKKB-Leroen-Datapartner-AS RIPE ASSIGNED ● low

IPv6 ranges (11)

Footprint over time

16 weekly snapshots · JSON
17 0 netblocks since 2026-07-05
2026-07-05 peak 17 2026-10-11

Network trust

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

These blocks are registered to NO BKKB Leroen Datapartner 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:4a06::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:485b::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4a20::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:44e5::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4cca::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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