Feedback Request on Network Delay

We have received quite a few reports that players still incur damage from Ifrit’s AoE attacks (such as Eruption) even after they move out of the AoE during the Bowl of Embers / the Bowl of Embers (Hard) battle.

In order to thoroughly investigate this issue, please reply to this thread with the following details if you have personally experienced the issue.
Date & Time

Internet Service Provider

Network Type and Speed

Global IP (optional)

tracert Result*
Use the following command to obtain a tracert result:
　　　　 tracert -h 50 traceip.ffxiv.com
　　 * Please try and obtain tracert results several times if possible.

Thank you for your assistance and cooperation.

Quote:

How to obtain tracert results:
Run cmd.exe or command.exe
If you are using Windows XP, Vista, or Windows 7:
Select Start > All Programs > Accessories > Command Prompt

Type the command "tracert -h 50 traceip.ffxiv.com" (without quotes) on Command Prompt and press Enter.

Copy and paste a tracert result.

Click the "Command Prompt" icon located at the title bar to open a menu. Select Edit > Mark.

Mark the tracert result in Command Prompt (from “Tracing route to...” to “Tracing complete.”). Click the icon again to select Edit > Copy.

Paste the result in your reply.

Users in Germany, please visit this thread.
Users in France, please visit this thread.

Lemme put mine here. Since it's in portuguese i'll "translate" it after the line. Good to know it started worrying you guys ^^ Because right now the best performance from FFXIV is way below the worst performance i ever had with FFXI...and right now it's also much worse than prior to 1.18...seems like every patch that comes the game response is getting worse.

Date: 16:30 10/28/2011
ISP: BrTurbo (Brazil)
Network: ADSL 2MBps

Rastreando a rota para traceip.ffxiv.com [202.67.52.81] (tracing route for traceip.ffxiv.com)
com no máximo 50 saltos:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 1 ms * * 192.168.254.254
3 * * * Esgotado o tempo limite do pedido. (request timeout)
4 * * * Esgotado o tempo limite do pedido.
5 * * * Esgotado o tempo limite do pedido.
6 * * * Esgotado o tempo limite do pedido.
7 * * * Esgotado o tempo limite do pedido.
8 * * * Esgotado o tempo limite do pedido.
9 * * * Esgotado o tempo limite do pedido.
10 * * * Esgotado o tempo limite do pedido.
11 * * * Esgotado o tempo limite do pedido.
12 * * * Esgotado o tempo limite do pedido.
13 * * * Esgotado o tempo limite do pedido.
14 394 ms 359 ms 387 ms 202.67.52.81

Rastreamento concluído. (tracing complete)

3:25PM CST (13:25 PDT as you call it)
Time Warner Cable
Cable Wideband 50MBps

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

1 <1 ms <1 ms <1 ms AUSTINS-TIME-CA [10.0.1.1]
2 6 ms 7 ms 7 ms 10.77.19.1
3 9 ms 6 ms 7 ms tge1-8.snantx2300-er03.texas.rr.com [24.28.134.188]
4 8 ms 8 ms 7 ms tge3-3.snantx2000-er03.texas.rr.com [24.28.131.30]
5 14 ms 13 ms 10 ms tengig0-0-0-3.snantx6000-rtr1.satx.rr.com [24.28.133.120]
6 25 ms 23 ms 23 ms ae23.dllatxl3-cr01.texas.rr.com [72.179.205.8]
7 15 ms 15 ms 15 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
8 52 ms 51 ms 56 ms ae-3-0.cr0.lax30.tbone.rr.com [66.109.6.0]
9 53 ms 53 ms 53 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
10 52 ms 53 ms 54 ms pacnet.com.any2ix.coresite.com [206.223.143.138]
11 159 ms 159 ms 159 ms po15-1-1.cr1.nrt1.asianetcom.net [202.147.61.186]
12 159 ms 159 ms 159 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
13 161 ms 162 ms 159 ms squareco.asianetcom.net [203.192.149.210]
14 160 ms 159 ms 160 ms 61.195.56.129
15 159 ms 160 ms 160 ms 219.117.144.2
16 160 ms 160 ms 159 ms 219.117.146.149
17 158 ms 157 ms 157 ms 219.117.146.129
18 158 ms 157 ms 158 ms 219.117.146.38
19 159 ms 159 ms 159 ms 202.67.52.81

Trace complete.

Is there any way we can submit this information privately without having our IPs on display?

Are you guys posting results from inside the Ifrit fight?

Or are you posting a result while standing in Uldah or something?

Shouldn't the sample come from when you have just fought Ifrit and notice latency issues?

I'll be also translating my results from portuguese ;P

Date & Time: 28/10/2011 21:48
Internet Service Provider: ZON TV Cabo
Network Type and Speed: ADSL 12MB
tracert Result:

A rastrear a rota para traceip.ffxiv.com [202.67.52.81] (tracing route for traceip.ffxiv.com)
até um máximo de 50 saltos:

1 1 ms 1 ms 1 ms 192.168.2.1
2 8 ms 9 ms 8 ms 10.4.127.254
3 333 ms 123 ms 53 ms 10.137.196.145
4 14 ms 9 ms 11 ms 10.255.49.94
5 874 ms 142 ms 9 ms te2-8.ccr01.opo01.atlas.cogentco.com [149.6.32.17]
6 13 ms 13 ms 16 ms te7-1.ccr01.vgo01.atlas.cogentco.com [154.54.57.138]
7 24 ms 23 ms 23 ms te4-8.ccr01.bio01.atlas.cogentco.com [154.54.37.49]
8 27 ms 27 ms 27 ms te2-2.ccr01.bod01.atlas.cogentco.com [154.54.38.82]
9 36 ms 38 ms 35 ms te0-0-0-1.mpd22.par01.atlas.cogentco.com [130.117.0.226]
10 108 ms 109 ms 109 ms te0-6-0-2.mpd22.jfk02.atlas.cogentco.com [154.54.46.105]
11 114 ms 115 ms 114 ms te0-3-0-6.mpd22.dca01.atlas.cogentco.com [154.54.41.29]
12 160 ms 154 ms 145 ms te0-2-0-3.mpd22.atl01.atlas.cogentco.com [154.54.2.101]
13 145 ms 144 ms 145 ms te0-3-0-2.mpd22.iah01.atlas.cogentco.com [154.54.2.246]
14 194 ms 176 ms 175 ms te0-0-0-3.mpd22.lax01.atlas.cogentco.com [154.54.45.6]
15 179 ms 179 ms 183 ms te9-1.ccr02.lax05.atlas.cogentco.com [154.54.44.130]
16 181 ms 181 ms 180 ms 38.104.84.42
17 289 ms 289 ms * gi11-0-0.cr1.nrt1.asianetcom.net [202.147.61.170]
18 289 ms 291 ms 290 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
19 295 ms 295 ms 298 ms squareco.asianetcom.net [203.192.149.210]
20 316 ms 310 ms 683 ms 61.195.56.129
21 310 ms 298 ms 307 ms 219.117.144.2
22 296 ms 296 ms 297 ms 219.117.146.149
23 306 ms 308 ms 308 ms 219.117.146.129
24 310 ms 308 ms 307 ms 219.117.146.46
25 447 ms 416 ms 317 ms 202.67.52.81

Rastreio concluído. (tracing complete)

Those aren't your IPs they are the route its taking to get to it.

It doesn't matter if you are killing ifrit or not, the servers are in the same building. Even if the ifrit fight is on another server its in the same room.

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 8 ms 7 ms 8 ms 73.205.22.1
3 15 ms 9 ms 7 ms te-4-1-ur01.maplegrove.mn.minn.comcast.net [68.8
5.166.49]
4 7 ms 9 ms 9 ms te-2-1-ur02.newhope.mn.minn.comcast.net [68.87.1
74.45]
5 8 ms 13 ms 12 ms te-8-1-ur01.newhope.mn.minn.comcast.net [69.139.
176.49]
6 11 ms 14 ms 11 ms te-0-3-0-2-ar01.crosstown.mn.minn.comcast.net [6
8.87.174.29]
7 27 ms 27 ms 30 ms te-2-1-0-6-cr01.denver.co.ibone.comcast.net [68.
86.94.249]
8 73 ms 72 ms 71 ms pos-3-13-0-0-cr01.sanjose.ca.ibone.comcast.net [
68.86.85.134]
9 71 ms 71 ms 72 ms pos-0-1-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.87.2]
10 70 ms 75 ms 83 ms 80.156.163.153
11 179 ms 180 ms 182 ms 217.239.40.154
12 177 ms 177 ms 177 ms 80.150.170.106
13 178 ms 177 ms 177 ms 61.195.56.133
14 181 ms 178 ms 177 ms 219.117.144.6
15 176 ms 190 ms 177 ms 219.117.146.153
16 178 ms 177 ms 177 ms 219.117.146.141
17 178 ms 178 ms 182 ms 219.117.146.50
18 177 ms 177 ms 178 ms 202.67.52.81

Trace complete.

Quote:

Originally Posted by Rentahamster

Is there any way we can submit this information privately without having our IPs on display?

Indeed it's like Defmetal said...those IPs are route destiny IPs, not yours. And IPs starting with 192.168.*.* are network device IPs, like routers, hubs, switches...it's default for network devices so you cannot be identified by it.

But if you want to send it in a private way, try using the support page contact for it. There is a technical support option there (even though i believe it would be better just sending it with feedback option since technical support first approach is always automated. Just explain that you don't want to post info of yours at forum)

EDIT: Lol...i'm the only one getting timeout...i guess my connection is even worse than i expected...even though those speedtest sites rate it pretty well (Often B)

October 28, 2011 4:55 PM MDT
Comcast
Cable 2MB

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 25 ms 32 ms 28 ms 98.245.112.1
3 12 ms 9 ms 30 ms te-8-2-ur02.boulder.co.denver.comcast.net [68.85
.107.109]
4 12 ms 31 ms 16 ms te-0-6-0-5-ar02.aurora.co.denver.comcast.net [68
.86.179.81]
5 14 ms 14 ms 33 ms pos-3-7-0-0-cr01.denver.co.ibone.comcast.net [68
.86.91.101]
6 56 ms 59 ms 93 ms pos-3-13-0-0-cr01.sanjose.ca.ibone.comcast.net [
68.86.85.134]
7 56 ms 54 ms 54 ms pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.86.122]
8 56 ms 52 ms 53 ms 80.156.163.153
9 161 ms 163 ms 162 ms 217.239.40.154
10 176 ms 160 ms 160 ms 80.150.170.106
11 176 ms 174 ms 160 ms 61.195.56.133
12 159 ms 160 ms 162 ms 219.117.144.6
13 158 ms 176 ms 163 ms 219.117.146.153
14 203 ms 185 ms 164 ms 219.117.146.141
15 160 ms 162 ms 160 ms 219.117.146.50
16 177 ms 162 ms 160 ms 202.67.52.81

Trace complete.

---
October 28, 2011 5:00 PM MDT

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 28 ms 24 ms 29 ms 98.245.112.1
3 32 ms 11 ms 29 ms te-8-2-ur02.boulder.co.denver.comcast.net [68.85
.107.109]
4 16 ms 31 ms 14 ms te-0-6-0-5-ar02.aurora.co.denver.comcast.net [68
.86.179.81]
5 12 ms 13 ms 13 ms pos-3-7-0-0-cr01.denver.co.ibone.comcast.net [68
.86.91.101]
6 58 ms 56 ms 55 ms pos-3-13-0-0-cr01.sanjose.ca.ibone.comcast.net [
68.86.85.134]
7 64 ms 59 ms 54 ms pos-0-0-0-0-pe01.529bryant.ca.ibone.comcast.net
[68.86.86.122]
8 80 ms 99 ms 55 ms 80.156.163.153
9 166 ms 163 ms 165 ms 217.239.40.154
10 161 ms 166 ms 159 ms 80.150.170.106
11 159 ms 162 ms 162 ms 61.195.56.133
12 163 ms 178 ms 160 ms 219.117.144.6
13 166 ms 167 ms 164 ms 219.117.146.153
14 161 ms 162 ms 160 ms 219.117.146.141
15 162 ms 161 ms 163 ms 219.117.146.50
16 159 ms 159 ms 177 ms 202.67.52.81

Trace complete.