AS201014 AXILARIS axilaris GmbH
🇩🇪Org handle: ORG-AG133-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
2total
1 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)1,024
Announced (BGP)1,024
IPv6 Addresses
Allocated (RIR)6.3×10²⁹
Announced (BGP)6.3×10²⁹
Announced Prefixes
(BGP)2|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-11 | |
| Valid | RIPE | 2026-10-11 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 185.88.224.0/22 | 🇩🇪 DE | RIPENCC | allocated |
| 2a05:cf00::/29 | 🇩🇪 DE | RIPENCC | allocated |
All 2 announced prefixes of AS201014 →
BGP Neighbours
(seen in AS paths)Upstreams (2)
Networks AS201014 hands its own prefixes to: transit providers, or peers at an exchange.
Other adjacent networks (1)
Adjacent to AS201014 in the transit part of AS paths: peers, providers or customers.
- AS21413ENVIA TEL Envia Tel2
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 AS201014 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/201014Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201014" | jq