11 replies to this topic

[Jon Cunningham]

Currently NTT misroutes traffic to our online game. We're having trouble persuading them to change their route.

Please email your support or contact them and complain that playing games on their network is slow.

If you have the ability, please also send them a tracert and a ping to our server addresses at 192.99.109.192 and 192.99.40.103.

More technically, the details are this:

NTT chooses to use our Seabone peer to get to our datacenter rather than the other peer, Level3. The problem is transiting to Seabone means going to Singapore first, then Miami, rather than straight across the pacific.

This adds more than 50+ ms to the trip.

Please forward this to your friends using NTT as well so they are aware of the issues.

And if anyone in Japan *doesn't* use NTT, I'd love to see your ping speed to our server. I expect NTT would also be interested to see if their competitors perform better.

[Kageru Ikazuchi]

I use J:Com, and get about 200 ping pretty consistently.

tracert results in the spoiler ...

Spoiler

C:\Windows\system32>tracert 192.99.109.192

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 <1 ms 3 ms <1 ms 192.168.1.1
2 11 ms 32 ms 12 ms 42-148-8-1.rev.home.ne.jp [42.148.8.1]
3 10 ms 10 ms 10 ms 10.202.99.3
4 35 ms 18 ms 15 ms 10.1.0.45
5 15 ms 15 ms 30 ms 203-165-18-205.rev.home.ne.jp [203.165.18.205]
6 17 ms 14 ms 14 ms c1-t0-1-0-2.ot-dc.zaq.ad.jp [203.165.18.206]
7 12 ms 16 ms 37 ms 124.211.14.13
8 27 ms 26 ms 12 ms otejbb205.int-gw.kddi.ne.jp [118.155.197.1]
9 113 ms 120 ms 163 ms pajbb001.int-gw.kddi.ne.jp [203.181.100.134]
10 132 ms 128 ms 126 ms ix-pa8.int-gw.kddi.ne.jp [111.87.3.6]
11 113 ms 114 ms 130 ms 198.27.73.33
12 * 163 ms * 198.27.73.188
13 192 ms 173 ms 185 ms mtl-1-6k.qc.ca [198.27.73.183]
14 203 ms 203 ms 207 ms bhs-g2-6k.qc.ca [198.27.73.3]
15 196 ms * 181 ms 198.27.73.233
16 174 ms 174 ms 174 ms mwomercs.com [192.99.109.192]

Trace complete.

C:\Windows\system32>tracert 192.99.40.103

Tracing route to ns7000224.ip-192-99-40.net [192.99.40.103]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 192.168.1.1
2 9 ms 13 ms 9 ms 42-148-8-1.rev.home.ne.jp [42.148.8.1]
3 8 ms 10 ms 10 ms 10.202.99.4
4 13 ms 17 ms 11 ms 10.1.0.41
5 13 ms 14 ms 14 ms 203-165-18-201.rev.home.ne.jp [203.165.18.201]
6 14 ms 11 ms 14 ms c2-t0-1-0-2.ot-dc.zaq.ad.jp [203.165.18.202]
7 14 ms 13 ms 14 ms c1-t0-1-0-6.ot-dc.zaq.ad.jp [220.152.42.229]
8 14 ms 14 ms 15 ms 124.211.14.13
9 15 ms 14 ms 14 ms otejbb205.int-gw.kddi.ne.jp [118.155.197.129]
10 123 ms 129 ms 131 ms pajbb001.int-gw.kddi.ne.jp [203.181.100.138]
11 135 ms 122 ms 123 ms ix-pa8.int-gw.kddi.ne.jp [111.87.3.6]
12 119 ms 122 ms 131 ms 198.27.73.33
13 * * * Request timed out.
14 192 ms 243 ms 177 ms 198.27.73.175
15 184 ms 191 ms 186 ms bhs-g1-6k.qc.ca [198.27.73.1]
16 177 ms 178 ms 178 ms bhs-s4-6k.qc.ca [198.27.73.144]
17 185 ms 186 ms 185 ms ns7000224.ip-192-99-40.net [192.99.40.103]

Trace complete.

Edited by Kageru Ikazuchi, 11 December 2014 - 12:40 AM.

[jawa]

My ISP is OCN (This ISP is provided by NTT Communications Corporation)

Tracert 192.99.109.192

Spoiler

mwomercs.com [192.99.109.192] へのルートをトレースしています
経由するホップ数は最大 30 です:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 12 ms 11 ms 10 ms 122.28.24.38
3 18 ms 20 ms 19 ms 122.28.24.62
4 18 ms 20 ms 11 ms 221.184.12.221
5 25 ms 7 ms 12 ms 122.28.168.89
6 8 ms 8 ms 8 ms 118.23.168.89
7 9 ms 11 ms 12 ms ae-5.r21.tokyjp05.jp.bb.gin.ntt.net [129.250.11.53]
8 8 ms 7 ms 7 ms ae-0.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.6.96]
9 97 ms 114 ms 91 ms ae-3.r21.sngpsi05.sg.bb.gin.ntt.net [129.250.7.35]
10 82 ms 82 ms 82 ms ae-13.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.4.74]
11 * 88 ms * ae0.singapore2.sin.seabone.net [93.186.133.12]
12 265 ms 271 ms 271 ms xe-1-2-0.miami15.mia.seabone.net [195.22.199.193]
13 271 ms 269 ms 271 ms xe-1-3-1.miami15.mia.seabone.net [89.221.41.9]
14 298 ms 288 ms 287 ms mia-1-6k.fl.us [178.32.135.208]
15 * * * 要求がタイムアウトしました。
16 299 ms 300 ms 290 ms bhs-g1-6k.qc.ca [198.27.73.205]
17 293 ms 299 ms 292 ms 198.27.73.231
18 285 ms 284 ms 284 ms mwomercs.com [192.99.109.192]

トレースを完了しました

Tracert 192.99.40.103

Spoiler

ns7000224.ip-192-99-40.net [192.99.40.103] へのルートをトレースしています
経由するホップ数は最大 30 です:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 5 ms 8 ms 122.28.24.38
3 15 ms 10 ms 6 ms 122.28.24.62
4 10 ms 9 ms 9 ms 221.184.12.221
5 8 ms 9 ms 16 ms 122.28.168.89
6 11 ms 11 ms 7 ms 60.37.27.153
7 11 ms 7 ms 6 ms ae-5.r21.tokyjp05.jp.bb.gin.ntt.net [129.250.11.53]
8 7 ms 7 ms 10 ms ae-0.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.6.96]
9 73 ms 72 ms 72 ms ae-3.r21.sngpsi05.sg.bb.gin.ntt.net [129.250.7.35]
10 72 ms 80 ms 75 ms ae-13.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.4.74]
11 76 ms 75 ms 73 ms ae0.singapore2.sin.seabone.net [93.186.133.12]
12 267 ms 264 ms 260 ms xe-1-2-3.miami15.mia.seabone.net [195.22.199.109]
13 258 ms * 258 ms xe-1-2-3.miami15.mia.seabone.net [195.22.199.109]
14 276 ms 303 ms 281 ms mia-1-6k.fl.us [178.32.135.208]
15 * * * 要求がタイムアウトしました。
16 294 ms 282 ms 281 ms bhs-g1-6k.qc.ca [198.27.73.205]
17 286 ms 281 ms 283 ms bhs-s3-6k.qc.ca [198.27.73.140]
18 286 ms 278 ms 278 ms ns7000224.ip-192-99-40.net [192.99.40.103]

トレースを完了しました。

[Jon Cunningham]

Jawa, would you mind making a complaint to OCN? Especially considering the speeds Kageru gets with J:COM?

[Binbo Gami]

I made a complaint about this 2 or 3 weeks ago to ntt and my provider. my tracert no longer goes through Europe but there is no improvement at all.

[Assault One]

Hello, semi-related question here. I play from the Philippines and I usually get 250-300 ping and I can play with that. Some days however, I get 400+ to 900+ ping. Today is one of those days. However, i did a ping and tracert of the two ip addresses above.

ping and tracert for 192.99.109.192: http://img.photobuck...zps60fe370c.png

ping and tracert for 192.99.40.103: http://img.photobuck...zpsfe85c02f.png

What's weird is that it shows my regular range of ping rather than the unplayable 400+. Any idea why this happens?

[-FROST-]

Thank you for finally looking into this issue. I'm on NTT in Japan and have been having latency issues since the November 2013 patch. The game is unplayable for me unless I play behind a vpn. Getting NTT to change may be difficult - everything is so rigid here.

[jawa]

I inquired of OCN this problem.
But OCN is saying a problem of setting of PGI's ISP.
I don't know whether it's true.

[General Solo]

I don't live in japan but had a similar problem playing from Australia. I tested several sites in Montreal Canada to see if there was any difference depending on the sites ISP in Canada. Hope it gives you some ideas and helps you gather evidence.

http://mwomercs.com/...25#entry3794425

Edited by OZHomerOZ, 24 December 2014 - 03:33 AM.

[ice trey]

I am through NTT Japan.

I have already contacted them before. Actually, before contacting PGI about the issue. They politely brushed me off.

:"Sore wa muzukashii desu ne~!"
Translators note: This means "We're not lifting a damned finger"

I already sent a message to you guys about this. I suggested a staff member who could speak Japanese... possibly one of the higher ranking ones, could speak to them, as that seems to be the only way to get anyone to help you in this country.

In fact, though I couldn't make out half of the sonkeigo/technobabble they were telling me at 300 words per minute, NTT East told me that it was something on PGI's end that needed to be fixed.

[jawa]

I can't play MWO.
Communication state has become worse than before .
high ping value & Packet loss.

Tracert

Spoiler

mwomercs.com [192.99.109.192] へのルートをトレースしています
経由するホップ数は最大 30 です:

1 <1 ms <1 ms <1 ms ntt.setup [192.168.1.1]
2 5 ms 6 ms 5 ms 122.28.24.38
3 7 ms 6 ms 6 ms 122.28.24.62
4 8 ms 8 ms 9 ms 221.184.12.221
5 6 ms 6 ms 6 ms 122.28.168.89
6 6 ms 6 ms 6 ms 118.23.168.89
7 13 ms 7 ms 7 ms ae-5.r21.tokyjp05.jp.bb.gin.ntt.net [129.250.11.53]
8 7 ms 9 ms 8 ms ae-0.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.6.96]
9 81 ms 75 ms 81 ms ae-3.r21.sngpsi05.sg.bb.gin.ntt.net [129.250.7.35]
10 73 ms 73 ms 76 ms ae-13.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.4.74]
11 75 ms 74 ms 73 ms ae0.singapore2.sin.seabone.net [93.186.133.12]
12 330 ms 333 ms 325 ms xe-2-0-3.milano51.mil.seabone.net [195.22.205.109]
13 329 ms * * mil-1-6k.it.eu [91.121.131.25]
14 * 333 ms * fra-1-6k.de.eu [213.251.128.66]
15 339 ms 337 ms 338 ms sbg-g1-a9.fr.eu [91.121.128.80]
16 * 340 ms 343 ms 37.187.36.153
17 * * * 要求がタイムアウトしました。
18 333 ms 322 ms 329 ms mwomercs.com [192.99.109.192]

トレースを完了しました。

PING

Spoiler

mwomercs.com [192.99.109.192]に ping を送信しています 32 バイトのデータ:
192.99.109.192 からの応答: バイト数 =32 時間 =329ms TTL=49
192.99.109.192 からの応答: バイト数 =32 時間 =328ms TTL=49
要求がタイムアウトしました。
要求がタイムアウトしました。

192.99.109.192 の ping 統計:
パケット数: 送信 = 4、受信 = 2、損失 = 2 (50% の損失)、
ラウンド トリップの概算時間 (ミリ秒):
最小 = 328ms、最大 = 329ms、平均 = 328ms

[Binbo Gami]

Going through Europe again it seems

Spoiler

Tracing route to mwomercs.com [192.99.109.192]
over a maximum of 30 hops:

1 13 ms 159 ms 7 ms 192.168.1.1
2 9 ms 7 ms 8 ms 118.23.61.227
3 6 ms 7 ms 5 ms 118.23.53.113
4 11 ms 8 ms 7 ms 118.23.88.85
5 6 ms 7 ms 5 ms 61.207.46.45
6 14 ms 16 ms 13 ms 125.170.96.45
7 19 ms 17 ms 16 ms 61.207.4.5
8 18 ms 112 ms 36 ms ae-5.r21.osakjp02.jp.bb.gin.ntt.net [129.250.11.
173]
9 17 ms 16 ms 37 ms ae-5.r22.osakjp02.jp.bb.gin.ntt.net [129.250.6.1
92]
10 88 ms 86 ms 87 ms ae-8.r20.sngpsi05.sg.bb.gin.ntt.net [129.250.3.1
10]
11 89 ms 87 ms 88 ms ae-2.r00.sngpsi02.sg.bb.gin.ntt.net [129.250.3.1
47]
12 88 ms 87 ms 88 ms ae0.singapore2.sin.seabone.net [93.186.133.12]
13 314 ms 308 ms 315 ms xe-0-0-0.milano51.mil.seabone.net [195.22.196.13
5]
14 * * * Request timed out.
15 * * 292 ms fra-1-6k.de.eu [213.251.128.66]
16 345 ms 330 ms 306 ms rbx-s11-6k.fr.eu [91.121.131.250]
17 300 ms 359 ms 305 ms 37.187.36.153
18 * * * Request timed out.
19 318 ms 313 ms 306 ms mwomercs.com [192.99.109.192]

Trace complete.

Edited by Binbo Gami, 08 January 2015 - 04:21 PM.