KLab OU

Data as of 2026-10-04
BGP inherited
This organisation
Netblocks11
IPv6 11 prefixes (largest 2a12:bec4:16a0::/44)
Record ID245768851
RegistryBGP
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 3 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 (11)

⬇ export CSV
CIDR Org name Registry Status Confidence
2602:f72e:24::/48 KLab OU BGP ANNOUNCED ● medium
2602:f72e:c0::/48 KLab OU BGP ANNOUNCED ● medium
2602:f72e:c1::/48 KLab OU BGP ANNOUNCED ● medium
2602:f72e:cd::/48 KLab OU BGP ANNOUNCED ● medium
2a12:bec4:16a0::/44 KLab OU BGP ANNOUNCED ● medium
2a12:bec4:16a5::/48 KLab OU BGP ANNOUNCED ● medium
2a12:bec4:1c40::/44 KLab OU BGP ANNOUNCED ● medium
2a12:bec4:1dc0::/44 KLab OU BGP ANNOUNCED ● medium
2a12:bec4:1ed0::/44 KLab OU BGP ANNOUNCED ● medium
2a12:bec4:1f80::/44 KLab OU BGP ANNOUNCED ● medium
2a12:bec4:1f90::/44 KLab OU BGP ANNOUNCED ● medium

IPv6 ranges (11)

Footprint over time

4 weekly snapshots · JSON
11 +1 netblocks since 2026-09-13
2026-09-13 peak 11 2026-10-04

Network trust

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

These blocks are registered to KLab OU 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.

2602:f72e:c1::/48 /48 authorized for AS11967 — Hop179 OU
2602:f72e:24::/48 /48 authorized for AS11967 — Hop179 OU

NIC Handles

AS11967 AS214630 SBL-MNT