AS38910 JPMORGAN-TRANSIT-AS-JP-AP Transit AS Tokyo

🇺🇸

Org handle: ORG-JMCC1-AP

Transit AS Tokyo

APNICallocated

Announced Prefixes (BGP)

6total

3 IPv43 IPv6

IPv4 Addresses

Allocated (RIR)16,384

Announced (BGP)16,384

IPv6 Addresses

Allocated (RIR)0

Announced (BGP)4.3×10²⁵

Prefix Limit (IPv4)

Prefix Limit (IPv6)

Country

RIR

Status

allocated

Allocated

2008-02-22

Announced Prefixes

(BGP)6

Prefix	RPKI	IRR	Last Seen
161.121.128.0/19	Valid	APNIC	2026-10-11
161.121.128.0/20	Valid	APNIC	2026-10-11
161.121.144.0/20	Valid	APNIC	2026-10-11
2407:e500:40::/43	Valid	APNIC	2026-10-11
2407:e500:40::/47	Valid	APNIC	2026-10-11
2407:e500:50::/47	Valid	APNIC	2026-10-11

(RIR)3

Prefix	Country	RIR	Status
161.121.128.0/19	🇺🇸 US	APNIC	allocated
161.121.128.0/20	🇮🇳 IN	APNIC	assigned
161.121.144.0/20	🇮🇳 IN	APNIC	assigned

(seen in AS paths)

Networks AS38910 hands its own prefixes to: transit providers, or peers at an exchange.

ASPA

No ASPA

External Links

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 AS38910 should publish an ASPA object
IPv4 transfers in the APNIC regionMonthly volume and the latest registry transfers
ASN data in AI agents and SIEMMCP server and API integrations

API

Returns ASN details, announced prefixes, and BGP routing data.

curl -s "https://api.ipctl.io/v1/asn/38910" | jq