NO BKKB Acos AS

NO-BKKB-Acos-AS
Data as of 2026-07-26
Registry
Cluster stats
Netblocks6
IPv6 2 prefixes (largest 2a00:14d8:439a::/48)
All fragments 8,116 blocks across 2,748 clusters
Cluster ID214515110
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

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

IP Ranges (6)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.204.200/29 NO-BKKB-Acos-AS RIPE ASSIGNED PA ● low
82.134.18.192/27 NO-BKKB-Acos-AS RIPE ASSIGNED PA ● low
82.134.23.60/30 NO-BKKB-Acos-AS RIPE ASSIGNED PA ● low
85.200.208.128/25 NO-BKKB-Acos-AS RIPE ASSIGNED PA ● low
2a00:14d8:1001:29e::/64 NO-BKKB-Acos-AS RIPE ASSIGNED ● low
2a00:14d8:439a::/48 NO-BKKB-Acos-AS RIPE ASSIGNED ● low

IPv6 ranges (2)

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 Acos 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:439a::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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