ResearchRouting table, RPKI, IRR & looking glass

AS38910 Transit AS Tokyo

AS38910 (JPMORGAN-TRANSIT-AS-JP-AP) is registered to Transit AS Tokyo in US. It originates 6 prefixes in the global routing table.

3
IPv4 prefixes
3
IPv6 prefixes
8,192
IPv4 addresses
100%
RPKI valid

Who holds AS38910

Names from RIPE NCC’s daily list of every allocated AS number. The ASN lookup fetches the full WHOIS record live.

AS number
AS38910
Handle
JPMORGAN-TRANSIT-AS-JP-AP
Organization
Transit AS Tokyo
Country
US
ASPA
None published

What AS38910 announces

Prefixes originated by AS38910 in the RouteViews table (refreshed every four hours), each checked against the RPKI (every ten minutes) and the IRR (daily).

IPv4 prefixes
3
IPv6 prefixes
3
IPv4 addresses
8,192 (32 /24s)
RPKI valid
6 100%
RPKI invalid
0
RPKI not found
0
ROAs naming AS38910
6
With an IRR route object
6 100%

Announced prefixes

Each opens its own page: who announces it, the paths our collectors see, its ROAs and route objects.

Who AS38910 is reached through

The AS just before AS38910 in the paths our looking glass collectors hold, for 6 of its prefixes. Usually a transit provider, sometimes a peer. The number is how many of those prefixes it was seen on.

Routing registry objects

From the mirrored IRR databases (RADB, the five RIRs and more). Look it up live.

Sourceas-nameMaintained by
APNICJPMORGAN-TRANSIT-AS-JP-APAPNIC-HM

Route objects with origin AS38910: APNIC 6 · ARIN 1 · RADB 1

as-sets that list AS38910 (6)