NO BKKB BKK AS

NO-BKKB-BKK-AS
Data as of 2026-07-26
Registry
Cluster stats
Netblocks11
IPv6 5 prefixes (largest 2a00:14d8:4053::/48)
All fragments 12 blocks across 2 clusters
Cluster ID214513197
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 · report an issue

Footprint over time

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

IP Ranges (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.223.56/30 NO-BKKB-BKK-AS RIPE ASSIGNED PA ● low
62.97.238.100/30 NO-BKKB-BKK-AS RIPE ASSIGNED PA ● low
62.97.242.88/30 NO-BKKB-BKK-AS RIPE ASSIGNED PA ● low
82.134.24.92/30 NO-BKKB-BKK-AS RIPE ASSIGNED PA ● low
82.134.80.96/30 NO-BKKB-BKK-AS RIPE ASSIGNED PA ● low
85.200.240.132/30 NO-BKKB-BKK-AS RIPE ASSIGNED PA ● low
2a00:14d8:1001:5dd::/64 NO-BKKB-BKK-AS RIPE ASSIGNED ● low
2a00:14d8:1001:6c3::/64 NO-BKKB-BKK-AS RIPE ASSIGNED ● low
2a00:14d8:4053::/48 NO-BKKB-BKK-AS RIPE ASSIGNED ● low
2a00:14d8:44b0::/48 NO-BKKB-BKK-AS RIPE ASSIGNED ● low
2a00:14d8:46b6::/48 NO-BKKB-BKK-AS RIPE ASSIGNED ● low

IPv6 ranges (5)

Network trust

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

These blocks are registered to NO BKKB BKK 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:44b0::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:4053::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:46b6::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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