AS205008 HExpNetwork Junqi Huang
🇨🇳Org handle: ORG-HJ175-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
11total
0 IPv411 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)6.3×10²⁶
Announced (BGP)1.3×10²⁵
Routing hygiene
Score 2/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
0
0 announced against others' ROAs, 0 own announced by others
Upstreams
6
diversity 83/100
- All announced prefixes have a valid ROA and a matching IRR route object
Based on 11 announced prefixes, updated daily (2026-10-21). How the score works · RPKI explained
Announced Prefixes
(BGP)11|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
1-10 of 11
1 / 2
Allocated Prefixes
(RIR)13Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0f:1cc5:2700::/40 | 🇨🇳 CN | RIPE | assigned |
| 2a14:7583:f300::/40 | 🇨🇳 CN | RIPE | assigned |
| 2a14:7583:f300::/48 | 🇦🇶 AQ | RIPE | assigned |
| 2a14:7583:f301::/48 | 🇳🇱 NL | RIPE | assigned |
| 2a14:7583:f302::/48 | 🇺🇸 US | RIPE | assigned |
| 2a14:7583:f303::/48 | 🇭🇰 HK | RIPE | assigned |
| 2a14:7583:f304::/48 | 🇭🇰 HK | RIPE | assigned |
| 2a14:7583:f305::/48 | 🇯🇵 JP | RIPE | assigned |
| 2a14:7583:f306::/48 | 🇺🇸 US | RIPE | assigned |
| 2a14:7583:f307::/48 | 🇯🇵 JP | RIPE | assigned |
1-10 of 13
1 / 2
All 11 announced prefixes of AS205008 →
Downstream Customers(1)
| ASN | Name |
|---|---|
| AS214955 | 🇨🇳LaunchPad-Network Weikang Zeng |
BGP Neighbours
(seen in AS paths)Upstreams (6)
Networks AS205008 hands its own prefixes to: transit providers, or peers at an exchange.
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
- How to run an ASPA checkVerify the upstream providers listed above
- 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/205008Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/205008" | jq