Latency problems on Japan realm

Hi!
Recently ive expirienced latency problems on Japan realm.

WinMRT trace
https://pastebin.com/zAxpmZwn

Ive contacted my ISP and they said that this problem isnt on their side.

I cant be sure whats the problem, since on log in screen latency is normal (87ms), but as soon as i log in - all instances i create (maps/hideout) are 400ms ping (also Oriath town too).

I live in Far East Russia, Moscow realm is like 120ms ping for me.

I wonder why connection to tok-m.speedtest.pathofexile.com goes via Frankfurt and USA, like making whole circle around the world to connect.

"

fataleast wrote:

Hi!
Recently ive expirienced latency problems on Japan realm.

WinMRT trace
https://pastebin.com/zAxpmZwn

Ive contacted my ISP and they said that this problem isnt on their side.

I cant be sure whats the problem, since on log in screen latency is normal (87ms), but as soon as i log in - all instances i create (maps/hideout) are 400ms ping (also Oriath town too).

I live in Far East Russia, Moscow realm is like 120ms ping for me.

I wonder why connection to tok-m.speedtest.pathofexile.com goes via Frankfurt and USA, like making whole circle around the world to connect.

I've been reporting this for several days now, no response as yet. I'll Probaly send an email to support today.

"

Fitzy_GGG wrote:

It looks like your ISP is peering through Europe rather than through a more direct route to get outside of Russia. You will need to raise this with their support.

I think there might be intentional changes on their end to prefer peering and routing through Russian infrastructure, which is unfortunately in the west.

Hi Fitzy.

I emailed support with some additional details, however, to yopur point here. The route keeps changing depending upon instance. Login is fine and the route/latency is correct. It's when changing instances that the route changes.

Also:

tracert www.bbix.net (Tokyo IX)

Tracing route to www.bbix.net [103.120.84.42]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms bashful.home.arpa [192.168.255.254]
2 4 ms 3 ms 3 ms 10.251.14.125
3 2 ms 2 ms 2 ms 10.251.14.126
4 35 ms 35 ms 35 ms 87.226.133.15
5 35 ms 35 ms 35 ms 218.100.7.31
6 36 ms 35 ms 35 ms 103.120.84.28
7 35 ms 35 ms 35 ms 103.120.84.42

tracert tok.speedtest.pathofexile.com

Tracing route to speedtest.tok02.softlayer.com [161.202.125.20]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms bashful.home.arpa [192.168.255.254]
2 3 ms 3 ms 3 ms 10.251.14.127
3 7 ms 2 ms 2 ms 10.251.14.124
4 35 ms 35 ms 35 ms 87.226.133.15
5 34 ms 34 ms 34 ms 218.100.6.65
6 38 ms 35 ms 35 ms ae5.cbs02.eq01.tok01.networklayer.com [169.45.19.160]
7 36 ms 36 ms 36 ms 5a.10.35a9.ip4.static.sl-reverse.com [169.53.16.90]
8 35 ms 35 ms 35 ms 89.76.85a2.ip4.static.sl-reverse.com [162.133.118.137]
9 36 ms 36 ms 36 ms cd.76.85a2.ip4.static.sl-reverse.com [162.133.118.205]
10 34 ms 35 ms 34 ms speedtest.tok02.softlayer.com [161.202.125.20]

Trace complete.


This only started when Korea came online.

Edit: as discovered at the beginning of last league, your Google Cloud servers are routed through Moscow and back but this is not that.

Edit: for what its worth BGP Equinix, BBIX and JPNAP as direct peers.

"

Fitzy_GGG wrote:

I've asked our host to see if they can get any info.

The Korean launch was coincidentally at the same when we were increasing the Japan realm's capacity for the Legion launch. The new capacity is with our new hosting partner, which would have made this problem more apparent.

I need to update the target that displays the latency at the login screen, since it's not going to be accurate anymore.

The login screen still shows ~35ms which is what I get on first login.

|-------------------------------------------------------------------|

| WinMTR statistics |

|Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|-------------------------|------|------|------|------|------|------|

| 192.168.255.254 - 0 | 501 | 501 | 0 | 0 | 1 | 0 |

| 10.251.14.121 - 0 | 501 | 501 | 3 | 3 | 5 | 4 |

| 10.251.14.120 - 0 | 501 | 501 | 2 | 2 | 21 | 2 |

| 87.226.133.15 - 0 | 501 | 501 | 35 | 35 | 60 | 35 |

| 218.100.6.65 - 0 | 501 | 501 | 35 | 35 | 57 | 42 |

| 169.45.19.160 - 16 | 309 | 260 | 36 | 37 | 69 | 36 |

| 169.53.16.88 - 0 | 501 | 501 | 37 | 38 | 69 | 38 |

| 162.133.118.135 - 0 | 501 | 501 | 36 | 36 | 55 | 36 |

| 162.133.118.211 - 0 | 501 | 501 | 36 | 36 | 71 | 36 |

| 161.202.101.39 - 0 | 501 | 501 | 35 | 35 | 37 | 35 |

|_________________________|______|______|______|______|______|______|

WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

"

Fitzy_GGG wrote:

Yes - I expect this to be the case. The gateway is relatively empty at the moment, so you're being put on to one of the few servers on the other route.

If the new hosting partner is PSYCHZ-NETWORKS the routes I'm getting when changing instances are all through their servers.

172.107.201.54 - ~200ms+
103.102.160.198 - ~200ms+
43.251.181.130 - ~80ms

I hope I'm wrong about this but if PSYCHZ-NETWORKS are your new hosting partners they don't seem to peer with any East coast RU providers and from what I can see the only RU peers are in the West, which means all traffic from East Russia, because of your new provider, will not actually go to Japan but to the USA?

Terrific!

You've updated the routes for your new provider and now the login screen shows 200ms+! Couldn't you have found a provider that doesn't need to go West to go East!