Eksi — IP ranges & network footprint

Footprint over time

5 weekly snapshots · JSON

7 0 netblocks since 2026-07-05

2026-07-05 peak 7 2026-07-19

IP Ranges (7)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
185.0.29.38/32	Eksi	PEERINGDB	ASSIGNED	● high
185.1.63.203/32	Eksi	PEERINGDB	ASSIGNED	● high
185.1.66.5/32	Eksi	PEERINGDB	ASSIGNED	● high
185.1.85.49/32	Eksi	PEERINGDB	ASSIGNED	● high
185.1.134.22/32	Eksi	PEERINGDB	ASSIGNED	● high
185.1.196.20/32	Eksi	PEERINGDB	ASSIGNED	● high
185.1.213.143/32	Eksi	PEERINGDB	ASSIGNED	● high

Possibly related to this organisation

what's this?

Same name family

Separately-registered clusters whose names share “Eksi” — 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.

EKSI-516294-Bangalore 2 blocks
EKSI-MINSK 1 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.

Teleros-Leksika-SLPK-NET sub-allocation
Neksi via MTS PJSC sub-allocation
Teksib M via MTS PJSC sub-allocation
Eksima via MTS PJSC sub-allocation
Neksit via MTS PJSC sub-allocation
Himteksinzheneriya via MTS PJSC sub-allocation
Eksim Personal via MTS PJSC sub-allocation
Eksim Standart sub-allocation

NIC Handles

AS44411

Netblocks	7
All fragments	10 blocks across 3 clusters
Cluster ID	213187559
Registry	PEERINGDB
Customers	find customers using this network →

Attribution	BGP parent (inherited)
Shared handles	clustered on 1 shared RIR contact/maintainer handle
Registry names	1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works