LEX
Unresolved
Cluster stats
| Netblocks | 4 |
| All fragments | 82 blocks across 43 clusters |
| Cluster ID | 191702645 |
| Registry | RIPE |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 4 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (4)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 89.175.9.40/30 | Lex-net | RIPE | ASSIGNED PA | ● low |
| 213.183.251.128/27 | Lex-Net | RIPE | ASSIGNED PA | ● low |
| 217.27.140.248/29 | LEX-Net | RIPE | ASSIGNED PA | ● low |
| 2a14:c880::/30 | LEX | RIPE | ASSIGNED | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
50.0%
of checked blocks have valid RPKI ROA coverage
(2 of 4)
Possible discrepancies (1)
These blocks are registered to LEX but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 2a14:c880::/30 /30 | authorized for AS216213 — Lexistar Alliance Ltd. |
NIC Handles
ARTX-RIPE-MNT
DUMY-RIPE
DUMY-RIPE
MTU-NOC
lir-sc-lexistar2-1-MNT