AXIALYS

Axialys
Data as of 2026-08-09
GLEIF verified
Complete entity footprint
2 linked clusters · 12 netblocks · 5,122 IPv4 addresses · 3 IPv6 prefixes
This organisation's clusters combined by evidence — shared GLEIF corporate family — not name similarity, so genuinely different organisations that share a name are excluded.
View the full entity page →
LEI
969500TC3489YK1ZCG61
Registered name
AXIALYS
Jurisdiction
FR
Ultimate parent
No parent on file in GLEIF
Cluster stats
Netblocks5 · 514 IPv4 addresses
IPv6 2 prefixes (largest 2001:7f8:43::1:6363:1/128)
All fragments 18 blocks across 6 clusters
Cluster ID218603502
RegistryPEERINGDB
Owner jurisdictionFR
Customersfind customers using this network →
Evidence & provenance ?
Attribution GLEIF legal-entity match
Legal identityLEI 969500TC3489YK1ZCG61
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 · report an issue

IP Ranges (5)

⬇ export CSV
CIDR Org name Registry Status Confidence
37.49.237.17/32 Axialys PEERINGDB ASSIGNED ● high
195.42.144.226/32 Axialys PEERINGDB ASSIGNED ● high
2001:7f8:43::1:6363:1/128 Axialys PEERINGDB ASSIGNED ● high
2001:7f8:54::1:17/128 Axialys PEERINGDB ASSIGNED ● high
217.146.224.0/23 AXIALYS-HOSTING RIPE ASSIGNED PA ● low

IPv6 ranges (2)

CIDR
2001:7f8:43::1:6363:1/128
2001:7f8:54::1:17/128

Corporate group (2 confirmed entities)

+5 additional unconfirmed candidates not shown — full list (JSON)

Network trust

what's this?
RPKI hygiene: B how networks compare →
80.0% of checked blocks have valid RPKI ROA coverage (4 of 5)
No discrepancies found among checked blocks.

NIC Handles

AS16363 AXIALYS-MNT DUMY-RIPE DUMY-RIPE