Feedback Request on Network Delay

[Reika]

Dear all

We have successfully acquired a sizable amount of information concerning the network latency (lag) found to mainly occur during the Ifrit Battle thanks to all the feedback contributed by everyone up until today.
This will prove most helpful and we wish to thank you all for your valuable help.

Our development team is currently constructing a play environment that replicates the one everyone else using in order to investigate and test this ongoing issue.

We will be sure to inform everyone as soon as we discover any useful information.
For now however, we won't require any further feedback about tracert data.

Once again we would like to express our sincere thanks to everyone for their kind assistance.

Please note that we are not closing the thread so please feel free to continue posting about any lag you encounter during the Ifrit Battle, or indeed any other relevant concerns you would like to inform us about.

Thank you for your continuing support.

Once again.. the latency issue is not caused by the ifrit fight, the latency issue effects the ifrit fight. This same issue was present with the ogre fight, batraal fight, fights in totoruk, and every world NM fight. Levequests, Side-quests, crafting, gathering, skill timers, skill delay, etc. Its been around since day one, and it only became a really big issue because the ifrit fight is considerably harder than all the others, and the ongoing latency issue that has been present since day one will make ifrit and every other challenging battle you create from hereon out almost impossible for almost everyone not living in japan to complete without "help". I say that because connecting to a different country is undoubtedly going to continue causing this latency issue. I saw from my tracert that as soon as it started pinging routes in japan the pings skyrocketed. Unless you plan to make a direct connection to your servers and bypass all that other junk, or make servers in different countries, I think it will just continue and all hard content created will just give everyone more problems than necessary.

[Reika]

As I stated in a previous post, please understand this is not "mainly" ocurring in the Ifrit battle. This is ocurring everywhere. It's not as pronounced because getting hit by a regular monster's weapon skill is small potatoes compared to getting hit by Ifrit's stuff. Please understand that what you're dealing with here is an underlying issue with the way the client updates the server. Please do not just focus on the Ifrit battle - the position update latency is an issue that affects ALL battles.

Ah you beat me to it I hope they realize this.... or they wont fix anything.

[Laraul]

My internet is down... currently tethering my phone for connection...

Dustins-MacPro:~ dustin$ traceroute traceip.ffxiv.com
traceroute to traceip.ffxiv.com (202.67.52.81), 64 hops max, 52 byte packets
1 172.20.10.1 (172.20.10.1) 1.473 ms 1.549 ms 1.360 ms
2 172.26.236.2 (172.26.236.2) 176.590 ms 277.435 ms 317.497 ms
3 172.16.68.106 (172.16.68.106) 159.377 ms 253.986 ms 185.780 ms
4 172.16.69.177 (172.16.69.177) 159.901 ms 163.814 ms 275.506 ms
5 172.16.69.49 (172.16.69.49) 165.505 ms 156.173 ms 157.106 ms
6 172.16.75.5 (172.16.75.5) 161.986 ms
172.16.75.1 (172.16.75.1) 161.418 ms 155.346 ms
7 12.94.0.17 (12.94.0.17) 193.708 ms 245.983 ms
12.88.242.189 (12.88.242.189) 284.548 ms
8 cr1.dlstx.ip.att.net (12.122.139.38) 200.245 ms
cr1.santx.ip.att.net (12.123.236.6) 169.663 ms 179.938 ms
9 dlstx01jt.ip.att.net (12.122.80.41) 165.213 ms 159.293 ms
cr2.dlstx.ip.att.net (12.122.30.130) 174.589 ms
10 dlstx01jt.ip.att.net (12.122.80.101) 313.043 ms 167.917 ms 159.598 ms
11 ae-9.r01.dllstx04.us.bb.gin.ntt.net (129.250.8.237) 161.760 ms
ae-1.r21.dllstx09.us.bb.gin.ntt.net (129.250.2.198) 189.953 ms
ae-9.r01.dllstx04.us.bb.gin.ntt.net (129.250.8.237) 167.689 ms
12 ae-5.r20.lsanca03.us.bb.gin.ntt.net (129.250.2.168) 300.411 ms 326.945 ms
ae-1.r21.dllstx09.us.bb.gin.ntt.net (129.250.2.198) 172.354 ms
13 as-2.r20.osakjp01.jp.bb.gin.ntt.net (129.250.3.202) 378.399 ms
as-1.r21.osakjp01.jp.bb.gin.ntt.net (129.250.3.198) 277.363 ms
ae-4.r21.snjsca04.us.bb.gin.ntt.net (129.250.4.25) 187.993 ms
14 as-1.r21.osakjp01.jp.bb.gin.ntt.net (129.250.3.198) 334.393 ms
ae-1.r23.osakjp01.jp.bb.gin.ntt.net (129.250.2.49) 428.102 ms
as-0.r21.tokyjp01.jp.bb.gin.ntt.net (129.250.4.45) 350.464 ms
15 ae-2.r24.tokyjp01.jp.bb.gin.ntt.net (129.250.3.77) 432.931 ms 825.093 ms
ae-4.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.162) 316.225 ms
16 ae-4.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.162) 273.090 ms 251.350 ms
ae-5.r24.tokyjp01.jp.bb.gin.ntt.net (129.250.3.221) 268.283 ms
17 ae-5.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.170) 277.196 ms
ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net (61.120.146.94) 399.860 ms
ae-5.a20.tokyjp01.jp.ra.gin.ntt.net (61.213.162.170) 273.159 ms
18 ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net (61.120.146.94) 273.094 ms 279.307 ms 287.776 ms
19 219.117.146.149 (219.117.146.149) 264.120 ms
219.117.144.2 (219.117.144.2) 391.401 ms 643.276 ms
20 219.117.146.149 (219.117.146.149) 281.571 ms 301.889 ms
219.117.146.129 (219.117.146.129) 369.816 ms
21 219.117.146.129 (219.117.146.129) 345.204 ms 329.630 ms
202.67.52.81 (202.67.52.81) 316.645 ms

[Laraul]

Here we are with my standard internet connection...

ustins-MacPro:~ dustin$ traceroute traceip.ffxiv.com
traceroute to traceip.ffxiv.com (202.67.52.81), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.704 ms 0.399 ms 0.202 ms
2 10.245.40.1 (10.245.40.1) 8.920 ms 8.882 ms 8.881 ms
3 70.169.76.208 (70.169.76.208) 9.498 ms 11.109 ms 7.751 ms
4 70.169.73.18 (70.169.73.18) 15.222 ms
70.169.74.192 (70.169.74.192) 12.383 ms
chndcorc01-te-0-8-0-2.ph.ph.cox.net (70.169.72.60) 14.698 ms
5 chnddsrj01-ae2.0.rd.ph.cox.net (70.169.76.229) 12.449 ms 12.282 ms 13.937 ms
6 langbprj01-ae1.rd.la.cox.net (68.1.1.13) 38.724 ms 45.851 ms 38.575 ms
7 po15-1-0.cr1.nrt1.asianetcom.net (202.147.0.165) 138.410 ms 149.813 ms 140.837 ms
8 gi1-0-0.gw1.nrt5.asianetcom.net (202.147.0.178) 131.480 ms 130.991 ms 130.061 ms
9 squareco.asianetcom.net (203.192.149.210) 128.606 ms 130.519 ms 130.670 ms
10 61.195.56.129 (61.195.56.129) 146.456 ms 160.700 ms 149.680 ms
11 219.117.144.2 (219.117.144.2) 159.291 ms 159.398 ms 157.536 ms
12 219.117.146.149 (219.117.146.149) 158.340 ms 157.755 ms 157.764 ms
13 219.117.146.129 (219.117.146.129) 141.015 ms 143.150 ms 140.225 ms
14 219.117.146.38 (219.117.146.38) 145.130 ms 146.279 ms
219.117.146.46 (219.117.146.46) 159.483 ms
15 202.67.52.81 (202.67.52.81) 155.632 ms 156.985 ms 156.017 ms

[Asai]

1 <1 ms <1 ms <1 ms 192.168.1.1
2 18 ms 18 ms 21 ms 63.246.255.254.dynamic.musfiber.com [63.246.255.
254]
3 6 ms 3 ms 2 ms 192.168.200.9
4 2 ms 2 ms 2 ms 172.16.0.5
5 4 ms 8 ms 4 ms 205.232.68.165
6 16 ms 15 ms 15 ms ge-0-1-1-0-13.KNVLTN02W03CR02.paetec.net [169.13
0.102.90]
7 13 ms 13 ms 14 ms so-2-1-0.atlngamah66cr01.paetec.net [169.130.80.
13]
8 20 ms 13 ms 15 ms te-0-6-0-0-13.atlngamah66ig03.paetec.net [169.13
0.96.221]
9 * * * Request timed out.
10 33 ms 39 ms 33 ms 10gigabitethernet3-2.core1.dal1.he.net [184.105.
213.113]
11 53 ms 94 ms 52 ms 10gigabitethernet1-2.core1.phx1.he.net [72.52.92
.253]
12 68 ms 74 ms 74 ms 10gigabitethernet2-2.core1.lax1.he.net [72.52.92
.249]
13 76 ms 77 ms 76 ms pacnet.10gigabitethernet2-3.core1.lax1.he.net [2
16.218.223.206]
14 172 ms 172 ms 172 ms gi6-0-0.cr1.nrt1.asianetcom.net [202.147.61.166]

15 172 ms 172 ms 172 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

16 173 ms 173 ms 173 ms squareco.asianetcom.net [203.192.149.210]
17 187 ms 188 ms 233 ms 61.195.56.129
18 220 ms 207 ms 207 ms 219.117.144.2
19 188 ms 193 ms 188 ms 219.117.146.149
20 163 ms 163 ms 163 ms 219.117.146.129
21 170 ms 169 ms 171 ms 219.117.146.38
22 210 ms 207 ms 184 ms 202.67.52.81

[Dragonhaven]

So are we never going to see any fruit from this, im getting tired of dieing from plume and eruption im not standing on, on my screen and my wife's screen as we both have tracked our chrs and our LS members chrs in the ifrit battle getting hit when they are off of the dmg spots. Plume at 35% is the worst, Just asking so I know what we are paying for this month.

[Rhylee_Mau]

So are we never going to see any fruit from this, im getting tired of dieing from plume and eruption im not standing on, on my screen and my wife's screen as we both have tracked our chrs and our LS members chrs in the ifrit battle getting hit when they are off of the dmg spots. Plume at 35% is the worst, Just asking so I know what we are paying for this month.

IMO the most sensable way to go about this is change the way player's position is reported. That should help people with under 200ms lag. Every 3rd step position reporting really is annoying. The only way I could see for people in the 300ms range is actually adjust / design the fights now and in the future to allow for a 300ms delay and reaction time before exploding.

[Dragonhaven]

yup simple quick fix they seem to be avoiding

[Dragonhaven]

Can we get a reply as to when this issue will be fixed? Bahy? Rikki, Enkrateia, this is our LS's 1xxxx'th run with this issue killing us as plume goes off and everyone is safe we have even frapsed this issue for you and nothing seems to spark a reply.

[Kirei]

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

1 1 ms <1 ms 1 ms home [192.168.1.254]
2 24 ms 23 ms 23 ms adsl-98-68-157-1.cha.bellsouth.net [98.68.157.1]

3 27 ms 31 ms 31 ms 12.81.101.58
4 30 ms 31 ms 27 ms 12.81.32.96
5 41 ms 23 ms 25 ms 12.81.32.111
6 26 ms 23 ms 25 ms 74.175.192.138
7 40 ms 39 ms 41 ms cr1.nsvtn.ip.att.net [12.122.148.14]
8 43 ms 41 ms 37 ms cr2.attga.ip.att.net [12.122.28.105]
9 33 ms 33 ms 31 ms 12.122.117.121
10 34 ms 33 ms 33 ms 192.205.36.158
11 207 ms 206 ms 206 ms ae-6.r03.atlnga05.us.bb.gin.ntt.net [129.250.5.1
88]
12 60 ms 60 ms 59 ms ae-8.r21.dllstx09.us.bb.gin.ntt.net [129.250.3.9
1]
13 101 ms 100 ms 128 ms ae-4.r21.snjsca04.us.bb.gin.ntt.net [129.250.4.2
5]
14 206 ms 199 ms 206 ms as-0.r21.tokyjp01.jp.bb.gin.ntt.net [129.250.4.4
5]
15 198 ms 198 ms 208 ms ae-1.r25.tokyjp01.jp.bb.gin.ntt.net [129.250.2.7
3]
16 198 ms 297 ms 195 ms ae-5.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
170]
17 189 ms 190 ms 189 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
18 202 ms 206 ms 203 ms 219.117.144.2
19 191 ms 195 ms 191 ms 219.117.146.149
20 202 ms 194 ms 199 ms 219.117.146.129
21 201 ms 192 ms 204 ms 219.117.146.46
22 199 ms 201 ms 201 ms 202.67.52.81

Trace complete.