High ping on JP Servers [Please Help SE]

Dear SE,

Me and my friends are experiencing high ping/latency on one of the JP Server. Before the 2.1 maintenance everything is fine we have 50-80ms ping.. but after the update it increase 70-80% ping..

Doing Primals, Raid , Dungeons and even Gathering is a almost impossible with this high latency..

Using tracert :

Quote:

---

Used the IP taken from ARRSTATUS.COM "ASURA SERVER"

Tracing route to 124.150.157.29 over a maximum of 30 hops

1 1 ms <1 ms <1 ms unknown [10.0.1.1]
2 14 ms 14 ms 17 ms 112.200.128.1.pldt.net [112.200.128.1]
3 14 ms 15 ms 15 ms 122.2.135.177.pldt.net [122.2.135.177]
4 16 ms 14 ms 15 ms 210.213.131.70.static.pldt.net [210.213.131.70]

5 18 ms 18 ms 16 ms 210.213.128.33.static.pldt.net [210.213.128.33]

6 15 ms 13 ms 14 ms 210.213.130.141.static.pldt.net [210.213.130.141
]
7 219 ms 218 ms 219 ms p64-1-1-3.r20.snjsca04.us.bb.gin.ntt.net [140.17
4.21.177]
8 320 ms 333 ms 321 ms ae-4.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.7
]
9 326 ms 318 ms 348 ms ae-19.r25.tokyjp05.jp.bb.gin.ntt.net [129.250.6.
213]
10 * 315 ms 316 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
170]
11 315 ms 321 ms 320 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
12 319 ms 369 ms 319 ms 219.117.144.66
13 333 ms 318 ms 324 ms 219.117.144.53
14 335 ms 329 ms 333 ms 219.117.144.41
15 319 ms * 327 ms 219.117.147.194
16 319 ms 323 ms 333 ms 124.150.157.29

Trace complete.

---

We live in the Philippines, Our Internet speeds are normal.. Other MMO's we tried are working fine "Rift, DC Universe Online"..

Please fix this.. I know I'm not the majority but still this is an issue that needs to be resolve.

Thanks.

Almost all of the people that connect through PLDT are having the same problem, the root cause being is NTT Communications, their server is congested at the moment.

I tried to contact NTT and this is their reply

Dear Sir/Madame,

Thank you very much for contacting OCN Technical Service Center.
This is in regard to your inquiry we received from you by e-mail.

We checked the trace route result you forwarded and it seems
it does not go through OCN network.
Therefore it is difficult for OCN to investigate the problem in
details.

Please contact the administrators of the game server site
regarding this issue.


Thank you for your understanding and cooperation.


Sincerely,

*****

*OCN either deletes or replaces some information in your mail
with asterisks due to our complete privacy protection policy.


This is my route as well, I used to have around 60ms before, I'm on fiber optic line as well. I did try to contact PLDT but that didn't got me anywhere.

C:\Users\Stars>tracert 202.67.53.202

Tracing route to 202.67.53.202 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms 192.168.1.1
2 13 ms 19 ms 11 ms 112.209.32.1.pldt.net [112.209.32.1]
3 13 ms 13 ms 12 ms 119.93.255.213
4 14 ms 13 ms 13 ms 210.213.132.34.static.pldt.net [210.213.132.34]
5 13 ms 12 ms 14 ms 210.213.128.21.static.pldt.net [210.213.128.21]
6 12 ms 12 ms 12 ms 210.213.130.137.static.pldt.net [210.213.130.137]
7 178 ms 177 ms 202 ms p64-1-1-3.r20.snjsca04.us.bb.gin.ntt.net [140.174.21.177]
8 288 ms 306 ms 282 ms ae-4.r20.tokyjp05.jp.bb.gin.ntt.net [129.250.3.7]
9 362 ms 352 ms 362 ms ae-19.r25.tokyjp05.jp.bb.gin.ntt.net [129.250.6.213]
10 273 ms 278 ms 317 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.170]
11 281 ms 277 ms 275 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
12 288 ms 272 ms 274 ms 219.117.144.66
13 303 ms 299 ms 302 ms 219.117.144.45
14 278 ms 285 ms 283 ms 219.117.146.129
15 285 ms 280 ms 277 ms 219.117.146.102
16 353 ms 350 ms 341 ms 202.67.53.202

Trace complete.

Probably more to do with California in general--that whole corridor has been having issues for months now, and it doesn't seem to be isolated to just one ISP either. Could try notifying the admins at that hop where it all goes south. May not get much out of it, since they aren't your ISP, but if you still have your previous email available for a quick copy/paste, could try some of the contacts listed in their whois data:

http://myip.ms/info/whois/140.174.21.177

Ultimately though, it should be your ISP handling this, as it is someone they partner with to carry your data... but getting the details to the right person can be tricky. I seem to have better luck with TWC when I go through the admin's listed in their WhoIs or using their Forums--help desk people at the 866 number are virtually useless most of the time.

After several requests and follow ups on customer support with PLDT they finally are able to route the data directly to Japan, this is my current route ... a bigger improvement but is still not enough.

Check your route as well Heliosfiend, they were able to remove a hop. Hopefully we can see an improvement on NTT Comms end as well.

here is mine's:

tracert 202.67.53.202

Tracing route to 202.67.53.202 over a maximum of 30 hops

1 <1 ms 1 ms <1 ms 192.168.1.1
2 21 ms 12 ms 12 ms 112.209.0.1.pldt.net [112.209.0.1]
3 12 ms 11 ms 13 ms 119.93.255.213
4 15 ms 13 ms 13 ms 210.213.132.34.static.pldt.net [210.213.132.34]
5 12 ms 13 ms 12 ms 210.213.128.53.static.pldt.net [210.213.128.53]
6 12 ms 12 ms 13 ms 210.213.133.17.static.pldt.net [210.213.133.17]
7 169 ms 170 ms 168 ms 61.120.144.197
8 190 ms 206 ms 280 ms ae-13.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.3.240]
9 188 ms 200 ms 183 ms ae-4.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.162]
10 187 ms 188 ms 187 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
11 195 ms 190 ms 189 ms 219.117.144.66
12 189 ms 189 ms 189 ms 219.117.144.53
13 190 ms 190 ms 189 ms 219.117.146.141
14 192 ms 192 ms 191 ms 219.117.146.106
15 190 ms 183 ms 193 ms 202.67.53.202

Trace complete.

This is mine for tonberry servers.. other pldt subscribers are routed differently.. some still retain the old 60ms latency.. ill try to get you a traceroute for it

Tracing route to 124.150.157.21 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 13 ms 13 ms 17 ms 49.144.160.1
3 12 ms 14 ms 13 ms 122.2.135.25
4 15 ms 16 ms 15 ms 210.213.133.70
5 14 ms 13 ms 12 ms 210.213.133.17
6 181 ms 181 ms 179 ms 61.120.144.197
7 164 ms 168 ms 168 ms 129.250.3.240
8 163 ms 164 ms 163 ms 61.213.162.170
9 165 ms 163 ms 164 ms 61.120.146.94
10 170 ms 169 ms 170 ms 219.117.144.66
11 166 ms 165 ms 164 ms 219.117.144.45
12 180 ms 180 ms 186 ms 219.117.144.29
13 169 ms 170 ms 169 ms 219.117.147.186
14 169 ms 169 ms 168 ms 124.150.157.21

from friend

1 2 ms 1 ms 21 ms 192.168.1.1
2 18 ms 19 ms 35 ms 112.208.32.1.pldt.net [112.208.32.1]
3 31 ms 19 ms 19 ms 119.93.255.197
4 51 ms 22 ms 32 ms 210.213.131.70.static.pldt.net [210.213.131.70]

5 20 ms 18 ms 32 ms 210.213.128.65.static.pldt.net [210.213.128.65]

6 17 ms 25 ms 49 ms 210.213.133.21.static.pldt.net [210.213.133.21]

7 72 ms 59 ms 75 ms 61.120.144.197
8 77 ms 95 ms 136 ms ae-13.r24.tokyjp05.jp.bb.gin.ntt.net [129.250.3.
240]
9 157 ms 133 ms 65 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
170]
10 63 ms 95 ms 87 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
11 60 ms 70 ms 59 ms 219.117.144.66
12 97 ms 74 ms 59 ms 219.117.144.45
13 92 ms 60 ms 61 ms 219.117.144.29
14 59 ms 68 ms 59 ms 219.117.147.186
15 71 ms 59 ms 78 ms 124.150.157.30

After following up again with PLDT they were able to reduce the latency to nominal. If you guys are still having issues with your connection I would suggests you requests PLDT to have your line re-wired from the PLDT cabinets to your PC using only one cable not multiple ones stiched together. It made a huge difference when I had mine rewired.

Here is my current latency on PLDT fibr:

Tracert 202.67.53.202

Tracing route to 202.67.53.202 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms . [192.168.2.1]
2 25 ms 29 ms 25 ms 112.209.64.1.pldt.net [112.209.64.1]
3 25 ms 25 ms 25 ms 119.93.255.209
4 27 ms 26 ms 26 ms 210.213.132.26.static.pldt.net [210.213.132.26]
5 26 ms 26 ms 27 ms 210.213.128.57.static.pldt.net [210.213.128.57]
6 25 ms 25 ms 45 ms 210.213.133.17.static.pldt.net [210.213.133.17]
7 66 ms 65 ms 65 ms 61.120.144.197
8 66 ms 68 ms 99 ms ae-14.r25.tokyjp05.jp.bb.gin.ntt.net [129.250.3.242]
9 66 ms 66 ms 65 ms ae-4.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.162]
10 66 ms 66 ms 78 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
11 65 ms 66 ms 66 ms 219.117.144.66
12 66 ms 66 ms 66 ms 219.117.144.53
13 66 ms 66 ms 66 ms 219.117.146.141
14 67 ms 67 ms 67 ms 219.117.146.106
15 66 ms 66 ms 66 ms 202.67.53.202

Trace complete.

If you guys are on regular DSL lines the latency should be around 90-130ms and primal extreme fights should still be do-able.