Skip to main content

AS17961

MITENE

mitene internet co., ltd.

Registry

Authoritative registration data

AS number
17961
Name
MITENE
Organisation
mitene internet co., ltd.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
—
Source:asn:rdap retrieved

IPv4 prefixes

14

IPv6 prefixes

1

Total announced

15

Announced prefixes

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

Prefixes announced by AS17961
124.241.0.0/18 IPv4 /18 not checked
220.213.128.0/18 IPv4 /18 not checked
124.241.0.0/19 IPv4 /19 not checked
124.241.32.0/19 IPv4 /19 not checked
124.241.64.0/19 IPv4 /19 not checked
218.219.160.0/19 IPv4 /19 not checked
220.213.96.0/19 IPv4 /19 not checked
124.241.64.0/20 IPv4 /20 not checked
124.241.80.0/20 IPv4 /20 not checked
124.241.96.0/20 IPv4 /20 not checked
202.238.48.0/20 IPv4 /20 not checked
220.213.112.0/20 IPv4 /20 not checked
220.213.96.0/20 IPv4 /20 not checked
124.241.112.0/21 IPv4 /21 not checked
2402:e200::/32 IPv6 /32 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 AS17961
Address families
BBIX Hong Kong 1,000 Mbps IPv4 · IPv6
BBIX Osaka 20,000 Mbps IPv4 · IPv6
BBIX Singapore 1,000 Mbps IPv4 · IPv6
BBIX Tokyo 20,000 Mbps IPv4 · IPv6
JPIX TOKYO 20,000 Mbps IPv4 · IPv6
JPNAP Osaka 20,000 Mbps IPv4 · IPv6
JPNAP Tokyo: Peering 20,000 Mbps IPv4 · IPv6
KINX 10,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 AS17961 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS17961 in AS paths

Observed upstreams
Families
AS2518 BIGLOBE 428 2,126
v4 v6
AS2519 VECTANT 428 1,484
v4 v6
AS2497 IIJ 130 820
v4
AS6939 HURRICANE 41 628
v4
AS8966 Etisalat-AS 7 74
v4
AS7473 SINGTEL-AS-AP 5 48
v4
AS9002 RETN-AS 3 20
v4 v6
AS12389 ROSTELECOM-AS 2 20
v4
AS9957 KINX-AS-KR 2 19
v4
AS17686 ACCELIA 1 10
v4
AS137409 GSLNETWORKS-AS-AP 2 4
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS17961 in AS paths

Observed downstreams
Families
AS23777 VIPALETTE 264 692
v4 v6
AS10004 AS-PHOENIX-J 60 351
v4
AS18283 CCV 9 141
v4

No rows match “”.

Showing – of

Uncertain adjacencies

14 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 139
v4 v6
AS14907 WIKIMEDIA 5 77
v4 v6
AS18106 VIEWQWEST-SG-AP 5 77
v4 v6
AS1828 UNITAS 2 19
v4 v6
AS59105 HOMENOC 2 19
v4 v6
AS35280 F5 1 17
v4 v6
AS4777 APNIC-COLO 1 15
v4 v6
AS17639 CONVERGE-AS 1 15
v4 v6
AS36236 NETACTUATE 1 15
v4 v6
AS45489 SLT-GLOBAL 1 15
v4 v6
AS49544 i3Dnet 1 15
v4 v6
AS2500 WIDE-BB 1 14
v4
AS23777 VIPALETTE 1 4
v4
AS25152 K-ROOT-SERVER 1 3
v4 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.