LUKOIL-INFORM

BGP inherited
Cluster stats
Netblocks8 · 680 IPv4 addresses
All fragments 216 blocks across 166 clusters
Cluster ID209015586
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 4 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
80.237.91.224/28 Lukoil-Inform-NET RIPE ASSIGNED PA ● low
82.118.130.16/29 LUKOIL-INFORM RIPE ASSIGNED PA ● low
95.171.248.0/24 LUKOIL-INFORM RIPE ASSIGNED PA ● low
212.38.96.232/29 LUKOIL-INFORM RIPE ASSIGNED PA ● low
212.38.102.0/24 LUKOIL-INFORM RIPE ASSIGNED PA ● low
212.38.106.64/26 LUKOIL-INFORM RIPE ASSIGNED PA ● low
212.38.106.128/26 LUKOIL-INFORM RIPE ASSIGNED PA ● low
212.38.120.144/28 LUKOIL-INFORM RIPE ASSIGNED PA ● low

Possibly related to this organisation

what's this?
Same name family
Separately-registered clusters whose names share “LUKOIL INFORM” — 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.
Combined view of all 166 name-family clusters →
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: F how networks compare →
12.5% of checked blocks have valid RPKI ROA coverage (1 of 8)
No discrepancies found among checked blocks.

NIC Handles

DUMY-RIPE DUMY-RIPE LUKOIL-INFORM-MNT-RIPE TRANSTELECOM-MNT