NO-BKKB-Voss-Kommune

BGP inherited
Cluster stats
Netblocks9
All fragments 38 blocks across 11 clusters
Cluster ID210093896
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

Footprint over time

5 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-19

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.192.48/28 NO-BKKB-Voss-Kommune RIPE ASSIGNED PA ● low
62.97.234.168/30 NO-BKKB-Voss-Kommune RIPE ASSIGNED PA ● low
62.97.234.192/30 NO-BKKB-Voss-Kommune RIPE ASSIGNED PA ● low
62.97.251.128/28 NO-BKKB-Voss-Kommune RIPE ASSIGNED PA ● low
62.97.251.240/28 NO-BKKB-Voss-Kommune RIPE ASSIGNED PA ● low
2a00:14d8:1001:202::/64 NO-BKKB-Voss-Kommune RIPE ASSIGNED ● low
2a00:14d8:1001:798::/64 NO-BKKB-Voss-Kommune RIPE ASSIGNED ● low
2a00:14d8:42fe::/48 NO-BKKB-Voss-Kommune RIPE ASSIGNED ● low
2a00:14d8:478a::/48 NO-BKKB-Voss-Kommune RIPE ASSIGNED ● low

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 (2)

These blocks are registered to NO-BKKB-Voss-Kommune 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:42fe::/48 /48 authorized for AS8542 — Eviny Fiber AS
2a00:14d8:478a::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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