SHKOLA2

BGP inherited

Cluster stats

Netblocks	6
All fragments	10 blocks across 2 clusters
Cluster ID	205782886
Registry	RIPE
Customers	find customers using 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

Footprint over time

4 weekly snapshots · JSON

6 0 netblocks since 2026-07-05

2026-07-05 peak 6 2026-07-13

IP Ranges (6)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
2.133.23.8/30	SHKOLA2	RIPE	ASSIGNED PA	● low
2.133.23.28/30	SHKOLA2	RIPE	ASSIGNED PA	● low
37.150.63.164/30	SHKOLA2	RIPE	ASSIGNED PA	● low
84.240.253.220/30	SHKOLA2	RIPE	ASSIGNED PA	● low
88.204.206.224/30	SHKOLA2	RIPE	ASSIGNED PA	● low
92.46.216.64/30	SHKOLA2	RIPE	ASSIGNED PA	● low

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “SHKOLA2” — often per-country or per-system registrations of the same brand, occasionally a different organisation sharing the name. Not counted in this organisation's own footprint.

SHKOLA2_ARK 4 blocks

Sub-allocations under carriers

IP blocks an ISP reassigned to a similarly-named customer — decoded from the ISP's own naming convention, not a direct registration.

ALGASREDSHKOLA2 via JSC Kazakhtelecom sub-allocation
ILIISK_SHKOLA2 via JSC Kazakhtelecom sub-allocation
ILIISK_SHKOLA22 via JSC Kazakhtelecom sub-allocation
ILIISK_SHKOLA23 via JSC Kazakhtelecom sub-allocation
ILIISK_SHKOLA20 via JSC Kazakhtelecom sub-allocation
Otdel Obrazovaniyashkola24 via JSC Kazakhtelecom sub-allocation
NACHALNAYASHKOLA2 via JSC Kazakhtelecom sub-allocation
Shkola282 via JSC Kazakhtelecom sub-allocation

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (6 of 6)

No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT