NO BKKB Intility AS
NO-BKKB-Intility-AS
Registry
Cluster stats
| Netblocks | 16 |
| All fragments | 8,116 blocks across 2,748 clusters |
| Cluster ID | 192630053 |
| 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 | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-06
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 62.97.222.44/30 | NO-BKKB-Intility-AS | RIPE | ASSIGNED PA | ● low |
| 82.134.4.164/30 | NO-BKKB-Intility-AS | RIPE | ASSIGNED PA | ● low |
| 82.134.28.240/30 | NO-BKKB-Intility-AS | RIPE | ASSIGNED PA | ● low |
| 82.134.30.244/30 | NO-BKKB-Intility-AS | RIPE | ASSIGNED PA | ● low |
| 82.134.52.236/30 | NO-BKKB-Intility-AS | RIPE | ASSIGNED PA | ● low |
| 85.200.208.104/29 | NO-BKKB-Intility-AS | RIPE | ASSIGNED PA | ● low |
| 2a00:14d8:1001:423::/64 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:1001:936::/64 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:1001:d1f::/64 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:1001:e35::/64 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:1001:1055::/64 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:451b::/48 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4928::/48 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4d38::/48 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:4f3d::/48 | NO-BKKB-Intility-AS | RIPE | ASSIGNED | ● low |
| 2a00:14d8:5067::/48 | NO-BKKB-Intility-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
(16 of 16)
Possible discrepancies (5)
These blocks are registered to NO BKKB Intility 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:4f3d::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:5067::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:4928::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:4d38::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
| 2a00:14d8:451b::/48 /48 | authorized for AS8542 — Eviny Fiber AS |
NIC Handles
BKKB-MNT
DUMY-RIPE
DUMY-RIPE
LYSE-MNT