Feedback Request on Network Delay

Wanted to first ask why this topic is still sticked?

---

Quote:

---

Originally Posted by Rentahamster

Hm, that would explain the same crappy connection to Japan that my Hawaii friends have too when we play Street Fighter 4. I would have thought that they'd have better ping since they're closer. I wonder if there's anyway around this that doesn't involve SE having to work with the ISP directly to get the dynamic routing changed somehow.

---

Look at the first hop. It's over 300 ms. I live in the "lower 48" and my ping to that first hop (cpe-66-91-168-1.hawaii.res.rr.com) is less than 80 ms. So I don't understand how if he actually lives in Hawaii has a ping three times greater than mine.

I think I am the laggiest player in this game even though I have an 8Mbps connection.

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

1 <1 ms <1 ms <1 ms Router-Home [172.29.208.74]
2 2 ms 1 ms 1 ms 213.189.74.1
3 * * * Request timed out.
4 1 ms 2 ms 1 ms 10.10.40.2
5 2 ms 2 ms 1 ms 172.16.33.2
6 1 ms 1 ms 1 ms 172.16.33.5
7 * * * Request timed out.
8 131 ms 129 ms 129 ms 195.50.120.45
9 140 ms 131 ms 143 ms ae-52-52.csw2.London1.Level3.net [4.69.139.120]

10 138 ms 129 ms 129 ms ae-56-221.ebr2.London1.Level3.net [4.69.153.129]

11 198 ms 200 ms 199 ms ae-43-43.ebr1.NewYork1.Level3.net [4.69.137.74]

12 208 ms 207 ms 208 ms ae-10-10.ebr2.Washington12.Level3.net [4.69.148.
50]
13 209 ms 209 ms 214 ms ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
14 221 ms 209 ms 217 ms ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
15 211 ms 210 ms 211 ms ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]

16 243 ms 242 ms 242 ms ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
17 334 ms 334 ms 334 ms ae-3-3.ebr2.LosAngeles1.Level3.net [4.69.132.77]

18 321 ms 324 ms 324 ms ae-62-62.csw1.LosAngeles1.Level3.net [4.69.137.1
8]
19 297 ms 297 ms 297 ms ae-1-60.edge2.LosAngeles9.Level3.net [4.69.144.1
5]
20 382 ms 461 ms 461 ms KDDI-AMERIC.edge2.LosAngeles9.Level3.net [4.53.2
28.14]
21 329 ms 328 ms 328 ms lajbb002.kddnet.ad.jp [59.128.2.105]
22 299 ms 299 ms 299 ms otejbb204.kddnet.ad.jp [203.181.100.169]
23 327 ms 327 ms 326 ms cm-ote221.kddnet.ad.jp [118.155.197.161]
24 330 ms 303 ms 304 ms 203.181.98.10
25 302 ms 311 ms 301 ms 61.195.56.133
26 381 ms 382 ms 380 ms 219.117.144.74
27 394 ms 400 ms 394 ms 219.117.144.45
28 394 ms 391 ms 395 ms 219.117.146.129
29 395 ms 396 ms 397 ms 219.117.146.46
30 388 ms 397 ms 386 ms 202.67.52.81

Trace complete.

I'm currently using 2 connection, stable ADSL @ home and USB CDMA modem.

Here's the CDMA one:

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

1 70 ms 69 ms 78 ms 10.17.94.25
2 66 ms * * 10.17.97.2
3 79 ms 67 ms 58 ms 10.17.97.41
4 * 78 ms 72 ms 202.70.48.49
5 58 ms 59 ms 87 ms 202.70.48.17
6 * * * Request timed out.
7 64 ms 58 ms 60 ms ip-177-137.moratelindo.co.id [202.43.177.137]
8 * * * Request timed out.
9 100 ms 99 ms 99 ms ip-176-198.moratelindo.co.id [202.43.176.198]
10 241 ms 90 ms 93 ms ge-4-0-1.r00.sngpsi03.sg.bb.gin.ntt.net [116.51.17.181]
11 98 ms 100 ms 104 ms as-4.r20.sngpsi02.sg.bb.gin.ntt.net [129.250.3.59]
12 296 ms 213 ms 195 ms p64-7-1-3.r24.tokyjp01.jp.bb.gin.ntt.net [129.250.4.112]
13 171 ms 191 ms 179 ms ae-4.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.162]
14 170 ms 169 ms 198 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.146.94]
15 179 ms 173 ms 189 ms 219.117.144.66
16 179 ms 256 ms 187 ms 219.117.144.45
17 183 ms 192 ms 188 ms 219.117.146.129
18 176 ms 176 ms 172 ms 219.117.146.38
19 180 ms 163 ms 162 ms 202.67.52.81

Trace complete.

*****

Gonna post stable one later tonight.

People still posting this? it about 1year old i think they know the issue they can't fix it and wont even try when 2.0 is pretty much 1 and half or 2month away.

Quote:

---

Originally Posted by Zenaku

People still posting this? it about 1year old i think they know the issue they can't fix it and wont even try when 2.0 is pretty much 1 and half or 2month away.

---

It's likely that SE used their findings on this matter as a gauge for developing the rest of the 1.0 content.

Probably relating to the Garuda issue in Balmung.. Error 30002 for 3 days now.