The HES IP that is supposed to be in Germany is showing that it is coming from the Japan region when using IP geolocation.
Here is a statement from HES management team explaining why HES EMEA IP shows that it is originating from the Japan Region:
"We are a Japanese company and we apply our IP block (220.127.116.11/16) from JPNIC (Japan Network Information Center, a semi-government agency) back in 2004, more than 10 years ago. After that, we started to roll out colocation sites in different countries, mainly in Japan, Taiwan, US and Germany (was also in UK but we closed that site).
By the time when we roll out HES EMEA datacenter in Germany, the Internet was already suffering from shortage of IP addresses. Since /16 is an extremely large block and according to the record, we were extremely underutilizing the existing /16 block. After consulting JPNIC, it was around 2007 that we split /16 into multiple smaller /20 block, and used them globally. However, the entire 150.70.x.x is still under JPNIC's supervision.
In short, we are using the same method like other big enterprises are doing, which is to split a big block into smaller ones and use them in different locations. However, from the operation, we specifically announced the HES EMEA datacenter in Germany IP block 18.104.22.168/20 from Germany only, that is used to ensure that the HES EMEA datacenter in Germany IP stays in HES EMEA datacenter in Germany, and that the German traffic stays in Germany. As shown on a traceroute from a German user, it takes less than 10 ms to reach the server in HES EMEA datacenter in Germany, that for sure is a domestic access and not International.
There is a plan to move HES EMEA Datacenter to AWS before the year ends and it will completely resolve this issue as we will now be using AWS EMEA IP's including AWS Frankfurt Datacenter (primary site) and the Ireland Datacenter (backup site)."
Here are the new IP ranges we will be using when we migrate to EMEA AWS: