Feedback Request on Network Delay

[Sinzya]

deleted due to wrong subject

[Mirage]

Just because everyone else is being so cool, I will too

Tracing route to 202.67.52.81 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.10.1
2 16 ms 5 ms 2 ms 94-246-xxx.xxx.3p.ntebredband.no [94.246.xxx.xxx]
3 1 ms <1 ms <1 ms 94-246-61.106.3p.ntebredband.no [94.246.61.106]
4 1 ms 1 ms 1 ms 121.213-167-114.customer.lyse.net [213.167.114.121]
5 16 ms 15 ms 15 ms tengigabitethernet7-1.ar2.arn3.gblx.net [64.208.169.121]
6 172 ms 171 ms 171 ms ASIA-NETCOM-ASIA-PACIFIC-LTD.TenGigabitEthernet1-2.ar5.LAX2.gblx.net [64.215.81.146]
^ First asian network node, notice the huge increase in latency.

7 283 ms 283 ms 283 ms gi2-0-0.cr1.nrt1.asianetcom.net [202.147.0.57]
8 283 ms 284 ms 286 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]
9 284 ms 283 ms 283 ms squareco.asianetcom.net [203.192.149.210]
^ And here's probably the first node of Squenix' corporate network

10 284 ms 284 ms 297 ms 61.195.56.129
11 274 ms 277 ms 273 ms 219.117.144.2
12 284 ms 284 ms 284 ms 219.117.146.149
13 287 ms 287 ms 287 ms 219.117.146.129
14 290 ms 288 ms 289 ms 219.117.146.46
15 284 ms 296 ms 291 ms 202.67.52.81

Trace complete.

[Forerunner]

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.

It's not just Ifrit, it's the whole game.

[Holy_Dragoon]

Since I never got around to this, but meant to:


Date: 6:30PM EST
ISP: Cogeco Cable
Network: Cable 14M Down 1.5M UP.


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

1 2 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 14 ms 15 ms 20 ms d226-3-49.home.cgocable.net [24.226.3.49]
4 16 ms 22 ms 24 ms gw-he.torontointernetxchange.net [206.108.34.112
]
5 38 ms 28 ms 27 ms 10gigabitethernet7-3.core1.chi1.he.net [184.105.
213.150]
6 59 ms 50 ms 49 ms 10gigabitethernet3-2.core1.den1.he.net [184.105.
213.86]
7 77 ms 75 ms 74 ms 10gigabitethernet1-4.core1.lax2.he.net [72.52.92
.38]
8 77 ms 83 ms 90 ms 10gigabitethernet2-1.core1.lax1.he.net [72.52.92
.121]
9 82 ms 89 ms 85 ms pacnet.10gigabitethernet2-3.core1.lax1.he.net [2
16.218.223.206]
10 190 ms 191 ms 200 ms gi6-0-0.cr1.nrt1.asianetcom.net [202.147.61.166]

11 183 ms 179 ms 182 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

12 208 ms 190 ms 186 ms squareco.asianetcom.net [203.192.149.210]
13 192 ms 191 ms 190 ms 61.195.56.129
14 193 ms 197 ms 194 ms 219.117.144.2
15 203 ms 199 ms 203 ms 219.117.146.149
16 182 ms 179 ms 190 ms 219.117.146.129
17 181 ms 181 ms 179 ms 219.117.146.46
18 199 ms 185 ms 185 ms 202.67.52.81

Trace complete.

[Sabaku_Usagi]

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

1 21 ms 2 ms 2 ms 192.168.1.1
2 3 ms 3 ms 3 ms 192.168.2.1
3 22 ms 22 ms 22 ms nv-**-**-146-129.sta.embarqhsd.net [**.**.146.129]
4 23 ms 24 ms 24 ms nv-**-**-252-189.sta.embarqhsd.net [**.**.252.189]
5 24 ms 23 ms 53 ms 206.51.71.169
6 47 ms 25 ms 86 ms bb-lsvgnvxb-jx9-01-ae0.core.centurytel.net [206.51.69.157]
7 46 ms 48 ms 102 ms bb-snjucacl-jx4-02-ae6.core.centurytel.net [206.51.69.161]
8 42 ms 55 ms 41 ms snj-edge-03.inet.qwest.net [65.115.65.81]
9 53 ms 53 ms 53 ms lap-brdr-03.inet.qwest.net [67.14.22.74]
10 53 ms 53 ms 52 ms 63.146.26.70
11 63 ms 54 ms 53 ms lajbb001.kddnet.ad.jp [59.128.2.9]
12 157 ms 185 ms 156 ms otejbb203.kddnet.ad.jp [203.181.100.13]
13 158 ms 155 ms 155 ms cm-ote221.kddnet.ad.jp [118.155.197.161]
14 159 ms 169 ms 158 ms 203.181.98.10
15 153 ms 152 ms 151 ms 61.195.56.133
16 161 ms 159 ms 159 ms 219.117.144.6
17 165 ms 155 ms 154 ms 219.117.146.153
18 161 ms 171 ms 167 ms 219.117.146.141
19 153 ms 166 ms 164 ms 219.117.146.50
20 166 ms 164 ms 165 ms 202.67.52.81

Trace complete.

[Famrid]

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

1 <1 ms * <1 ms FREEBOX [192.168.1.254]
2 22 ms * 23 ms 82.246.35.254
3 24 ms * 23 ms 213.228.39.62
4 41 ms * 24 ms nantes-6k-1-po7.intf.routers.proxad.net [212.27.
57.34]
5 32 ms * 32 ms bzn-crs16-1-be1104.intf.routers.proxad.net [212.
27.50.185]
6 49 ms 59 ms 55 ms londres-6k-1-po101.intf.routers.proxad.net [212.
27.51.186]
7 112 ms 112 ms 140 ms newyork-6k-1-po1.intf.routers.proxad.net [212.27
.58.206]
8 182 ms 183 ms 181 ms paloalto-6k-1-po1.intf.routers.proxad.net [212.2
7.58.222]
9 181 ms 193 ms 182 ms 198.32.176.65
10 181 ms 181 ms 180 ms pajbb002.kddnet.ad.jp [111.87.3.25]
11 290 ms 280 ms 281 ms otejbb203.kddnet.ad.jp [203.181.100.209]
12 290 ms 281 ms 281 ms cm-ote221.kddnet.ad.jp [118.155.197.161]
13 302 ms 279 ms 283 ms 203.181.98.10
14 274 ms 287 ms 326 ms 61.195.56.133
15 283 ms 304 ms 304 ms 219.117.144.78
16 288 ms 284 ms 285 ms 219.117.144.57
17 282 ms 282 ms 282 ms 219.117.146.141
18 283 ms 282 ms 289 ms 219.117.146.42
19 288 ms 284 ms 284 ms 202.67.52.81

Trace complete.

[Reika]

This has been a problem for my partner and I in Australia for months and months. Still a problem when not using Battleping.

I made a lengthy post about this here: http://forum.square-enix.com/ffxiv/t...l=1#post628373

SE - why should my partner and I have to pay TWO ADDITIONAL MONTHLY SUBSCRIPTION FEES TO A THIRD PARTY to even play this game comfortably?

I have recently Decided to try out battleping as well. So far, its been keeping those two numbers lower than without it (west coast server seems to be the best). I have yet to try Ifrit(Hard) again tho to see if it spikes me back into the red/unable to act range again tho.



I do have a suggestion that maybe SE could pull off: State side servers that are not NEW servers, but offer both a connection to the normal servers and also serve as the main point of data send/receive for stateside players, such as enemy locations, enemy attacks, etc, and it can maintain character positioning with people across the way. I don't know if this is possible, or if I even worded that well enough, but just throwing it out there.

[Rikester]

Date/Time: July 31st, 12:09pm PST
Internet Service Provider: AT&T Uverse
Network Type and Speed: Fiber to node: 18mbs
tracert Result:
Tracing route to traceip.ffxiv.com [202.67.52.81] over a maximum of 50 hops:

1 <1 ms <1 ms <1 ms homeportal [192.168.1.254]
2 26 ms 26 ms 41 ms 108-195-120-2.lightspeed.frokca.sbcglobal.net [108.195.120.2]
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 24 ms 25 ms 24 ms 12.83.77.137
7 27 ms 26 ms 27 ms ggr6.wswdc.ip.att.net [12.122.86.89]
8 30 ms 30 ms 30 ms 192.205.34.154
9 136 ms 139 ms 137 ms tyo-e4-i.TYO.JP.NET.DTAG.DE [62.154.5.226]
10 140 ms 135 ms 135 ms 80.150.170.106
11 135 ms 135 ms 135 ms 61.195.56.133
12 148 ms 147 ms 148 ms 219.117.144.74
13 143 ms 144 ms 142 ms 219.117.144.53
14 150 ms 148 ms 148 ms 219.117.146.141
15 143 ms 146 ms 142 ms 219.117.146.50
16 141 ms 135 ms 136 ms 202.67.52.81

Trace complete.

[Ganbachi]

From Dubai, United Arab Emirates.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\gigabyte>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 Broadcom.Home [192.168.1.1]
2 1 ms 1 ms 1 ms 213.42.8.32
3 1 ms <1 ms <1 ms 213.42.8.30
4 3 ms 2 ms 2 ms 213.42.9.97
5 * * * Request timed out.
6 2 ms 2 ms 2 ms 194.170.0.234
7 9 ms 9 ms 16 ms 195.229.1.181
8 7 ms 7 ms 15 ms 195.229.3.110
9 7 ms 5 ms 175 ms 59.128.15.125
10 172 ms 171 ms 281 ms cm-ote221.kddnet.ad.jp [118.155.197.161]
11 292 ms 282 ms 282 ms cm-ote221.kddnet.ad.jp [118.155.197.161]
12 287 ms 334 ms 286 ms 61.195.56.133
13 287 ms 286 ms 299 ms 219.117.144.74
14 283 ms 284 ms 290 ms 219.117.144.74
15 285 ms 285 ms 285 ms 219.117.144.53
16 265 ms 266 ms 266 ms 219.117.146.141
17 289 ms 275 ms 288 ms 202.67.52.81

Trace complete.

[Ryuko]

From the EAST COAST of the United States.

My ISP is Optimum Online. I am using a cable connection over a wireless router.

1 3 ms 3 ms 3 ms
2 * * * Request timed out.
3 11 ms 12 ms 12 ms ash-bb1-geth0-2-1.telia.net [65.19.100.113]
4 13 ms 13 ms 13 ms rtr4-ge1-10.mhe.hcvlny.cv.net [167.206.39.137]
5 13 ms 14 ms 13 ms 64.15.1.210
6 13 ms 15 ms 18 ms rtr3-tg11-2.in.nycmnyzr.cv.net [64.15.0.29]
7 37 ms 35 ms 34 ms te8-7.ccr01.jfk04.atlas.cogentco.com [154.54.11.
249]
8 34 ms 34 ms 35 ms te0-6-0-5.ccr22.jfk02.atlas.cogentco.com [154.54
.47.29]
9 37 ms 37 ms 37 ms te0-0-0-2.ccr22.dca01.atlas.cogentco.com [66.28.
4.82]
10 54 ms 53 ms 54 ms te0-1-0-7.ccr22.atl01.atlas.cogentco.com [154.54
.7.209]
11 55 ms 54 ms 53 ms te0-2-0-7.ccr22.iah01.atlas.cogentco.com [154.54
.42.213]
12 92 ms 93 ms 92 ms te0-0-0-5.ccr22.lax01.atlas.cogentco.com [154.54
.5.194]
13 142 ms 222 ms 231 ms te9-8.ccr02.lax05.atlas.cogentco.com [154.54.44.
134]
14 93 ms 98 ms 93 ms 38.104.84.42
15 208 ms 207 ms 210 ms gi11-0-0.cr1.nrt1.asianetcom.net [202.147.61.170
]
16 205 ms 213 ms 208 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

17 207 ms 206 ms 207 ms squareco.asianetcom.net [203.192.149.210]
18 212 ms 197 ms 197 ms 61.195.56.129
19 199 ms 198 ms 195 ms 219.117.144.70
20 196 ms 197 ms 198 ms 219.117.144.57
21 197 ms 196 ms 198 ms 219.117.146.141
22 198 ms 196 ms 194 ms 219.117.146.50
23 224 ms 201 ms 191 ms 202.67.52.81

Trace complete.