NO BKKB 4SUBSEA AS
NO-BKKB-4SUBSEA-AS
Data as of 2026-09-13
Registry
This organisation
| Netblocks | 4 |
| IPv6 | 3 prefixes (largest 2a00:14d8:41d9::/48) |
| Also registered under this name | 5 netblocks across 2 separate records |
| Record ID | 240767665 |
| Registry | RIPE |
| Customers | see who runs inside 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 | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 82.134.17.96/30 | NO-BKKB-4SUBSEA-AS | RIPE | ASSIGNED PA | ● low |
| 2a00:14d8:1001:ecb::/64 | NO-BKKB-4SUBSEA-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:41d9::/48 | NO-BKKB-4SUBSEA-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4ef8::/48 | NO-BKKB-4SUBSEA-AS | RIPE | ASSIGNED | ● low |
IPv6 ranges (3)
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(4 of 4)
Possible discrepancies (2)
These blocks are registered to NO BKKB 4SUBSEA 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:41d9::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:4ef8::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
NIC Handles
BKKB-MNT
DUMY-RIPE
DUMY-RIPE
LYSE-MNT