AS402319 BYOIP-ASN - TAIPEI101
🇺🇸ARINassignedASPA Published
Announced Prefixes (BGP)
3total
2 IPv41 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)768
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)1.2×10²⁴
Routing hygiene
Score 15/100 · Low riskRPKI ROA coverage
100%
no RPKI invalid prefixes
IRR route objects
100%
no origin mismatches
Hijack signals
1
0 announced against others' ROAs, 1 own announced by others
Upstreams
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
- 1 prefix of this ASN announced by another network against its ROAs
Based on 3 announced prefixes, updated daily (2026-10-26). How the score works · RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | - | 2026-10-26 | |
| Valid | ARIN | 2026-10-26 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 85.149.216.0/23 | 🇺🇸 US | RIPE | assigned |
All 3 announced prefixes of AS402319 →
Upstream Providers(1)
| ASN | Name |
|---|---|
| AS216211 | 🇺🇸CYBERVERSE-BACKBONE CYBERVERSE LLC |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS402319 hands its own prefixes to: transit providers, or peers at an exchange.
- AS216211CYBERVERSE BACKBONE CYBERVERSE3
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 ARIN 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/402319Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/402319" | jq