NO-BKKB-Bergen-og-Omegn-Boligbyggelag
BGP inherited
Cluster stats
| Netblocks | 3 |
| All fragments | 4 blocks across 2 clusters |
| Cluster ID | 214514671 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| 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 (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.97.202.120/30 | NO-BKKB-Bergen-og-Omegn-Boligbyggelag | RIPE | ASSIGNED PA | ● low |
| 62.97.255.72/29 | NO-BKKB-Bergen-og-Omegn-Boligbyggelag | RIPE | ASSIGNED PA | ● low |
| 2a00:14d8:4660::/48 | NO-BKKB-BERGEN-OG-OMEGN-BOLIGBYGGELAG | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(3 of 3)
Possible discrepancies (1)
These blocks are registered to NO-BKKB-Bergen-og-Omegn-Boligbyggelag 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:4660::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
NIC Handles
BKKB-MNT
DUMY-RIPE
DUMY-RIPE
LYSE-MNT