SKIF

BGP inherited
Cluster stats
Netblocks6
Registered in KZ (4) · Russia (2)
All fragments 23 blocks across 8 clusters
Cluster ID209356102
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 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
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
82.200.81.240/30 SKIF-NET RIPE ASSIGNED PA ● low
88.204.132.56/30 SKIF RIPE ASSIGNED PA ● low
88.204.132.60/30 SKIF RIPE ASSIGNED PA ● low
89.21.142.40/29 SKIF-NET RIPE ASSIGNED PA ● low
89.218.46.40/30 SKIF RIPE ASSIGNED PA ● low
95.56.232.52/30 SKIF RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “SKIF” — 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.
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.

Network trust

what's this?
RPKI hygiene: C how networks compare →
66.7% of checked blocks have valid RPKI ROA coverage (4 of 6)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT MNT-TELECOM-TZ ZSTTK-MNT