LEXISNEXIS

BGP inherited
Cluster stats
Netblocks8
Registered in United Kingdom (4) · France (3) · Poland (1)
All fragments 27 blocks across 11 clusters
Cluster ID209310647
RegistryRIPE
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 7 shared RIR contact/maintainer handles
Registry names 3 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
46.229.149.16/29 LexisNexis-NET RIPE ASSIGNED PA ● low
86.65.191.32/28 LEXISNEXIS RIPE ASSIGNED PA ● low
86.65.191.48/28 LEXISNEXIS RIPE ASSIGNED PA ● low
91.186.177.160/28 LEXISNEXIS-NET RIPE ASSIGNED PA ● low
91.186.182.128/28 LEXISNEXIS-NET RIPE ASSIGNED PA ● low
91.186.183.208/28 LEXISNEXIS-NET RIPE ASSIGNED PA ● low
109.3.146.64/29 LEXISNEXIS RIPE ASSIGNED PA ● low
212.187.170.240/28 LEXISNEXIS RIPE ASSIGNED PA ● low

Possibly related to this organisation

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

NIC Handles

ATMAN-MNT DUMY-RIPE DUMY-RIPE LDCOM-MNT LDCOM-PRO-MNT LEVEL3-MNT MAINT-VIPAR