Feedback Request on Network Delay

[Zel]

Quest dsl up to 12

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 1 ms 1 ms 192.168.0.1
3 23 ms 22 ms 22 ms mpls-dsl-gw48-240.mpls.qwest.net [207.225.140.24
0]
4 25 ms 24 ms 23 ms mpls-agw1.inet.qwest.net [75.168.229.121]
5 83 ms 82 ms 83 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
6 84 ms 83 ms 84 ms 63.146.26.70
7 83 ms 82 ms 83 ms lajbb002.kddnet.ad.jp [59.128.2.177]
8 195 ms 196 ms 196 ms otejbb204.kddnet.ad.jp [203.181.100.45]
9 190 ms 190 ms 191 ms cm-ote221.kddnet.ad.jp [118.155.197.161]
10 196 ms 197 ms 197 ms 203.181.98.10
11 196 ms 196 ms 197 ms 61.195.56.133
12 197 ms 198 ms 196 ms 219.117.144.6
13 197 ms 197 ms 196 ms 219.117.146.153
14 190 ms 190 ms 190 ms 219.117.146.141
15 201 ms 201 ms 202 ms 219.117.146.42
16 196 ms 197 ms 196 ms 202.67.52.81

Trace complete.

C:\Users\Zelphar Moonglade>

[Cidspain]

Hello¡

02-11-2011 22:32
ONO (España)
ADSL 3MB


Traza a la dirección traceip.ffxiv.com [202.67.52.81]
sobre un máximo de 50 saltos:

1 10 ms 7 ms 8 ms 10.213.160.1
2 8 ms 8 ms 13 ms 10.127.44.33
3 11 ms 45 ms 9 ms 149.11.62.5
4 14 ms 12 ms 9 ms te0-2-0-7.ccr22.mad05.atlas.cogentco.com [130.11
7.2.69]
5 117 ms 111 ms 103 ms te0-2-0-1.ccr22.par01.atlas.cogentco.com [130.11
7.3.50]
6 132 ms 172 ms 157 ms te0-6-0-2.ccr22.jfk02.atlas.cogentco.com [154.54
.46.101]
7 126 ms 229 ms 118 ms te0-4-0-6.ccr22.dca01.atlas.cogentco.com [154.54
.42.29]
8 178 ms 216 ms 184 ms te0-0-0-6.ccr22.atl01.atlas.cogentco.com [154.54
.28.222]
9 181 ms 227 ms 190 ms te0-0-0-1.ccr22.iah01.atlas.cogentco.com [154.54
.5.94]
10 177 ms 246 ms 178 ms te0-1-0-6.ccr22.lax01.atlas.cogentco.com [66.28.
4.238]
11 169 ms 246 ms 207 ms te8-2.ccr02.lax05.atlas.cogentco.com [130.117.50
.90]
12 214 ms 212 ms 195 ms 38.104.84.42
13 323 ms 308 ms 302 ms gi11-0-0.cr1.nrt1.asianetcom.net [202.147.61.170
]
14 295 ms 343 ms 300 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

15 379 ms 315 ms 303 ms squareco.asianetcom.net [203.192.149.210]
16 437 ms 515 ms 490 ms 61.195.56.129
17 517 ms 429 ms 474 ms 219.117.144.2
18 500 ms 450 ms 472 ms 219.117.146.149
19 486 ms 512 ms 514 ms 219.117.146.129
20 433 ms 426 ms 500 ms 219.117.146.46

[Ryfen]

11/2/2011 - 11:29pm
Cox Communications
Cable (15 Mbps)

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

C:\Users\penizar>tracert -h 50 traceip.ffxiv.com

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

1 11 ms 14 ms 15 ms 192.168.1.1
2 27 ms 12 ms 17 ms 10.13.88.1
3 26 ms 13 ms 16 ms 68.10.11.33
4 27 ms 13 ms 15 ms 172.22.48.186
5 25 ms 15 ms 13 ms 68.10.8.181
6 29 ms 15 ms 51 ms 68.1.4.133
7 123 ms 132 ms 119 ms ae-5.r21.sttlwa01.us.bb.gin.ntt.net [129.250.4.1
82]
8 145 ms 119 ms 124 ms ae-0.r20.sttlwa01.us.bb.gin.ntt.net [129.250.2.5
3]
9 229 ms 217 ms 214 ms as-3.r20.tokyjp01.jp.bb.gin.ntt.net [129.250.4.1
90]
10 240 ms 228 ms 224 ms ae-1.r24.tokyjp01.jp.bb.gin.ntt.net [129.250.2.2
1]
11 230 ms 211 ms 225 ms ae-4.a20.tokyjp01.jp.ra.gin.ntt.net [61.213.162.
162]
12 232 ms 216 ms 209 ms ge-2-2-1.a20.tokyjp01.jp.ra.gin.ntt.net [61.120.
146.94]
13 219 ms 217 ms 220 ms 219.117.144.2
14 241 ms 220 ms 210 ms 219.117.146.149
15 207 ms 211 ms 193 ms 219.117.146.129
16 214 ms 201 ms 227 ms 219.117.146.46
17 221 ms 213 ms 197 ms 202.67.52.81

Trace complete.

[Gramul]

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

1 2 ms 1 ms 1 ms W_Col_2 [192.168.1.1]
2 * * * Request timed out.
3 11 ms 8 ms 9 ms te1-4.austtxc-er03.texas.rr.com [66.68.2.205]
4 16 ms 11 ms 10 ms te-0-8-0-3.austtxrdcsc-cr02.texas.rr.com [24.27.
12.196]
5 26 ms 23 ms 23 ms gig2-1-1.hstntxl3-rtr1.texas.rr.com [72.179.205.
58]
6 20 ms 16 ms 17 ms ae-4-0.cr0.hou30.tbone.rr.com [66.109.6.54]
7 19 ms 19 ms 58 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
8 55 ms 53 ms 53 ms ae-3-0.cr0.lax30.tbone.rr.com [66.109.6.0]
9 56 ms 55 ms 55 ms ae-1-0.pr0.lax00.tbone.rr.com [66.109.6.129]
10 55 ms 59 ms 55 ms pacnet.com.any2ix.coresite.com [206.223.143.138]

11 162 ms 161 ms 163 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]

12 161 ms 161 ms 163 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

13 180 ms 163 ms 162 ms squareco.asianetcom.net [203.192.149.210]
14 164 ms 163 ms 162 ms 61.195.56.129
15 161 ms 163 ms 161 ms 219.117.144.2
16 163 ms 163 ms 163 ms 219.117.146.149
17 171 ms 171 ms 171 ms 219.117.146.129
18 176 ms 171 ms 172 ms 219.117.146.38
19 165 ms 166 ms 164 ms 202.67.52.81

Trace complete.

[Geesus]

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.

Actually your wrong. The first line or two of the IPs are your IP or your router then your ISP IP so yes they are displaying their IPs. Example from Keftenk's IP
1 <1 ms <1 ms 1 ms 192.168.1.1 <---router
2 8 ms 7 ms 8 ms 73.205.22.1 <--- ISP IP assigned to his modem

[Geesus]

The bottom line is it's not the latency or packet loss (though that may be the case for some playesr with really bad ADSL/low budget connections) that is causing our issues with being unable to dodge enemy WSes, but rather an inability for the client to update the server often enough on position changes.

While this may be true, it's not the users fault that the service provide here, especially in the States is as crappy as it is. So while your statement again may be true, you can't count out the issue occuring for 90% of the players in such a broad general statement. While our Gov wants to believe this is the greatest country in the world, the fact they and the companies providing the service are coniving jerks and theives and provide awful service to those of us paying ridiculous prices is not the issue.

[Eruantien]

Date & Time: 2011-11-03-21:15:00 GMT
Internet Service Provider BT Internet (England)
Network Type and Speed ADSL 1Mbps
tracert Result:
Tracing route to traceip.ffxiv.com [202.67.52.81]
over a maximum of 50 hops:

1 21 ms 94 ms 94 ms BThomehub.home [192.168.1.254]
2 33 ms 33 ms 35 ms 217.47.79.122
3 34 ms 33 ms 35 ms 217.47.79.145
4 35 ms 37 ms 35 ms 213.1.69.90
5 33 ms 34 ms 32 ms 217.32.26.26
6 265 ms 459 ms 62 ms 217.32.26.178
7 35 ms 34 ms 34 ms acc1-10Gige-0-5-0-4.bm.21cn-ipp.bt.net [109.159.
248.96]
8 48 ms 43 ms 43 ms core1-te0-2-5-0.ealing.ukcore.bt.net [109.159.24
8.0]
9 42 ms 41 ms 41 ms acc1-10GigE-0-5-0-4.l-far.21cn-ipp.bt.net [109.1
59.254.104]
10 42 ms 40 ms 41 ms 195.99.126.129
11 203 ms 203 ms 202 ms te7-4.losangeles1.loa.seabone.net [89.221.35.146
]
12 198 ms 198 ms 198 ms pacnet.losangeles1.loa.seabone.net [89.221.35.18
6]
13 304 ms 303 ms 302 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]

14 305 ms 304 ms 304 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

15 302 ms 301 ms 301 ms squareco.asianetcom.net [203.192.149.210]
16 302 ms 299 ms 301 ms 61.195.56.129
17 296 ms 295 ms 296 ms 219.117.144.2
18 295 ms 295 ms 295 ms 219.117.146.149
19 309 ms 309 ms 309 ms 219.117.146.129
20 312 ms 313 ms 316 ms 219.117.146.38
21 351 ms 396 ms 297 ms 202.67.52.81





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

1 89 ms 98 ms 97 ms BThomehub.home [192.168.1.254]
2 34 ms 33 ms 33 ms 217.47.79.122
3 35 ms 32 ms 33 ms 217.47.79.145
4 35 ms 35 ms 33 ms 213.1.69.90
5 35 ms 34 ms 34 ms 217.32.26.26
6 33 ms 35 ms 34 ms 217.32.26.178
7 34 ms 34 ms 33 ms acc1-10Gige-0-5-0-4.bm.21cn-ipp.bt.net [109.159.
248.96]
8 44 ms 42 ms 43 ms core1-te0-2-5-0.ealing.ukcore.bt.net [109.159.24
8.0]
9 42 ms 41 ms 42 ms acc1-10GigE-0-5-0-4.l-far.21cn-ipp.bt.net [109.1
59.254.104]
10 43 ms 40 ms 61 ms 195.99.126.129
11 200 ms 200 ms 201 ms te7-4.losangeles1.loa.seabone.net [89.221.35.146
]
12 197 ms 198 ms 199 ms pacnet.losangeles1.loa.seabone.net [89.221.35.18
6]
13 304 ms 303 ms 303 ms gi8-0-0.cr1.nrt1.asianetcom.net [202.147.0.121]

14 303 ms 304 ms 304 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

15 302 ms 303 ms 302 ms squareco.asianetcom.net [203.192.149.210]
16 299 ms 301 ms 301 ms 61.195.56.129
17 297 ms 300 ms 297 ms 219.117.144.2
18 294 ms 297 ms 297 ms 219.117.146.149
19 309 ms 309 ms 312 ms 219.117.146.129
20 314 ms 313 ms 314 ms 219.117.146.38
21 297 ms 294 ms 297 ms 202.67.52.81

[lanthom]

11/3/11 - 8:53 PM EDT
Comcast Cable
Cable - 12 MB

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 11 ms 21 ms 13 ms 68.53.100.1
3 8 ms 13 ms 10 ms ge-2-24-ur01.sharpsridge.tn.knox.comcast.net [68.85.38.53]
4 8 ms 8 ms 11 ms te-8-1-ar01.sharpsridge.tn.knox.comcast.net [68.86.136.82]
5 113 ms 53 ms 14 ms xe-5-1-1-0-ar03.nashville.tn.nash.comcast.net [68.85.174.1]
6 33 ms 31 ms 28 ms pos-3-7-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.73]
7 33 ms 28 ms 34 ms 68.86.88.30
8 51 ms 46 ms 47 ms pos-4-10-0-0-cr01.newyork.ny.ibone.comcast.net [68.86.88.169]
9 49 ms 50 ms 57 ms pos-0-2-0-0-pe01.111eighthave.ny.ibone.comcast.net [68.86.87.226]
10 60 ms 51 ms 48 ms e0-3.cr01.mia01.mzima.net [75.149.228.178]
11 215 ms 209 ms 211 ms 217.239.40.154
12 219 ms 214 ms 234 ms 80.150.170.106
13 209 ms 219 ms 208 ms 61.195.56.133
14 211 ms 211 ms 209 ms 219.117.144.6
15 215 ms 216 ms 210 ms 219.117.146.153
16 207 ms 209 ms 210 ms 219.117.146.141
17 211 ms 210 ms 210 ms 219.117.146.42
18 211 ms 212 ms 212 ms 202.67.52.81

[Bahn]

While this may be true, it's not the users fault that the service provide here, especially in the States is as crappy as it is. So while your statement again may be true, you can't count out the issue occuring for 90% of the players in such a broad general statement. While our Gov wants to believe this is the greatest country in the world, the fact they and the companies providing the service are coniving jerks and theives and provide awful service to those of us paying ridiculous prices is not the issue.

Oh, I know. ISPs are a business, and like any business, they will go to the absolute extremes to make profit within legal means, even if it involves screwing customers and the "little guy" over. Subscribe as many customers as possible, keep their bandwiths to the lowest a customer can tolerate before they move to another network, and charge through the nose for "upgrades". And just to add salt to the wound, here's a recent article from DSL Reports stating that the US is ranked 12th in the world in Internet broadband speeds: https://secure.dslreports.com/showne...d-Speed-116718

Do note I said *some*, not all, users may just have an ISP with a poor connection into the Internet, and yeah most likely than not they're a minority, but my experience with ADSL vs Cable generally goes to show that ADSL tends to run off of backbones that are farther away from the "main" backbones that go through our country. The farther away you are from a backbone, the more hops your data has to make, the more hops your data makes, the worse ping times you get (among other things). It's cheaper to get an ADSL line into a rural area than it is for another company to run cable lines. Anyone who has more network experience than me (as I'm just a lowly technician) feel free to chime in on this.

Anyway, yeah, I definitely agree this is an issue with the way Square programmed their client/service architecture, and has little to do with traceroutes or ping times.

[Geesus]

Oh, I know. ISPs are a business, and like any business, they will go to the absolute extremes to make profit within legal means, even if it involves screwing customers and the "little guy" over. Subscribe as many customers as possible, keep their bandwiths to the lowest a customer can tolerate before they move to another network, and charge through the nose for "upgrades". And just to add salt to the wound, here's a recent article from DSL Reports stating that the US is ranked 12th in the world in Internet broadband speeds: https://secure.dslreports.com/showne...d-Speed-116718

Oh don't I know it LOL. *sigh