AS402782 AS-JPY - TAIPEI101
🇺🇸ARINassigned
Announced Prefixes (BGP)
7total
4 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)512
Announced (BGP)1,280
IPv6 Addresses
Allocated (RIR)0
Announced (BGP)3.9×10²⁵
Announced Prefixes
(BGP)7|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
85.149.217.0/24MOAS | Valid | RIPE | 2026-10-11 |
| Valid | Other IRRRIPE | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | - | 2026-10-11 | |
| Valid | ARIN | 2026-10-11 | |
| Valid | ARIN | 2026-10-11 | |
| Valid | ARIN | 2026-10-11 |
Allocated Prefixes
(RIR)1Prefix | Country | RIR | Status |
|---|---|---|---|
| 143.20.8.0/23 | 🇪🇺 EU | RIPE | assigned |
All 7 announced prefixes of AS402782 →
BGP Neighbours
(seen in AS paths)Upstreams (3)
Networks AS402782 hands its own prefixes to: transit providers, or peers at an exchange.
Downstreams (7)
Networks whose own prefixes AS402782 passes on: usually its customers.
ASPA
No ASPA
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 AS402782 should publish an ASPA object
- 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/402782Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/402782" | jq