NO BKKB Bergen Rode Kors Sykehjem AS

NO-BKKB-Bergen-Rode-Kors-Sykehjem-AS
Registry
Cluster stats
Netblocks5
All fragments 306 blocks across 108 clusters
Cluster ID209540630
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution Registry record
Shared handles clustered on 4 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
62.97.203.156/30 NO-BKKB-Bergen-Rode-Kors-Sykehjem-AS RIPE ASSIGNED PA ● low
82.134.22.40/30 NO-BKKB-Bergen-Rode-Kors-Sykehjem-AS RIPE ASSIGNED PA ● low
82.134.93.40/29 NO-BKKB-Bergen-Rode-Kors-Sykehjem RIPE ASSIGNED PA ● low
2a00:14d8:1001:f3a::/64 NO-BKKB-Bergen-Rode-Kors-Sykehjem-AS RIPE ASSIGNED ● low
2a00:14d8:4f70::/48 NO-BKKB-Bergen-Rode-Kors-Sykehjem-AS RIPE ASSIGNED ● low

Network trust

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

These blocks are registered to NO BKKB Bergen Rode Kors Sykehjem 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:4f70::/48 /48 authorized for AS8542 — Eviny Fiber AS

NIC Handles

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