AS201705 XLI-NET Xinrun Li
🇨🇳Org handle: ORG-XL124-RIPE
OCITOKEN::201705:24ce91febec56fd2a3c738015654cdd20561876f7641fe4c110897968d689a6d
RIPE NCCallocated
Announced Prefixes (BGP)
9total
0 IPv49 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)5×10²⁵
Announced (BGP)1×10²⁵
Announced Prefixes
(BGP)9|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| No ROA | 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 |
Allocated Prefixes
(RIR)12Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a14:67c3:1680::/44 | 🇭🇰 HK | RIPE | assigned |
| 2a14:67c3:168a::/48 | 🇺🇸 US | RIPE | assigned |
| 2a14:7dc0:510::/44 | 🇳🇱 NL | RIPE | assigned |
| 2a14:7dc0:510::/48 | 🇯🇵 JP | RIPE | assigned |
| 2a14:7dc0:511::/48 | 🇸🇬 SG | RIPE | assigned |
| 2a14:7dc0:512::/48 | 🇨🇳 CN | RIPE | assigned |
| 2a14:7dc0:514::/48 | 🇭🇰 HK | RIPE | assigned |
| 2a14:7dc0:515::/48 | 🇭🇰 HK | RIPE | assigned |
| 2a14:7dc0:516::/48 | 🇨🇦 CA | RIPE | assigned |
| 2a14:7dc0:517::/48 | 🇳🇱 NL | RIPE | assigned |
1-10 of 12
1 / 2
All 9 announced prefixes of AS201705 →
BGP Neighbours
(seen in AS paths)Upstreams (7)
Networks AS201705 hands its own prefixes to: transit providers, or peers at an exchange.
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 AS201705 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/201705Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201705" | jq