HUGE CONNECTION PROBLEM

[HeroSamson]

I feel like I am playing FFXI on a 56k connection, this is not right.

I mean FFXI runs better than this with cable/DSL, there should be zero reasons we are all lagging this bad.

I played on 56k before regular dial up on ffxi before I upgraded my internet, it is the same as ffxiv's right now, play for 10-15 minutes get dced 90k

[Zindel-Origin]

Lamia Server. Just started playing this game about 2 weeks ago and have had no problems until the patch. Now I'm getting hammered with 90k every 10 minutes, and unable to log back in quick enough to save my group due to 3102 which is seems like a ridiculous amount of time to auto log a character from the server.



If this continues I'm not subscribing... the game is unplayable for me right now.

[Kerberon]

Lamia Server. Just started playing this game about 2 weeks ago and have had no problems until the patch. Now I'm getting hammered with 90k every 10 minutes, and unable to log back in quick enough to save my group due to 3102 which is seems like a ridiculous amount of time to auto log a character from the server.



If this continues I'm not subscribing... the game is unplayable for me right now.

That speed test really means nothing. You have to check your ping to the server, is that bad then a traceroute, if that's good, then a pathping to look for loss.
Ton's of info in this post on how to find your problem and how to get it fixed. http://forum.square-enix.com/ffxiv/t...=1#post2168562 The error doesn't seem to be with SE but with the routing done between TWC and SE in Montreal. From what I've seen in these threads it seems like most the people with problems are TWC subscribers.

[Dreamslave]

Yup, this is happening to me every single night, just past midnight (EST). I pinged the NA servers and I have >40ms to them, yet the moment I enter combat outside of a dungeon, be it a FATE or even just a single mob, I get HUGE lag and usually get 90k'd. I just came back to the game not even two weeks ago and I already want to quit because I cannot play at night.

That speed test really means nothing. You have to check your ping to the server, is that bad then a traceroute, if that's good, then a pathping to look for loss.
Ton's of info in this post on how to find your problem and how to get it fixed. http://forum.square-enix.com/ffxiv/t...=1#post2168562 The error doesn't seem to be with SE but with the routing done between TWC and SE in Montreal. From what I've seen in these threads it seems like most the people with problems are TWC subscribers.

I'm a TWC subscriber, living in Upstate NY. My ping to the NA servers in Montreal is >40ms, which is pretty dang good. There is no excuse for this at this point...so frustrating...

[Kerberon]

Yup, this is happening to me every single night, just past midnight (EST). I pinged the NA servers and I have >40ms to them, yet the moment I enter combat outside of a dungeon, be it a FATE or even just a single mob, I get HUGE lag and usually get 90k'd. I just came back to the game not even two weeks ago and I already want to quit because I cannot play at night.




I'm a TWC subscriber, living in Upstate NY. My ping to the NA servers in Montreal is >40ms, which is pretty dang good. There is no excuse for this at this point...so frustrating...

Run a pathping to the datacenters. See if you have any loss, if you have loss that is your problem. Most games tolerate high ping times fairly well but can't handle when there is high loss in my experience. If you get loss before it hits the datacenter you need to try to deal with your isp and their routing tables not SE.

[Sithgear75]

Been getting hammered with 90k since update 2.28, mainly after midnight EST. Playing on PS4, hard wired into a 100 Mb connection through Comcast in FL.



Tracing route to 184.107.107.176 over a maximum of 30 hops

0 Home-PC.hsd1.fl.comcast.net. [10.0.0.14]
1 10.0.0.1
2 c-66-177-130-1.hsd1.fl.comcast.net [66.177.130.1]
3 te-9-4-ur01.timuquana.fl.jacksvil.comcast.net [68.86.171.189]
4 te-0-11-0-6-ar02.southside.fl.jacksvil.comcast.net [68.85.225.65]
5 pos-0-3-0-0-cr01.miami.fl.ibone.comcast.net [68.86.93.133]
6 pos-0-3-0-0-pe01.nota.fl.ibone.comcast.net [68.86.87.230]
7 te0-0-0-13.ccr21.mia03.atlas.cogentco.com [154.54.12.209]
8 be2055.ccr22.mia01.atlas.cogentco.com [154.54.24.233]
9 be2123.ccr42.atl01.atlas.cogentco.com [154.54.24.197]
10 be2099.ccr42.ord01.atlas.cogentco.com [154.54.28.73]
11 be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42.6]
12 te0-0-2-3.rcr11.b011027-3.yyz02.atlas.cogentco.com [154.54.6.242]
13 38.122.70.182
14 ae21.cr6.mtl.iweb.com [67.205.127.121]
15 ae0.cr5.mtl.iweb.com [184.107.1.61]
16 te7-4.dr9.mtl.iweb.com [184.107.1.110]
17 72.55.128.44
18 184.107.107.176

Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Home-PC.hsd1.fl.comcast.net. [10.0
.0.14]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
1/ 100 = 1% |
2 67ms 1/ 100 = 1% 0/ 100 = 0% c-66-177-130-1.hsd1.fl.comcast.net
[66.177.130.1]
2/ 100 = 2% |
3 33ms 3/ 100 = 3% 0/ 100 = 0% te-9-4-ur01.timuquana.fl.jacksvil.
comcast.net [68.86.171.189]
1/ 100 = 1% |
4 54ms 4/ 100 = 4% 0/ 100 = 0% te-0-11-0-6-ar02.southside.fl.jack
svil.comcast.net [68.85.225.65]
0/ 100 = 0% |
5 45ms 7/ 100 = 7% 3/ 100 = 3% pos-0-3-0-0-cr01.miami.fl.ibone.co
mcast.net [68.86.93.133]
0/ 100 = 0% |
6 40ms 6/ 100 = 6% 2/ 100 = 2% pos-0-3-0-0-pe01.nota.fl.ibone.com
cast.net [68.86.87.230]
0/ 100 = 0% |
7 33ms 4/ 100 = 4% 0/ 100 = 0% te0-0-0-13.ccr21.mia03.atlas.cogen
tco.com [154.54.12.209]
0/ 100 = 0% |
8 28ms 5/ 100 = 5% 1/ 100 = 1% be2055.ccr22.mia01.atlas.cogentco.
com [154.54.24.233]
0/ 100 = 0% |
9 36ms 4/ 100 = 4% 0/ 100 = 0% be2123.ccr42.atl01.atlas.cogentco.
com [154.54.24.197]
0/ 100 = 0% |
10 51ms 4/ 100 = 4% 0/ 100 = 0% be2099.ccr42.ord01.atlas.cogentco.
com [154.54.28.73]
0/ 100 = 0% |
11 61ms 5/ 100 = 5% 1/ 100 = 1% be2080.ccr22.yyz02.atlas.cogentco.
com [154.54.42.6]
0/ 100 = 0% |
12 --- 100/ 100 =100% 96/ 100 = 96% te0-0-2-3.rcr11.b011027-3.yyz02.at
las.cogentco.com [154.54.6.242]
0/ 100 = 0% |
13 137ms 6/ 100 = 6% 2/ 100 = 2% 38.122.70.182
0/ 100 = 0% |
14 --- 100/ 100 =100% 96/ 100 = 96% ae21.cr6.mtl.iweb.com [67.205.127.
121]
0/ 100 = 0% |
15 --- 100/ 100 =100% 96/ 100 = 96% ae0.cr5.mtl.iweb.com [184.107.1.61
]
0/ 100 = 0% |
16 --- 100/ 100 =100% 96/ 100 = 96% te7-4.dr9.mtl.iweb.com [184.107.1.
110]
0/ 100 = 0% |
17 145ms 4/ 100 = 4% 0/ 100 = 0% 72.55.128.44
4/ 100 = 4% |
18 119ms 8/ 100 = 8% 0/ 100 = 0% 184.107.107.176

Trace complete.

[Dreamslave]

Run a pathping to the datacenters. See if you have any loss, if you have loss that is your problem. Most games tolerate high ping times fairly well but can't handle when there is high loss in my experience. If you get loss before it hits the datacenter you need to try to deal with your isp and their routing tables not SE.

Tracing route to 184.107.107.176 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.1.1
2 43 ms 23 ms 28 ms cable-mac1.troynydv-ar4005.nyroc.rr.com [67.246. 32.1]
3 13 ms 11 ms 14 ms xe-4-0-0-0.troynydv-rtr001.alb.east.twcable.com [24.29.43.153]
4 16 ms 12 ms 12 ms rdc-74-76-243-0.alb.east.twcable.com [74.76.243. 0]
5 27 ms 27 ms 27 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.24 1.193]
6 26 ms 27 ms 27 ms be46.cr0.nyc30.tbone.rr.com [107.14.19.102]
7 24 ms 23 ms 63 ms ae-1-0.pr0.nyc20.tbone.rr.com [66.109.6.163]
8 20 ms 26 ms 26 ms 66.110.96.13
9 33 ms 30 ms 35 ms 63.243.128.121
10 29 ms 39 ms 30 ms if-5-5.tcore1.NYY-New-York.as6453.net [216.6.90. 5]
11 30 ms 69 ms 28 ms if-11-2.tcore2.NYY-New-York.as6453.net [216.6.99 .1]
12 61 ms 32 ms 30 ms if-5-2.tcore2.MTT-Montreal.as6453.net [216.6.99. 30]
13 97 ms 439 ms 78 ms if-0-2.tcore1.MTT-Montreal.as6453.net [216.6.115 .89]
14 * 316 ms 172 ms 64.86.31.42
15 31 ms 38 ms 35 ms ae31.cr6.mtl.iweb.com [184.107.1.254]
16 36 ms 33 ms 30 ms te8-4.dr10.mtl.iweb.com [67.205.127.82]
17 34 ms 31 ms 34 ms 72.55.128.44
18 1580 ms 31 ms 31 ms 184.107.107.176
Trace complete.

Hop 14 is a jerk...

[Kerberon]

snip

You've got loss almost immediately. Do the normal tech support thing and look for any damage to your cables and make sure everything is tight. If that is good call your isp and get a tech out. I've had similar problems when the junction box outside my house got a bad seal and corrosion started in on the connections.

[Xruptor]

Folks you are using the wrong IP address. DO NOT USE 184.107.107.176

I made the same mistake. It turns out that the above IP address in red is for the FFXIV web servers not the actual game servers. That's a huge difference. You need to use the game servers IP to do an actual trace.

Example: Adamantoise Server: 199.91.189.28

To learn how to get the IP of your server go to this thread: http://forum.square-enix.com/ffxiv/t...=1#post2180490

[Sithgear75]

Ran a test just now, does the 0% signify my loss? Or is a 0% right off the rip mean I have a string and a cup connecting me to the servers?





Tracing route to 184.107.107.176 over a maximum of 30 hops

0 Home-PC.hsd1.fl.comcast.net. [10.0.0.4]
1 10.0.0.1
2 c-66-177-130-1.hsd1.fl.comcast.net [66.177.130.1]
3 te-9-4-ur01.timuquana.fl.jacksvil.comcast.net [68.86.171.189]
4 te-0-11-0-6-ar02.southside.fl.jacksvil.comcast.net [68.85.225.65]
5 pos-0-3-0-0-cr01.miami.fl.ibone.comcast.net [68.86.93.133]
6 pos-0-3-0-0-pe01.nota.fl.ibone.comcast.net [68.86.87.230]
7 te0-0-0-13.ccr21.mia03.atlas.cogentco.com [154.54.12.209]
8 be2055.ccr22.mia01.atlas.cogentco.com [154.54.24.233]
9 be2123.ccr42.atl01.atlas.cogentco.com [154.54.24.197]
10 be2099.ccr42.ord01.atlas.cogentco.com [154.54.28.73]
11 be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42.6]
12 te0-0-2-3.rcr11.b011027-3.yyz02.atlas.cogentco.com [154.54.6.242]
13 38.122.70.182
14 ae21.cr6.mtl.iweb.com [67.205.127.121]
15 ae0.cr5.mtl.iweb.com [184.107.1.61]
16 te7-4.dr9.mtl.iweb.com [184.107.1.110]
17 72.55.128.44
18 184.107.107.176

Computing statistics for 450 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Home-PC.hsd1.fl.comcast.net. [10.0
.0.4]
0/ 100 = 0% |
1 1ms 0/ 100 = 0% 0/ 100 = 0% 10.0.0.1
0/ 100 = 0% |
2 12ms 0/ 100 = 0% 0/ 100 = 0% c-66-177-130-1.hsd1.fl.comcast.net
[66.177.130.1]
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% te-9-4-ur01.timuquana.fl.jacksvil.
comcast.net [68.86.171.189]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% te-0-11-0-6-ar02.southside.fl.jack
svil.comcast.net [68.85.225.65]
0/ 100 = 0% |
5 20ms 0/ 100 = 0% 0/ 100 = 0% pos-0-3-0-0-cr01.miami.fl.ibone.co
mcast.net [68.86.93.133]
0/ 100 = 0% |
6 21ms 0/ 100 = 0% 0/ 100 = 0% pos-0-3-0-0-pe01.nota.fl.ibone.com
cast.net [68.86.87.230]
0/ 100 = 0% |
7 19ms 0/ 100 = 0% 0/ 100 = 0% te0-0-0-13.ccr21.mia03.atlas.cogen
tco.com [154.54.12.209]
0/ 100 = 0% |
8 19ms 0/ 100 = 0% 0/ 100 = 0% be2055.ccr22.mia01.atlas.cogentco.
com [154.54.24.233]
0/ 100 = 0% |
9 30ms 0/ 100 = 0% 0/ 100 = 0% be2123.ccr42.atl01.atlas.cogentco.
com [154.54.24.197]
0/ 100 = 0% |
10 49ms 0/ 100 = 0% 0/ 100 = 0% be2099.ccr42.ord01.atlas.cogentco.
com [154.54.28.73]
0/ 100 = 0% |
11 61ms 0/ 100 = 0% 0/ 100 = 0% be2080.ccr22.yyz02.atlas.cogentco.
com [154.54.42.6]
0/ 100 = 0% |
12 --- 100/ 100 =100% 100/ 100 =100% te0-0-2-3.rcr11.b011027-3.yyz02.at
las.cogentco.com [154.54.6.242]
0/ 100 = 0% |
13 63ms 0/ 100 = 0% 0/ 100 = 0% 38.122.70.182
0/ 100 = 0% |
14 --- 100/ 100 =100% 100/ 100 =100% ae21.cr6.mtl.iweb.com [67.205.127.
121]
0/ 100 = 0% |
15 --- 100/ 100 =100% 100/ 100 =100% ae0.cr5.mtl.iweb.com [184.107.1.61
]
0/ 100 = 0% |
16 --- 100/ 100 =100% 100/ 100 =100% te7-4.dr9.mtl.iweb.com [184.107.1.
110]
0/ 100 = 0% |
17 63ms 0/ 100 = 0% 0/ 100 = 0% 72.55.128.44
0/ 100 = 0% |
18 64ms 0/ 100 = 0% 0/ 100 = 0% 184.107.107.176

Trace complete.