Kyberorg IT OU

Data as of 2026-08-16
BGP inherited
Cluster stats
Netblocks10
IPv6 10 prefixes (largest 2a12:bec4:1c40::/44)
Cluster ID222418397
RegistryBGP
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
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

Footprint over time

8 weekly snapshots · JSON
10 +2 netblocks since 2026-07-05
2026-07-05 peak 10 2026-08-16

IP Ranges (10)

⬇ export CSV
CIDR Org name Registry Status Confidence
2602:f72e:c0::/48 Kyberorg IT OU BGP ANNOUNCED ● high
2602:f72e:c1::/48 Kyberorg IT OU BGP ANNOUNCED ● high
2a0b:4e07:d1::/48 Kyberorg IT OU BGP ANNOUNCED ● high
2a12:bec4:16a5::/48 Kyberorg IT OU BGP ANNOUNCED ● high
2a12:bec4:1c40::/44 Kyberorg IT OU BGP ANNOUNCED ● high
2a12:bec4:1d5f::/48 Kyberorg IT OU BGP ANNOUNCED ● high
2a12:bec4:1dc0::/44 Kyberorg IT OU BGP ANNOUNCED ● high
2a12:bec4:1ed0::/44 Kyberorg IT OU BGP ANNOUNCED ● high
2a12:bec4:1f80::/44 Kyberorg IT OU BGP ANNOUNCED ● high
2a12:bec4:1f90::/44 Kyberorg IT OU BGP ANNOUNCED ● high

IPv6 ranges (10)

CIDR
2a12:bec4:1c40::/44
2a12:bec4:1dc0::/44
2a12:bec4:1ed0::/44
2a12:bec4:1f80::/44
2a12:bec4:1f90::/44
2602:f72e:c0::/48
2602:f72e:c1::/48
2a0b:4e07:d1::/48
2a12:bec4:16a5::/48
2a12:bec4:1d5f::/48

Network trust

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

These blocks are registered to Kyberorg IT 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

NIC Handles

AS11967 AS214630 HOP179-MNT SBL-MNT