Feedback Request on Network Delay

[Atomisk]

Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 2 ms 1 ms 1 ms
3 693 ms 641 ms 603 ms 99-129-232-3.lightspeed.milwwi.sbcglobal.net [99
.129.232.3]
4 629 ms 617 ms 661 ms 71.144.192.58
5 * * * Request timed out.
6 * * * Request timed out.
7 23 ms 21 ms 22 ms bb2.10g5-0.milwwi.sbcglobal.net [151.164.43.203]

8 38 ms 73 ms 75 ms ppp-151-164-55-178.eulstx.swbell.net [151.164.55
.178]
9 29 ms 25 ms 29 ms as2914-ntt.eqchil.sbcglobal.net [151.164.251.114
]
10 26 ms 26 ms 32 ms ae-7.r20.chcgil09.us.bb.gin.ntt.net [129.250.4.1
45]
11 32 ms 25 ms 25 ms ae-0.r21.chcgil09.us.bb.gin.ntt.net [129.250.3.9
8]
12 98 ms 76 ms 81 ms ae-5.r20.snjsca04.us.bb.gin.ntt.net [129.250.3.1
07]
13 226 ms 191 ms 181 ms as-2.r20.tokyjp01.jp.bb.gin.ntt.net [129.250.2.3
5]
14 203 ms 270 ms 180 ms ae-1.r24.tokyjp01.jp.bb.gin.ntt.net [129.250.2.2
1]
15 187 ms 192 ms 183 ms ae-4.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
162]
16 171 ms 177 ms 178 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
17 195 ms 184 ms 195 ms 219.117.144.2
18 206 ms 205 ms 206 ms 219.117.146.149
19 187 ms 176 ms 183 ms 219.117.146.129
20 194 ms 220 ms 186 ms 219.117.146.38
21 372 ms 317 ms 225 ms 202.67.52.81

Trace complete.

[Cale_Imrik]

Date & Time: Oct 31st 12:20pm
ISP: Telstra Bigpond
Type and Speed: ADSL2 7-10mbps (says up to 20, but I call bullshit)
Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 74 ms 99 ms 99 ms BigPond.BigPond [10.0.0.138]
2 29 ms 28 ms 28 ms 172.18.210.21
3 29 ms 28 ms 28 ms 172.18.68.162
4 28 ms 27 ms 28 ms 172.18.240.14
5 32 ms 31 ms 31 ms 172.18.240.9
6 29 ms 31 ms 31 ms Bundle-Ether10.win18.Melbourne.telstra.net [203.45.17.37]
7 37 ms 35 ms 34 ms Bundle-Ether2.win-core1.Melbourne.telstra.net [203.50.6.113]
8 41 ms 39 ms 39 ms Pos0-0-0-0.fli-core1.Adelaide.telstra.net [203.50.6.186]
9 43 ms 41 ms 41 ms TenGigE0-8-0-5-1.way-core4.Adelaide.telstra.net [203.50.6.10]
10 74 ms 73 ms 74 ms Bundle-Pos2.pie-core1.Perth.telstra.net [203.50.11.17]
11 71 ms 71 ms 71 ms GigabitEthernet1-1.pthp-core01.Perth.net.reach.com [203.50.13.242]
12 117 ms 117 ms 116 ms i-5-0-1.6ntp-core01.bx.reach.com [202.84.141.66]
13 120 ms 119 ms 119 ms i-1-0-1.6ntp01.bi.reach.com [202.84.180.142]
14 124 ms 124 ms 122 ms 202.79.197.7
15 182 ms 181 ms 181 ms 217.239.40.154
16 189 ms 177 ms 177 ms 80.150.170.106
17 176 ms 178 ms 176 ms 61.195.56.133
18 178 ms 178 ms 177 ms 219.117.144.6
19 177 ms 178 ms 180 ms 219.117.146.153
20 216 ms 216 ms 216 ms 219.117.146.141
21 178 ms 181 ms 181 ms 219.117.146.42
22 205 ms 204 ms 204 ms 202.67.52.81

Trace complete.


Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 81 ms 99 ms 99 ms BigPond.BigPond [10.0.0.138]
2 29 ms 29 ms 29 ms 172.18.210.21
3 28 ms 27 ms 28 ms 172.18.68.162
4 28 ms 29 ms 28 ms 172.18.240.14
5 30 ms 30 ms 31 ms 172.18.240.9
6 30 ms 30 ms 31 ms Bundle-Ether10.win18.Melbourne.telstra.net [203.45.17.37]
7 35 ms 35 ms 36 ms Bundle-Ether2.win-core1.Melbourne.telstra.net [203.50.6.113]
8 40 ms 39 ms 40 ms Pos0-0-0-0.fli-core1.Adelaide.telstra.net [203.50.6.186]
9 42 ms 41 ms 41 ms TenGigE0-8-0-5-1.way-core4.Adelaide.telstra.net [203.50.6.10]
10 74 ms 75 ms 74 ms Bundle-Pos2.pie-core1.Perth.telstra.net [203.50.11.17]
11 71 ms 71 ms 71 ms GigabitEthernet1-1.pthp-core01.Perth.net.reach.com [203.50.13.242]
12 118 ms 117 ms 117 ms i-5-0-1.6ntp-core01.bx.reach.com [202.84.141.66]
13 119 ms 119 ms 119 ms i-1-0-1.6ntp01.bi.reach.com [202.84.180.142]
14 122 ms 125 ms 123 ms 202.79.197.7
15 179 ms 179 ms 179 ms 217.239.40.154
16 176 ms 177 ms 177 ms 80.150.170.106
17 181 ms 181 ms 177 ms 61.195.56.133
18 179 ms 178 ms 179 ms 219.117.144.6
19 178 ms 179 ms 178 ms 219.117.146.153
20 217 ms 217 ms 215 ms 219.117.146.141
21 181 ms 183 ms 179 ms 219.117.146.42
22 205 ms 203 ms 206 ms 202.67.52.81

Trace complete.

[Gath]

The server to client relationship has only very little to do with what is happening. It is due to crappy design that makes it like this. There is one server, and it is in Japan. For information to go from my computer to the server, back to my computer to see a single plume, makes it crappy. Looking at peoples IPs and whatnot won't do anything. This should be shown in the game logs.

[Bahn]

The server to client relationship has only very little to do with what is happening. It is due to crappy design that makes it like this. There is one server, and it is in Japan. For information to go from my computer to the server, back to my computer to see a single plume, makes it crappy. Looking at peoples IPs and whatnot won't do anything. This should be shown in the game logs.

I disagree. Several knowledgeable players with network experience pointed out in another thread that it's definitely not the latency from the West to the Japanese servers that's causing it, but simply a poorly coded client. If I had the video I would link it, but basically the client isn't updating the server often enough on position changes. The latency has nothing to do with this. If a person goes from point 1 to point 10, for example, the client only tells the server when the player goes from point 1, 4, 7, and 10 (I'm using a very, very simple and dumbed down example so give me a break on this). If I have to be at point 8 to dodge an attack for example, the client doesn't tell the server "in time" that I managed to dodge an attack because the client fails to tell the server about what I'm doing at points 8 and 9; the server just thinks I moved from 7 to 10 only when I actually reach position 10 - for all intents and purposes the server thinks I'm still at position 7 when I visually see my character moving from 7 to 8, 9, and 10.

The latency would just cause me to move at a slightly later time, but if the server/client architecture was properly made like every other MMO where the client continuously updates the server on positions, I should still be able to move out of the way of an attack - I might have to move a little bit earlier, yes, but there wouldn't be these silly things where you're CLEARLY out of the way of the attack yet you still get hit.

It's much harder to spot this badly made architecture when a person is moving in a straight line (because for all intents and purposes, visually you would see other players always moving in one direction, so it can be "masked"), but when you have to sidestep/move out of the way of attacks which causes your x and y positions to change and not just one or the other, it's very easy to see.

[rbrogue]

Date & Time - 10/31/2011 15:33 CST
Internet Service Provider - Time Warner Cable
Network type and speed - 30Mb(down) 5Mb(up) Cable

Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 <1 ms <1 ms <1 ms 192.168.0.2
2 14 ms 21 ms 13 ms 10.77.31.1
3 13 ms 16 ms 11 ms tge1-8.snantx1000-er03.texas.rr.com [24.28.133.00]
4 28 ms 23 ms 47 ms tengig0-0-0-2.snantx6000-rtr1.satx.rr.com [24.2.133.4]
5 19 ms 22 ms 35 ms ae23.dllatxl3-cr01.texas.rr.com [72.179.205.8]
6 23 ms 16 ms 33 ms 107.14.17.136
7 62 ms 66 ms 77 ms ae-3-0.cr0.lax30.tbone.rr.com [66.109.6.0]
8 101 ms 65 ms 87 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
9 87 ms 59 ms 59 ms pacnet.com.any2ix.coresite.com [206.223.143.138

10 169 ms 165 ms 161 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]

11 164 ms 168 ms 166 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

12 170 ms 167 ms 160 ms squareco.asianetcom.net [203.192.149.210]
13 179 ms 163 ms 169 ms 61.195.56.129
14 162 ms 171 ms 167 ms 219.117.144.2
15 168 ms 161 ms 169 ms 219.117.146.149
16 160 ms 168 ms 166 ms 219.117.146.129
17 196 ms 188 ms 174 ms 219.117.146.46
18 165 ms 168 ms 164 ms 202.67.52.81

Trace complete.

[DoomCky]

Date & Time: 12:35 AM EST 10/31/2011
Internet Service Provider: RCN
Network Type and Speed: Cable 60 Mbs/6MBs
Global IP (optional): just say eastern PA
tracert Result:

C:\Users\Admin>tracert -h 50 traceip.ffxiv.com
Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 3 ms 3 ms 2 ms bdl1.tlg-ubr2.atw-tlg.pa.cable.rcn.net [10.50.96
.1]
3 4 ms 5 ms 5 ms vl4.aggr1.phdl.pa.rcn.net [208.59.252.1]
4 22 ms 95 ms 84 ms tge1-1.core4.phdl.pa.rcn.net [207.172.15.39]
5 164 ms 203 ms 204 ms tge2-4.core4.nyw.ny.rcn.net [207.172.19.229]
6 8 ms 8 ms 7 ms port-chan1.border1.nyw.ny.rcn.net [207.172.15.76
]
7 70 ms 69 ms 69 ms eqix-ny.pacnet.com [198.32.118.162]
8 176 ms 175 ms 175 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]
9 175 ms 175 ms 175 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
10 182 ms 176 ms 168 ms squareco.asianetcom.net [203.192.149.210]
11 178 ms 178 ms 198 ms 61.195.56.129
12 193 ms 193 ms 193 ms 219.117.144.2
13 180 ms 170 ms 171 ms 219.117.146.149
14 176 ms 175 ms 175 ms 219.117.146.129
15 173 ms 171 ms 171 ms 219.117.146.38
16 170 ms 169 ms 170 ms 202.67.52.81
Trace complete.

[Jinrya-Geki]

Date: Oct 31, 2011 3:31 am EST
Internet Service Provider: Verizon


Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 1 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 6 ms 7 ms L100.BSTNMA-VFTTP-92.verizon-gni.net [98.118.39.
1]
3 9 ms 8 ms 9 ms G2-0-892.BSTNMA-LCR-08.verizon-gni.net [130.81.1
10.26]
4 9 ms 13 ms 31 ms so-0-3-0-0.BOS-BB-RTR2.verizon-gni.net [130.81.2
9.254]
5 21 ms 19 ms 21 ms xe-4-1-0-0.NY325-BB-RTR2.verizon-gni.net [130.81
.23.255]
6 32 ms 20 ms 21 ms 0.ae2.BR3.NYC4.ALTER.NET [152.63.16.49]
7 28 ms 20 ms 19 ms xe-0-2-0-6.r06.nycmny01.us.bb.gin.ntt.net [129.2
50.9.77]
8 21 ms 21 ms 22 ms ae-2.r22.nycmny01.us.bb.gin.ntt.net [129.250.4.1
74]
9 111 ms 103 ms 104 ms ae-4.r21.sttlwa01.us.bb.gin.ntt.net [129.250.2.5
1]
10 123 ms 104 ms 104 ms ae-0.r20.sttlwa01.us.bb.gin.ntt.net [129.250.2.5
3]
11 209 ms 216 ms 231 ms as-3.r20.tokyjp01.jp.bb.gin.ntt.net [129.250.4.1
90]
12 213 ms 231 ms 264 ms ae-1.r24.tokyjp01.jp.bb.gin.ntt.net [129.250.2.2
1]
13 193 ms 217 ms 206 ms ae-4.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
162]
14 222 ms 222 ms 226 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
15 233 ms 219 ms 234 ms 219.117.144.2
16 233 ms 233 ms 238 ms 219.117.146.149
17 228 ms 214 ms 220 ms 219.117.146.129
18 242 ms 222 ms 239 ms 219.117.146.38
19 206 ms 228 ms 221 ms 202.67.52.81

[Steggun]

Date: 10/29/2011 8:45PM CST, 9:25PM CST, 10:51PM CST, 11:50PM CST and many others
ISP: Time Warner
Network: Cable, 10Mbps

Tracert:

Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 6 ms 6 ms Removed
3 7 ms 6 ms 8 ms gig3-10.milwwismil-swt401.wi.rr.com [24.160.229.
4]
4 7 ms 7 ms 8 ms tge0-1-0-5.milwwirtco-asr1.wi.rr.com [24.160.230
.38]
5 10 ms 9 ms 10 ms tge1-1-0.tr00.chctilwc.mwrtn.rr.com [24.160.229.
193]
6 8 ms 10 ms 9 ms ae-6-0.cr0.chi30.tbone.rr.com [66.109.6.206]
7 30 ms 32 ms 31 ms ae-6-0.cr0.dca20.tbone.rr.com [66.109.10.0]
8 32 ms 35 ms 32 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
9 31 ms 31 ms 33 ms 80.150.171.13
10 196 ms 204 ms 196 ms 217.239.40.154
11 184 ms 184 ms 182 ms 80.150.170.106
12 184 ms 183 ms 183 ms 61.195.56.133
13 187 ms 183 ms 183 ms 219.117.144.6
14 182 ms 183 ms 183 ms 219.117.146.153
15 183 ms 183 ms 184 ms 219.117.146.141
16 189 ms 194 ms 188 ms 219.117.146.50
17 187 ms 187 ms 189 ms 202.67.52.81

Trace complete.


Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 5 ms 5 ms 7 ms Removed
3 8 ms 6 ms 5 ms gig3-10.milwwismil-swt401.wi.rr.com [24.160.229.
4]
4 7 ms 7 ms 8 ms tge0-1-0-5.milwwirtco-asr1.wi.rr.com [24.160.230
.38]
5 9 ms 9 ms 10 ms tge1-1-0.tr00.chctilwc.mwrtn.rr.com [24.160.229.
193]
6 9 ms 8 ms 9 ms ae-6-0.cr0.chi30.tbone.rr.com [66.109.6.206]
7 31 ms 32 ms 31 ms ae-6-0.cr0.dca20.tbone.rr.com [66.109.10.0]
8 31 ms 31 ms 31 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
9 31 ms 31 ms 38 ms 80.150.171.13
10 193 ms 193 ms 194 ms 217.239.40.154
11 182 ms 183 ms 183 ms 80.150.170.106
12 185 ms 183 ms 185 ms 61.195.56.133
13 187 ms 183 ms 184 ms 219.117.144.6
14 194 ms 183 ms 183 ms 219.117.146.153
15 184 ms 185 ms 182 ms 219.117.146.141
16 188 ms 186 ms 190 ms 219.117.146.50
17 188 ms 187 ms 186 ms 202.67.52.81

Trace complete.

[totallynotme]

From Sweden, with problems on Ifrit.

31/10/2011 10:10PM GMT
ISP: Com Hem AB
100 (down) / 10 (up) Fiber

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Med ensamrätt.

tracert -h 50 traceip.ffxiv.com

Tracing route to traceip.ffxiv.com [202.67.52.81]
over max. 50 jumps:

1 8 ms 10 ms 9 ms c83-253-168-1.bredband.comhem.se [83.253.168.1]

2 9 ms 10 ms 11 ms 83.255.242.242
3 16 ms 13 ms 13 ms nap-bb-r-02-to-ksn-bbr-1.comhem.se [83.255.252.6
]
4 15 ms 14 ms 13 ms 83.255.232.0
5 23 ms 24 ms 15 ms 10gigabitethernet1-2.core1.sto1.he.net [195.245.
240.187]
6 48 ms 49 ms 50 ms 10gigabitethernet3-3.core1.fra1.he.net [72.52.92
.233]
7 49 ms 47 ms 50 ms 10gigabitethernet1-4.core1.par2.he.net [184.105.
213.162]
8 127 ms 140 ms 127 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.
213.93]
9 * * * Request timed out.
10 201 ms 191 ms 188 ms 10gigabitethernet5-3.core1.lax1.he.net [72.52.92
.226]
11 199 ms 193 ms 191 ms pacnet.10gigabitethernet2-3.core1.lax1.he.net [2
16.218.223.206]
12 299 ms 297 ms 297 ms gi6-0-0.cr1.nrt1.asianetcom.net [202.147.61.166]
13 297 ms 297 ms 300 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
14 297 ms 297 ms 297 ms squareco.asianetcom.net [203.192.149.210]
15 314 ms 315 ms 314 ms 61.195.56.129
16 306 ms 306 ms 305 ms 219.117.144.2
17 308 ms 309 ms 319 ms 219.117.146.149
18 312 ms 306 ms 306 ms 219.117.146.129
19 390 ms 311 ms 406 ms 219.117.146.46
20 309 ms 313 ms 315 ms 202.67.52.81

Trace complete.

[HiirNoivl]

•October 31st 6:47 AM
•Broadband Cable from Insight
•10 Megabit LAN
•tracert Result*

Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 5 ms 6 ms 11 ms 74-129-0-1.dhcp.insightbb.com [74.130.0.1]
2 8 ms 7 ms 8 ms 74-128-16-225.dhcp.insightbb.com [74.128.16.225]

3 104 ms 206 ms 211 ms 74.128.8.233
4 36 ms 34 ms 37 ms sl-gw25-atl-13-0-0.sprintlink.net [144.232.212.2
49]
5 36 ms 40 ms 37 ms sl-crs2-atl-0-5-3-0.sprintlink.net [144.232.22.1
3]
6 37 ms 36 ms 34 ms sl-crs4-atl-0-11-2-0.sprintlink.net [144.232.4.7
5]
7 38 ms 37 ms 40 ms sl-crs4-fw-0-3-0-2.sprintlink.net [144.232.18.14
9]
8 39 ms 38 ms 38 ms sl-crs2-fw-0-7-0-0.sprintlink.net [144.232.1.46]

9 71 ms 70 ms 72 ms sl-crs2-ria-0-0-0-0.sprintlink.net [144.232.8.15
4]
10 70 ms 71 ms 74 ms sl-crs2-ana-0-12-2-0.sprintlink.net [144.232.20.
158]
11 76 ms 71 ms 77 ms sl-st21-la-13-0-0.sprintlink.net [144.232.20.69]

12 67 ms 69 ms 71 ms sl-asian-19137-0.sprintlink.net [144.223.44.22]

13 167 ms 168 ms 170 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]

14 166 ms 167 ms 170 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

15 166 ms 166 ms 167 ms squareco.asianetcom.net [203.192.149.210]
16 184 ms 182 ms 182 ms 61.195.56.129
17 162 ms 160 ms 159 ms 219.117.144.2
18 170 ms 169 ms 170 ms 219.117.146.149
19 173 ms 177 ms 172 ms 219.117.146.129
20 176 ms 171 ms 172 ms 219.117.146.46
21 174 ms 174 ms 172 ms 202.67.52.81

Trace complete.