Skip to main content

AS138384

RMNI-AS-AP

Rakuten Mobile Network, Inc.

Registry

Authoritative registration data

AS number
138384
Name
RMNI-AS-AP
Organisation
Rakuten Mobile Network, Inc.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

31

IPv6 prefixes

1

Total announced

32

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS138384
157.192.0.0/16 IPv4 /16 not checked
110.165.128.0/17 IPv4 /17 not checked
133.106.128.0/17 IPv4 /17 not checked
193.119.128.0/17 IPv4 /17 not checked
219.106.0.0/17 IPv4 /17 not checked
101.102.0.0/18 IPv4 /18 not checked
119.30.192.0/18 IPv4 /18 not checked
133.106.64.0/18 IPv4 /18 not checked
193.114.192.0/18 IPv4 /18 not checked
219.105.192.0/18 IPv4 /18 not checked
119.31.128.0/19 IPv4 /19 not checked
133.106.32.0/19 IPv4 /19 not checked
193.114.32.0/19 IPv4 /19 not checked
193.114.64.0/19 IPv4 /19 not checked
193.115.0.0/19 IPv4 /19 not checked
193.117.96.0/19 IPv4 /19 not checked
193.118.0.0/19 IPv4 /19 not checked
193.118.64.0/19 IPv4 /19 not checked
193.82.160.0/19 IPv4 /19 not checked
194.193.224.0/19 IPv4 /19 not checked
194.193.64.0/19 IPv4 /19 not checked
194.223.96.0/19 IPv4 /19 not checked
210.157.192.0/19 IPv4 /19 not checked
211.133.160.0/19 IPv4 /19 not checked
211.7.96.0/19 IPv4 /19 not checked
133.106.16.0/20 IPv4 /20 not checked
202.176.16.0/20 IPv4 /20 not checked
202.216.0.0/20 IPv4 /20 not checked
219.105.144.0/20 IPv4 /20 not checked
133.106.8.0/21 IPv4 /21 not checked
103.124.0.0/22 IPv4 /22 not checked
240b:c000::/24 IPv6 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS138384
Address families
BBIX Osaka 100,000 Mbps IPv4 · IPv6
BBIX Tokyo 100,000 Mbps IPv4 · IPv6
Equinix Osaka 100,000 Mbps IPv4 · IPv6
Equinix Tokyo 100,000 Mbps IPv4 · IPv6
JPIX OSAKA 100,000 Mbps IPv4 · IPv6
JPIX TOKYO 100,000 Mbps IPv4 · IPv6
JPNAP Osaka 100,000 Mbps IPv4 · IPv6
JPNAP Tokyo: Peering 100,000 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS138384 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS138384 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 321 4,310
v4 v6
AS2914 NTT-DATA-2914 251 3,413
v4 v6
AS2497 IIJ 235 3,366
v4 v6
AS6939 HURRICANE 264 1,064
v4 v6
AS8220 COLT 15 263
v4 v6
AS20485 TRANSTELECOM 12 152
v4
AS9002 RETN-AS 6 82
v4 v6
AS132132 REPUBLICTELECOM-SG 4 48
v4
AS2516 KDDI 5 45
v4
AS7473 SINGTEL-AS-AP 3 41
v4 v6
AS9304 HUTCHISON-AS-AP 3 38
v4
AS15412 FLAG-AS 3 38
v4
AS60068 CDN77 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS138384 in AS paths

Observed downstreams
Families
AS10012 FUSION 373 1,660
v4 v6
AS23720 RMNI-AS-AP 383 1,323
v4 v6
AS23820 RAKUTEN 21 186
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

15 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 3 451
v4 v6
AS1828 UNITAS 4 57
v4 v6
AS59105 HOMENOC 4 57
v4 v6
AS17639 CONVERGE-AS 4 42
v4 v6
AS2500 WIDE-BB 3 41
v4 v6
AS4777 APNIC-COLO 3 41
v4 v6
AS18106 VIEWQWEST-SG-AP 3 41
v4 v6
AS35280 F5 3 41
v4 v6
AS36236 NETACTUATE 3 41
v4 v6
AS45489 SLT-GLOBAL 3 41
v4 v6
AS49544 i3Dnet 3 41
v4 v6
AS23820 RAKUTEN 1 16
v4 v6
AS10012 FUSION 1 5
v4 v6
AS23720 RMNI-AS-AP 1 4
v4 v6
AS25152 K-ROOT-SERVER 3 3
v6

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.