NO BKKB Iteam 1 AS

NO-BKKB-Iteam-1-AS
Data as of 2026-09-20
Registry
This organisation
Netblocks9
IPv6 6 prefixes (largest 2a00:14d8:4858::/48)
Also registered under this name 12 netblocks across 2 separate records
Record ID240852291
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 (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.238.244/30 NO-BKKB-Iteam-1-AS RIPE ASSIGNED PA ● low
82.134.80.176/30 NO-BKKB-Iteam-1-AS RIPE ASSIGNED PA ● low
85.200.203.84/30 NO-BKKB-Iteam-1-AS RIPE ASSIGNED PA ● low
2a00:14d8:1001:866::/64 NO-BKKB-Iteam-1-AS RIPE ASSIGNED ● low
2a00:14d8:1001:90b::/64 NO-BKKB-Iteam-1-AS RIPE ASSIGNED ● low
2a00:14d8:1001:a0b::/64 NO-BKKB-Iteam-1-AS RIPE ASSIGNED ● low
2a00:14d8:4858::/48 NO-BKKB-Iteam-1-AS RIPE ASSIGNED ● low
2a00:14d8:48fd::/48 NO-BKKB-Iteam-1-AS RIPE ASSIGNED ● low
2a00:14d8:4aee::/48 NO-BKKB-Iteam-1-AS RIPE ASSIGNED ● low

IPv6 ranges (6)

Footprint over time

13 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-09-20

Network trust

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

These blocks are registered to NO BKKB Iteam 1 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:4858::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:48fd::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4aee::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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