Feedback Request on Network Delay

[Ilean]

Oct 30 2011 8:38 AM CST
Prodigy
ADSL 7mbps/2mbps


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.254
2 18 ms 21 ms 21 ms HIDDEN
3 70 ms 52 ms 52 ms bb-dallas-stemmons-4-pos0-13-3-0.uninet.net.mx [201.125.6.1]
4 69 ms 70 ms 66 ms xe-0-4-0-5.r08.dllstx09.us.bb.gin.ntt.net [157.238.224.129]
5 68 ms 80 ms 74 ms ae-6.r21.dllstx09.us.bb.gin.ntt.net [129.250.3.80]
6 77 ms 97 ms 79 ms ae-4.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.25]
7 180 ms 178 ms 190 ms as-1.r21.osakjp01.jp.bb.gin.ntt.net [129.250.3.198]
8 188 ms 178 ms 180 ms ae-2.r23.osakjp01.jp.bb.gin.ntt.net [129.250.2.71]
9 214 ms 196 ms 196 ms ae-5.r25.tokyjp01.jp.bb.gin.ntt.net [129.250.3.223]
10 184 ms 188 ms 198 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.170]
11 221 ms 202 ms 198 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
12 197 ms 190 ms 194 ms 219.117.144.2
13 204 ms 196 ms 204 ms 219.117.146.149
14 194 ms 194 ms 196 ms 219.117.146.129
15 190 ms 202 ms 190 ms 219.117.146.38
16 196 ms 198 ms 196 ms 202.67.52.81


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.254
2 23 ms 21 ms 19 ms HIDDEN
3 53 ms 52 ms 54 ms bb-dallas-stemmons-4-pos0-13-3-0.uninet.net.mx [201.125.6.1]
4 67 ms 67 ms 70 ms xe-0-4-0-5.r08.dllstx09.us.bb.gin.ntt.net [157.238.224.129]
5 90 ms 70 ms 72 ms ae-6.r21.dllstx09.us.bb.gin.ntt.net [129.250.3.80]
6 75 ms 78 ms 78 ms ae-4.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.25]
7 179 ms 180 ms 186 ms as-1.r21.osakjp01.jp.bb.gin.ntt.net [129.250.3.198]
8 190 ms 235 ms 286 ms ae-2.r23.osakjp01.jp.bb.gin.ntt.net [129.250.2.71]
9 204 ms 237 ms 312 ms ae-5.r25.tokyjp01.jp.bb.gin.ntt.net [129.250.3.223]
10 180 ms 200 ms 178 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.170]
11 208 ms 194 ms 198 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
12 194 ms 188 ms 193 ms 219.117.144.2
13 196 ms 204 ms 196 ms 219.117.146.149
14 186 ms 190 ms 186 ms 219.117.146.129
15 192 ms 200 ms 196 ms 219.117.146.38
16 186 ms 188 ms 194 ms 202.67.52.81


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.254
2 19 ms 21 ms 21 ms HIDDEN
3 53 ms 54 ms 52 ms bb-dallas-stemmons-4-pos0-13-3-0.uninet.net.mx [201.125.6.1]
4 67 ms 70 ms 68 ms xe-0-4-0-5.r08.dllstx09.us.bb.gin.ntt.net [157.238.224.129]
5 91 ms 69 ms 70 ms ae-6.r21.dllstx09.us.bb.gin.ntt.net [129.250.3.80]
6 78 ms 78 ms 79 ms ae-4.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.25]
7 181 ms 190 ms 186 ms as-1.r21.osakjp01.jp.bb.gin.ntt.net [129.250.3.198]
8 192 ms 207 ms 188 ms ae-2.r23.osakjp01.jp.bb.gin.ntt.net [129.250.2.71]
9 230 ms 194 ms 249 ms ae-5.r25.tokyjp01.jp.bb.gin.ntt.net [129.250.3.223]
10 179 ms 192 ms 198 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.170]
11 195 ms 196 ms 204 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
12 188 ms 188 ms 188 ms 219.117.144.2
13 193 ms 196 ms 196 ms 219.117.146.149
14 195 ms 196 ms 188 ms 219.117.146.129
15 192 ms 192 ms 204 ms 219.117.146.38
16 187 ms 188 ms 198 ms 202.67.52.81


My connection is VERY stable and usually rated between B+ and A by pingtest.net

[RathSkybreaker]

This was in grid,

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 6 ms 9 ms 8 ms 10.31.144.1
3 7 ms 7 ms 7 ms wsip-24-249-37-229.br.br.cox.net [24.249.37.229]

4 10 ms 10 ms 9 ms btnrdsrc02-pos0801.br.br.cox.net [24.249.36.185]

5 13 ms 15 ms 13 ms btnrdsrj02-ge210.0.rd.br.cox.net [24.249.36.209]

6 22 ms 22 ms 23 ms 68.1.2.109
7 67 ms 66 ms 69 ms ae-5.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.1
68]
8 170 ms 169 ms 168 ms as-2.r20.osakjp01.jp.bb.gin.ntt.net [129.250.3.2
02]
9 178 ms 178 ms 229 ms ae-1.r23.osakjp01.jp.bb.gin.ntt.net [129.250.2.4
9]
10 244 ms 184 ms 186 ms ae-5.r25.tokyjp01.jp.bb.gin.ntt.net [129.250.3.2
23]
11 187 ms 215 ms 185 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
170]
12 194 ms 187 ms 185 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
13 179 ms 185 ms 182 ms 219.117.144.2
14 190 ms 187 ms 193 ms 219.117.146.149
15 174 ms 174 ms 177 ms 219.117.146.129
16 171 ms 172 ms 170 ms 219.117.146.46
17 174 ms 177 ms 180 ms 202.67.52.81

Trace complete.

[Reika]

Oct 30, 1030 - 1035
Comcast Cable
55mbit Cable

Trace 1:

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

1 8 ms 9 ms 7 ms 10.0.128.1
2 9 ms 10 ms 10 ms COX-68-12-10-228-static.coxinet.net [68.12.10.228]
3 35 ms 8 ms 9 ms COX-68-12-8-48-static.coxinet.net [68.12.8.48]
4 9 ms 12 ms 11 ms mtc3dsrj01-ae4.0.rd.ok.cox.net [68.12.14.0]
5 13 ms 65 ms 15 ms 68.1.2.109
6 92 ms 56 ms 64 ms ae-5.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.168]
7 166 ms 162 ms 168 ms as-2.r20.osakjp01.jp.bb.gin.ntt.net [129.250.3.202]
8 216 ms 183 ms 188 ms ae-1.r23.osakjp01.jp.bb.gin.ntt.net [129.250.2.49]
9 275 ms 171 ms 165 ms ae-5.r25.tokyjp01.jp.bb.gin.ntt.net [129.250.3.223]
10 178 ms 201 ms 183 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.170]
11 183 ms 179 ms 185 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
12 183 ms 187 ms 177 ms 219.117.144.2
13 164 ms 168 ms 171 ms 219.117.146.149
14 163 ms 173 ms 166 ms 219.117.146.129
15 177 ms 178 ms 176 ms 219.117.146.46
16 170 ms 182 ms 186 ms 202.67.52.81

Trace complete.
-----------------------

Trace 2

-----------------------

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

1 9 ms 7 ms 9 ms 10.0.128.1
2 11 ms 15 ms 10 ms COX-68-12-10-228-static.coxinet.net [68.12.10.228]
3 9 ms 11 ms 17 ms COX-68-12-8-48-static.coxinet.net [68.12.8.48]
4 10 ms 11 ms 9 ms mtc3dsrj01-ae4.0.rd.ok.cox.net [68.12.14.0]
5 92 ms 17 ms 15 ms 68.1.2.109
6 62 ms 56 ms 76 ms ae-5.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.168]
7 172 ms 157 ms 160 ms as-2.r20.osakjp01.jp.bb.gin.ntt.net [129.250.3.202]
8 188 ms 161 ms 243 ms ae-1.r23.osakjp01.jp.bb.gin.ntt.net [129.250.2.49]
9 186 ms 211 ms 251 ms ae-5.r25.tokyjp01.jp.bb.gin.ntt.net [129.250.3.223]
10 179 ms 196 ms 181 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.170]
11 187 ms 176 ms 177 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
12 193 ms 185 ms 182 ms 219.117.144.2
13 167 ms 166 ms 160 ms 219.117.146.149
14 174 ms 168 ms 169 ms 219.117.146.129
15 182 ms 201 ms 177 ms 219.117.146.46
16 176 ms 166 ms 158 ms 202.67.52.81

Trace complete.
-------------------------------------

And Trace 3

-------------------------------------

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

1 12 ms 6 ms 7 ms 10.0.128.1
2 11 ms 8 ms 10 ms COX-68-12-10-228-static.coxinet.net [68.12.10.228]
3 12 ms 7 ms 10 ms COX-68-12-8-48-static.coxinet.net [68.12.8.48]
4 7 ms 13 ms 11 ms mtc3dsrj01-ae4.0.rd.ok.cox.net [68.12.14.0]
5 17 ms 15 ms 13 ms 68.1.2.109
6 67 ms 58 ms 60 ms ae-5.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.168]
7 160 ms 160 ms 159 ms as-2.r20.osakjp01.jp.bb.gin.ntt.net [129.250.3.202]
8 248 ms 181 ms 168 ms ae-1.r23.osakjp01.jp.bb.gin.ntt.net [129.250.2.49]
9 172 ms 177 ms 166 ms ae-5.r25.tokyjp01.jp.bb.gin.ntt.net [129.250.3.223]
10 182 ms 174 ms 186 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.170]
11 260 ms 185 ms 180 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
12 179 ms 177 ms 189 ms 219.117.144.2
13 174 ms 170 ms 170 ms 219.117.146.149
14 195 ms 174 ms 161 ms 219.117.146.129
15 186 ms 188 ms 181 ms 219.117.146.46
16 174 ms 177 ms 172 ms 202.67.52.81

Trace complete.

------

I see an issue starting at #5... This is in the morning. I will do another 3 in the afternoon, evening, and night.

I will also note that for me the latency issue is not just with ifrit fight. it is for every game action, whether it be battle or gathering.

[Jinko]

30/10/11 @ 16:35
British Telecom (BT)
ADSL 2Mbps

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

1 1 ms <1 ms <1 ms BTHomeHub.home [192.168.1.254]
2 53 ms 35 ms 30 ms 217.47.107.250
3 35 ms 32 ms 31 ms 217.47.107.145
4 54 ms 34 ms 36 ms 213.1.69.122
5 36 ms 36 ms 40 ms 213.120.179.58
6 36 ms 36 ms 38 ms 213.120.179.182
7 36 ms 35 ms 36 ms 109.159.251.229
8 42 ms 40 ms 47 ms core1-te0-13-0-2.ilford.ukcore.bt.net [109.159.251.137]
9 43 ms 43 ms 44 ms peer2-xe9-0-0.telehouse.ukcore.bt.net [109.159.254.126]
10 47 ms 44 ms 93 ms 195.99.126.129
11 386 ms 274 ms 266 ms te7-4.losangeles1.loa.seabone.net [89.221.35.146]
12 255 ms 258 ms 256 ms pacnet.losangeles1.loa.seabone.net [89.221.35.186]
13 353 ms 348 ms 346 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]
14 343 ms 347 ms 345 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
15 350 ms 351 ms 354 ms squareco.asianetcom.net [203.192.149.210]
16 356 ms 356 ms 354 ms 61.195.56.129
17 357 ms 355 ms 354 ms 219.117.144.2
18 352 ms 351 ms 346 ms 219.117.146.149
19 364 ms 362 ms 361 ms 219.117.146.129
20 359 ms 356 ms 355 ms 219.117.146.46
21 358 ms 369 ms 357 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 BTHomeHub.home [192.168.1.254]
2 39 ms 33 ms 29 ms 217.47.107.250
3 29 ms 30 ms 28 ms 217.47.107.145
4 40 ms 39 ms 35 ms 213.1.69.122
5 37 ms 37 ms 37 ms 213.120.179.58
6 36 ms 38 ms 37 ms 213.120.179.182
7 36 ms 39 ms 35 ms 109.159.251.229
8 44 ms 43 ms 43 ms core1-te0-13-0-2.ilford.ukcore.bt.net [109.159.251.137]
9 75 ms 44 ms 45 ms peer2-xe9-0-0.telehouse.ukcore.bt.net [109.159.254.126]
10 45 ms 44 ms 47 ms 195.99.126.129
11 241 ms 238 ms 239 ms te7-4.losangeles1.loa.seabone.net [89.221.35.146]
12 245 ms 244 ms 249 ms pacnet.losangeles1.loa.seabone.net [89.221.35.186]
13 345 ms 347 ms 347 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]
14 340 ms 337 ms 338 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
15 337 ms 343 ms 341 ms squareco.asianetcom.net [203.192.149.210]
16 348 ms 340 ms 337 ms 61.195.56.129
17 356 ms 355 ms 355 ms 219.117.144.2
18 342 ms 342 ms 342 ms 219.117.146.149
19 376 ms 358 ms 359 ms 219.117.146.129
20 359 ms 360 ms 360 ms 219.117.146.46
21 358 ms 359 ms * 202.67.52.81
22 359 ms 358 ms 359 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 BTHomeHub.home [192.168.1.254]
2 31 ms 29 ms 30 ms 217.47.107.250
3 30 ms 31 ms 30 ms 217.47.107.145
4 35 ms 35 ms 36 ms 213.1.69.122
5 36 ms 36 ms 36 ms 213.120.179.58
6 35 ms 35 ms 35 ms 213.120.179.182
7 38 ms 35 ms 36 ms 109.159.251.229
8 41 ms 43 ms 62 ms core1-te0-13-0-2.ilford.ukcore.bt.net [109.159.251.137]
9 47 ms 44 ms 47 ms peer2-xe9-0-0.telehouse.ukcore.bt.net [109.159.254.126]
10 43 ms 44 ms 46 ms 195.99.126.129
11 318 ms 319 ms 337 ms te7-4.losangeles1.loa.seabone.net [89.221.35.146]
12 234 ms 236 ms 235 ms pacnet.losangeles1.loa.seabone.net [89.221.35.186]
13 342 ms 339 ms 345 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]
14 335 ms 333 ms 333 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
15 336 ms 330 ms 332 ms squareco.asianetcom.net [203.192.149.210]
16 337 ms 335 ms 333 ms 61.195.56.129
17 * 354 ms 350 ms 219.117.144.2
18 340 ms 341 ms 336 ms 219.117.146.149
19 356 ms 356 ms 373 ms 219.117.146.129
20 357 ms 352 ms * 219.117.146.46
21 357 ms 358 ms 354 ms 202.67.52.81

Trace complete.

[DantesAmore]

YA... i wont be posting all that BS... i run a 7 MBPS net and i still have the animation lag during this fight ... a plume or crack will post and i'll run like 14feet off of it and BOOM i'm still hit EVERY FIGHT dont matter the day or time it happens. granted i've now adapted to setting a timer in RL to ding every 15sec in preps for his abilities so i can dodge them >.> but REALLY the lag sucks ass.

[Jinko]

YA... i wont be posting all that BS... i run a 7 MBPS net and i still have the animation lag during this fight ... a plume or crack will post and i'll run like 14feet off of it and BOOM i'm still hit EVERY FIGHT dont matter the day or time it happens. granted i've now adapted to setting a timer in RL to ding every 15sec in preps for his abilities so i can dodge them >.> but REALLY the lag sucks ass.

7 Mbps has nothing to do with latency, you should post to help the dev team improve the game.

[Fear]

Internet speed has nothing to do with your latency or ping, that is delt with by your distance to the server.

UK to Japan gets roughly a 300ms latency or ping, UK to US roughly 130 and if I speed test on a server 50 miles from me I get 24-35ms

[Zarvlad]

Date & Time : October 30th 2011 16:59
Internet Service Provider : Videotron
Network Type and Speed: Cable 15Mbps


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

1 <1 ms <1 ms <1 ms ZARVLAD [192.168.1.1]
2 6 ms 5 ms 5 ms 10.50.40.1
3 7 ms 9 ms 6 ms 10.170.162.65
4 8 ms 7 ms 7 ms 216.113.123.233
5 26 ms 25 ms 25 ms 216.113.122.58
6 94 ms 92 ms 93 ms gw3.lax1.asianetcom.net [206.223.115.40]
7 198 ms 199 ms 198 ms gi6-0-0.cr1.nrt1.asianetcom.net [202.147.61.166]
8 191 ms 194 ms 192 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
9 201 ms 201 ms 201 ms squareco.asianetcom.net [203.192.149.210]
10 191 ms 192 ms 192 ms 61.195.56.129
11 194 ms 193 ms 192 ms 219.117.144.2
12 199 ms 199 ms 199 ms 219.117.146.149
13 199 ms 199 ms 199 ms 219.117.146.129
14 192 ms 192 ms 192 ms 219.117.146.38
15 193 ms 191 ms 195 ms 202.67.52.81

Trace complete.

[Bahn]

SE_James, I would like to say it's less of an issue with the server, and more an issue with the client. Someone posted a vid awhile back showing that the client doesn't update the server often enough on position changes. The inability to avoid attacks is not only evident on the Ifrit fight, but in ALL types of fights where you try to side step an attack to dodge something.

The vid I saw was someone who was playing FFXIV on two separate computers. He had one character continuously run around the other in a circle. The character that was circling saw obviously a smooth run around the one being circled. However, the character being circled saw the character pretty much start/stopping at certain points of the circle - almost creating a square shape sort of run.

The person in question concluded that the client/server architecture simply isn't updating each other often enough with position updates. What we see is NOT what we get. This is pretty evident when you get hit by knockback attacks. You can actually still do WSes (even though you're VISUALLY far away from the mob) for a good 3-5 seconds before the server realizes you're far away from the mob.

But yeah, I think it's something with your architecture that's causing this. All you really need to do is make the client update the server more often on position updates so this doesn't happen. The reason why everyone is complaining about it on the Ifrit fight is because of how often it's done and how much it SUCKS if you can't dodge it. It's much more noticeable to try to dodge something like that and get hit by it than dodging a random leveling monster's weaponskill.

[Vuitton]

Date & Time : October 30th 2011 18:01
Internet Service Provider : Comcast
Network Type and Speed: Cable 15Mbps

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

1 * * * Request timed out.
2 23 ms 11 ms 8 ms te-0-0-0-8-ur10.beaverton.or.bverton.comcast.net [68.85.149.153]
3 14 ms 9 ms 10 ms ae-3-0-ar03.troutdale.or.bverton.comcast.net [68.85.243.165]
4 22 ms 20 ms 18 ms pos-2-0-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.95.89]
5 23 ms 25 ms 58 ms pos-0-10-0-0-cr01.portland.or.ibone.comcast.net[68.86.85.106]
6 26 ms 39 ms 26 ms pos-1-15-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.197]
7 29 ms 31 ms 55 ms pos-0-7-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.46]
8 30 ms 33 ms 41 ms pos-0-1-0-0-pe01.529bryant.ca.ibone.comcast.net[68.86.87.2]
9 60 ms 42 ms 36 ms 80.156.163.153
10 166 ms 137 ms 161 ms 217.239.40.154
11 187 ms 164 ms 137 ms 80.150.170.106
12 134 ms 162 ms 135 ms 61.195.56.133
13 138 ms 165 ms 161 ms 219.117.144.6
14 166 ms 173 ms 135 ms 219.117.146.153
15 170 ms 158 ms 141 ms 219.117.146.141
16 143 ms 135 ms 149 ms 219.117.146.50
17 159 ms 135 ms 168 ms 202.67.52.81

Trace complete.