Hello,
I’m experiencing consistently higher ping than usual when connecting to the JP servers from Australia (Aussie Broadband). Normally my latency is ~149 ms, but for the past several weeks it has been stuck around ~202 ms unless I use a VPN, which restores the normal latency.
This suggests a routing issue rather than a general ISP or hardware problem.
Without VPN (Aussie Broadband direct)
Tracing route to 119.252.36.6 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms [redacted private IP]
2 6 ms 5 ms 5 ms loop612451440.bng.sa.aussiebb.net [61.245.144.1]
3 23 ms 24 ms 24 ms 10.241.8.142
4 25 ms 25 ms 25 ms be3.lsr2.8gif.nsw.aussiebb.net [180.150.0.151]
5 26 ms 25 ms 25 ms be20.lsr2.200bou.nsw.aussiebb.net [159.196.252.106]
6 26 ms 27 ms 25 ms 10.241.12.113
7 * 140 ms 141 ms ae-13.r32.tokyjp05.jp.bb.gin.ntt.net [129.250.5.46]
8 151 ms 140 ms 149 ms ae-0.a02.tokyjp08.jp.bb.gin.ntt.net [129.250.5.199]
9 202 ms 202 ms 202 ms xe-0-5-0-3.a02.tokyjp08.jp.ce.gin.ntt.net [203.105.72.174]
10 203 ms 203 ms 203 ms 61.195.56.162
11 203 ms 203 ms 203 ms 219.117.144.82
12 203 ms 203 ms 203 ms 219.117.144.98
13 203 ms 202 ms 203 ms 119.252.36.6
With VPN (via alternate route)
Tracing route to 119.252.36.6 over a maximum of 30 hops
1 144 ms 144 ms 144 ms 10.2.0.1
2 164 ms 155 ms 145 ms irb-134.as03-10g.tyo1.jp.m247.ro [45.87.213.209]
3 * * * Request timed out.
4 145 ms 145 ms 146 ms ae102-3102.bb1.tyo1.jp.m247.ro [82.102.29.24]
5 145 ms 145 ms 146 ms 210.171.224.181
6 145 ms 145 ms 145 ms 133.208.191.149
7 145 ms 145 ms 145 ms 133.208.55.26
8 145 ms 145 ms 145 ms 219.117.144.86
9 145 ms 145 ms 145 ms 219.117.144.102
10 145 ms 145 ms 145 ms 119.252.36.6
Summary
Direct AussieBB → NTT path: Latency jumps from ~149 ms to ~202 ms inside NTT’s Tokyo backbone.
VPN path: Routes differently, stable at ~145–149 ms (expected AU → JP latency).
Issue seems specific to FFXIV routing through NTT.
Could you please investigate this routing issue or escalate to your upstream provider? Many Aussie players appear to be affected, and currently the only workaround is to use a VPN.
Thank you.
Continue reading...
I’m experiencing consistently higher ping than usual when connecting to the JP servers from Australia (Aussie Broadband). Normally my latency is ~149 ms, but for the past several weeks it has been stuck around ~202 ms unless I use a VPN, which restores the normal latency.
This suggests a routing issue rather than a general ISP or hardware problem.
Without VPN (Aussie Broadband direct)
Tracing route to 119.252.36.6 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms [redacted private IP]
2 6 ms 5 ms 5 ms loop612451440.bng.sa.aussiebb.net [61.245.144.1]
3 23 ms 24 ms 24 ms 10.241.8.142
4 25 ms 25 ms 25 ms be3.lsr2.8gif.nsw.aussiebb.net [180.150.0.151]
5 26 ms 25 ms 25 ms be20.lsr2.200bou.nsw.aussiebb.net [159.196.252.106]
6 26 ms 27 ms 25 ms 10.241.12.113
7 * 140 ms 141 ms ae-13.r32.tokyjp05.jp.bb.gin.ntt.net [129.250.5.46]
8 151 ms 140 ms 149 ms ae-0.a02.tokyjp08.jp.bb.gin.ntt.net [129.250.5.199]
9 202 ms 202 ms 202 ms xe-0-5-0-3.a02.tokyjp08.jp.ce.gin.ntt.net [203.105.72.174]
10 203 ms 203 ms 203 ms 61.195.56.162
11 203 ms 203 ms 203 ms 219.117.144.82
12 203 ms 203 ms 203 ms 219.117.144.98
13 203 ms 202 ms 203 ms 119.252.36.6
With VPN (via alternate route)
Tracing route to 119.252.36.6 over a maximum of 30 hops
1 144 ms 144 ms 144 ms 10.2.0.1
2 164 ms 155 ms 145 ms irb-134.as03-10g.tyo1.jp.m247.ro [45.87.213.209]
3 * * * Request timed out.
4 145 ms 145 ms 146 ms ae102-3102.bb1.tyo1.jp.m247.ro [82.102.29.24]
5 145 ms 145 ms 146 ms 210.171.224.181
6 145 ms 145 ms 145 ms 133.208.191.149
7 145 ms 145 ms 145 ms 133.208.55.26
8 145 ms 145 ms 145 ms 219.117.144.86
9 145 ms 145 ms 145 ms 219.117.144.102
10 145 ms 145 ms 145 ms 119.252.36.6
Summary
Direct AussieBB → NTT path: Latency jumps from ~149 ms to ~202 ms inside NTT’s Tokyo backbone.
VPN path: Routes differently, stable at ~145–149 ms (expected AU → JP latency).
Issue seems specific to FFXIV routing through NTT.
Could you please investigate this routing issue or escalate to your upstream provider? Many Aussie players appear to be affected, and currently the only workaround is to use a VPN.
Thank you.
Continue reading...