NO BKKB Keynet AS
NO-BKKB-Keynet-AS
Registry
Cluster stats
| Netblocks | 17 |
| All fragments | 18 blocks across 2 clusters |
| Cluster ID | 204965207 |
| Registry | RIPE |
| Customers | find 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 | |
Footprint over time
4 weekly snapshots · JSON
17
0 netblocks since 2026-07-05
2026-07-05
peak 17
2026-07-13
IP Ranges (17)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.97.196.56/30 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED PA | ● low |
| 82.134.8.120/30 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED PA | ● low |
| 82.134.42.192/30 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED PA | ● low |
| 85.200.240.60/30 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED PA | ● low |
| 85.200.248.112/30 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED PA | ● low |
| 2a00:14d8:1001:2b0::/64 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:1001:39b::/64 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:1001:9a5::/64 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:1001:e69::/64 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:1001:e9f::/64 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:43ab::/48 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4494::/48 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4586::/48 | NO-BKKB-KEYNET-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:45bf::/48 | NO-BKKB-KEYNET-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4999::/48 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4e95::/48 | NO-BKKB-Keynet-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4fee::/48 | NO-BKKB-Keynet-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
(17 of 17)
Possible discrepancies (7)
These blocks are registered to NO BKKB Keynet 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:4586::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:45bf::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:4999::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:43ab::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:4e95::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:4494::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:4fee::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
NIC Handles
BKKB-MNT
DUMY-RIPE
DUMY-RIPE
LYSE-MNT