INKAR

BGP inherited
Cluster stats
Netblocks8
Registered in KZ (5) · Russia (3)
All fragments 10 blocks across 3 clusters
Cluster ID209188645
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

5 weekly snapshots · JSON
8 0 netblocks since 2026-07-05
2026-07-05 peak 8 2026-07-19

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
2.133.92.200/29 INKAR RIPE ASSIGNED PA ● low
83.219.6.0/28 INKAR-LTD RIPE ASSIGNED PA ● low
83.219.24.96/29 INKAR-LTD RIPE ASSIGNED PA ● low
83.219.25.56/29 INKAR-LTD RIPE ASSIGNED PA ● low
84.240.225.24/30 INKAR RIPE ASSIGNED PA ● low
84.240.226.92/30 INKAR RIPE ASSIGNED PA ● low
89.218.25.188/30 INKAR RIPE ASSIGNED PA ● low
92.46.214.160/30 INKAR RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “INKAR” — 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: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (8 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE KNIC-MNT PI-RIPE-MNT ROSTELECOM-MNT