Intermittently high (>300ms) latency on JP servers reverse-proxied by Cloudflare for new instances

Normally, playing on Japan servers, I get ~38ms latency.


This league, there's about 50% chance that location/map instance gets created on a server I have ~300ms latency with.


Using TCPView [1], shows that "good" server IPs are from 38.57.39.0/24 subnet (ASN 137409) or 165.192.64.0/18 (ASN 36351) [2].
$ ping 38.57.39.2 -c 1
PING 38.57.39.2 (38.57.39.2) 56(84) bytes of data.
64 bytes from 38.57.39.2: icmp_seq=1 ttl=55 time=36.7 ms
$ ping 165.192.75.205 -c 1
PING 165.192.75.205 (165.192.75.205) 56(84) bytes of data.
64 bytes from 165.192.75.205: icmp_seq=1 ttl=53 time=36.2 ms

While "bad" ones are Cloudflare IPs from 172.65.176.0/20 (ASN 13335 - CLOUDFLARENET, US).
$ ping 172.65.191.39 -c 1
PING 172.65.191.39 (172.65.191.39) 56(84) bytes of data.
64 bytes from 172.65.191.39: icmp_seq=1 ttl=57 time=59.7 ms

The thing is - I only have 60ms ICMP ping to those. Tha't's decently fast, but the game shows latency over 300ms.
So those are probably CF reverse proxies, and the 240ms difference is the latency between the reverse proxy and the server it actually connects to.

Since it's behind CF - there's nothing I or my ISP could do to optimize routes on the player side.

Those IPs should not be in the pool.
--------------------------------------------------------------------------------
[1] - https://learn.microsoft.com/en-us/sysinternals/downloads/tcpview
[2] - https://hackertarget.com/as-ip-lookup/