AS213617 ORG-BN162-RIPE KANG ZHENG OO
🇹🇼Org handle: ORG-BN162-RIPE
RIPE NCCallocated
Announced Prefixes (BGP)
6total
0 IPv46 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)3.1×10²⁶
Announced (BGP)2.5×10²⁵
Routing hygiene
Score 12/100 · Low riskRPKI ROA coverage
83.3%
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
2
diversity 28/100
- Routes concentrated on one upstream (83% of routes)
- 17% of announced prefixes (1 of 6) have no valid ROA
Based on 6 announced prefixes, updated daily (2026-10-26). How the score works · RPKI explained
Announced Prefixes
(BGP)6|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | ARINOther IRR | 2026-10-25 | |
| Valid | Other IRRRIPE | 2026-10-25 | |
| No ROA | Other IRR | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 | |
| Valid | RIPE | 2026-10-25 |
Allocated Prefixes
(RIR)2Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0c:9a40:8720::/48 | 🇹🇼 TW | RIPE | assigned |
| 2a14:7581:9b00::/40 | 🇹🇼 TW | RIPE | assigned |
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 AS213617 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/213617Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/213617" | jq