AS34863 HEXANET HEXANET SAS
π«π·Org handle: ORG-HS295-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
20total
17 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)18,432
Announced (BGP)18,688
IPv6 Addresses
Allocated (RIR)7.9Γ10Β²βΉ
Announced (BGP)7.9Γ10Β²βΉ
Prefix Limit (IPv4)
50
Prefix Limit (IPv6)
10
Country
π«π· FRRIR
RIPE NCCStatus
allocated
Allocated
2005-04-20
Announced Prefixes
(BGP)20|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
1-10 of 20
1 / 2
Allocated Prefixes
(RIR)20Prefix | Country | RIR | Status |
|---|---|---|---|
| 46.226.128.0/21 | π«π· FR | RIPENCC | allocated |
| 62.106.77.0/24 | π«π· FR | RIPENCC | allocated |
| 81.23.32.0/20 | π«π· FR | RIPENCC | allocated |
| 85.204.20.0/23 | π«π· FR | RIPENCC | allocated |
| 85.204.24.0/23 | π«π· FR | RIPENCC | allocated |
| 89.35.96.0/20 | π«π· FR | RIPE | assigned |
| 176.116.26.0/24 | π«π· FR | RIPENCC | allocated |
| 185.2.252.0/22 | π«π· FR | RIPENCC | allocated |
| 185.63.48.0/22 | π«π· FR | RIPENCC | allocated |
| 185.63.48.0/24 | π«π· FR | RIPE | assigned |
1-10 of 20
1 / 2
All 20 announced prefixes of AS34863 β
BGP Neighbours
(seen in AS paths)ASPA
No ASPA
Abuse Contact
External Links
Learn more
- What is an ASN?Autonomous systems, ASN ranges and how they are assigned
- RPKI and route origin validationWhat the RPKI badges on the prefix list mean
- ASPA explainedWhy AS34863 should publish an ASPA object
- IPv4 transfers in the RIPE NCC regionMonthly volume and the latest registry transfers
- ASN data in AI agents and SIEMMCP server and API integrations
API
Open https://api.ipctl.io/v1/asn/34863Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/34863" | jq