AS201345 Shuma-Watanabe Shuma Watanabe
π―π΅Org handle: ORG-SW125-RIPE
OCITOKEN::201345:dad6a09d8644632ab406a5b8c8856cc9401cfce9985e0007747ea916a4d65cb2
RIPE NCCallocatedASPA Published
Announced Prefixes (BGP)
3total
0 IPv43 IPv6
IPv4 Addresses
Allocated (RIR)0
Announced (BGP)0
IPv6 Addresses
Allocated (RIR)3.1Γ10Β²βΆ
Announced (BGP)3.1Γ10Β²βΆ
Prefix Limit (IPv4)
10
Prefix Limit (IPv6)
10
Country
π―π΅ JPRIR
RIPE NCCStatus
allocated
Allocated
2026-02-09
Routing hygiene
Score 10/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
1
diversity 0/100
- Only one upstream seen in the AS paths of its routes
Based on 3 announced prefixes, updated daily (2026-10-25). How the score works Β· RPKI explained
Announced Prefixes
(BGP)3|
Prefix | RPKI | IRR | Last Seen |
|---|---|---|---|
| Valid | RIPE | 2026-10-26 | |
| Valid | Other IRR | 2026-10-26 | |
| Valid | RIPE | 2026-10-26 |
Allocated Prefixes
(RIR)3Prefix | Country | RIR | Status |
|---|---|---|---|
| 2a0b:4e07:94::/46 | π―π΅ JP | RIPE | assigned |
| 2a0c:9a40:8920::/48 | π―π΅ JP | RIPE | assigned |
| 2a10:fa81:500::/40 | π·π΄ RO | RIPE | assigned |
All 3 announced prefixes of AS201345 β
Upstream Providers(8)
| ASN | Name |
|---|---|
| AS8075 | MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation |
| AS11967 | πͺπͺHOP179 Hop179 OU |
| AS20473 | πΊπΈAS-VULTR - The Constant Company, LLC |
| AS31898 | πΊπΈORACLE-BMC-31898 - Oracle Corporation |
| AS41051 | π¨πFREETRANSIT Openfactory GmbH |
| AS209533 | π¨πBGPTunnel iFog GmbH |
| AS212895 | π©πͺROUTE64_ORG Johannes Ernst |
| AS396982 | πΊπΈGOOGLE-CLOUD-PLATFORM - Google LLC |
BGP Neighbours
(seen in AS paths)Upstreams (1)
Networks AS201345 hands its own prefixes to: transit providers, or peers at an exchange.
- AS212895ROUTE64 ORG Johannes Ernst3
ASPA
Published8 upstreams, 0 downstreams
Authorized Upstream Providers
Expires 2026-10-27
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/201345Returns ASN details, announced prefixes, and BGP routing data.
curl -s "https://api.ipctl.io/v1/asn/201345" | jq