Constant Lag Spikes

[min99]

Still can't play on Hyperion. Everything was okay even after the emergency maintenance last night, but since a few hours ago, I get horrible lag spikes and then eventually disconnect. I've never had any problems with my game connection before today.

[Auttoh]

This right here is your problem:

11 * * 140 ms if-1-2.tcore1.NYY-NewYork.as6453.net [66.198.127
6]
12 141 ms 143 ms * if-11-2.tcore2.NYY-NewYork.as6453.net [216.6.99.
]
13 * * * Request timed out.

I had the same problems until I closed the client and reloaded. I'm not being hopped through New York anymore, but Chicago and I'm stable.

Nope. Still going through NY.

[emmgee]

Its not on SE's end. I had lagpspike problems on east coast, switched to a VPN in chicago and its fine. Switch back and lag again. There's a hop somewhere between your ISP and the servers that is lagging/has packetloss.

[Marishi-Ten]

Its not on SE's end. I had lagpspike problems on east coast, switched to a VPN in chicago and its fine. Switch back and lag again. There's a hop somewhere between your ISP and the servers that is lagging/has packetloss.

Exactly. The company having the problem is:

as6453.net owned by TATA COMMUNICATIONS: http://www.tatacommunications.com/co...commitment.asp

[min99]

I'm on the west coast and my isp is wavecable.

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 10 ms 9 ms 11 ms 10.30.0.1
3 8 ms 7 ms 8 ms static-24-113-126-225.wavecable.com [24.113.126.
225]
4 32 ms 17 ms 14 ms wave-gw.ae0.sea-bdr1.noanet.net [64.146.252.253]

5 21 ms 17 ms 24 ms xe-0-3-1.3011.ptl-bdr0.noanet.net [64.184.133.12
2]
6 16 ms 13 ms 13 ms te3-3.ccr01.pdx01.atlas.cogentco.com [38.104.104
.181]
7 22 ms 13 ms 14 ms 154.54.89.54
8 26 ms 25 ms 23 ms te4-3.ccr01.boi01.atlas.cogentco.com [154.54.40.
98]
9 35 ms 34 ms 31 ms te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54
.40.89]
10 46 ms 42 ms 44 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
.69]
11 56 ms 64 ms 52 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26
.114]
12 73 ms 67 ms 74 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
13 83 ms 78 ms 81 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 80 ms 81 ms 80 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
15 87 ms 80 ms 80 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]
16 88 ms 89 ms 89 ms 38.122.70.182
17 87 ms 90 ms 87 ms te8-2.cr1.mtl.iweb.com [67.205.127.121]
18 96 ms 88 ms 114 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
19 88 ms 89 ms 88 ms 72.55.128.44
20 88 ms 89 ms 111 ms 184.107.107.176

Trace complete

I don't know very much about this, but I don't see a problem here, and I'm getting very bad lag and disconnects since about 11am pdt.

[Marishi-Ten]

I'm on the west coast and my isp is wavecable.

Tracing route to 184.107.107.176 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 10 ms 9 ms 11 ms 10.30.0.1
3 8 ms 7 ms 8 ms static-24-113-126-225.wavecable.com [24.113.126.
225]
4 32 ms 17 ms 14 ms wave-gw.ae0.sea-bdr1.noanet.net [64.146.252.253]

5 21 ms 17 ms 24 ms xe-0-3-1.3011.ptl-bdr0.noanet.net [64.184.133.12
2]
6 16 ms 13 ms 13 ms te3-3.ccr01.pdx01.atlas.cogentco.com [38.104.104
.181]
7 22 ms 13 ms 14 ms 154.54.89.54
8 26 ms 25 ms 23 ms te4-3.ccr01.boi01.atlas.cogentco.com [154.54.40.
98]
9 35 ms 34 ms 31 ms te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54
.40.89]
10 46 ms 42 ms 44 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
.69]
11 56 ms 64 ms 52 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26
.114]
12 73 ms 67 ms 74 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
13 83 ms 78 ms 81 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 80 ms 81 ms 80 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
15 87 ms 80 ms 80 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]
16 88 ms 89 ms 89 ms 38.122.70.182
17 87 ms 90 ms 87 ms te8-2.cr1.mtl.iweb.com [67.205.127.121]
18 96 ms 88 ms 114 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]
19 88 ms 89 ms 88 ms 72.55.128.44
20 88 ms 89 ms 111 ms 184.107.107.176

Trace complete

I don't know very much about this, but I don't see a problem here, and I'm getting very bad lag and disconnects since about 11am pdt.

Your not taking the normal hops that I see. Where are you located? Who is your ISP? You're being routed through a completely different backbone than most. Would you by chance be behind a VPN/Proxy or firewall?

You're hitting two completely different providers:

iweb - http://iweb.com/?sfcid=70130000000lE...FaU9QgodphcAiw
17 87 ms 90 ms 87 ms te8-2.cr1.mtl.iweb.com [67.205.127.121]
18 96 ms 88 ms 114 ms te7-4.dr9.mtl.iweb.com [184.107.1.110]

Cogent - http://www.cogentco.com/

8 26 ms 25 ms 23 ms te4-3.ccr01.boi01.atlas.cogentco.com [154.54.40.
98]
9 35 ms 34 ms 31 ms te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54
.40.89]
10 46 ms 42 ms 44 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
.69]
11 56 ms 64 ms 52 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26
.114]
12 73 ms 67 ms 74 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
13 83 ms 78 ms 81 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 80 ms 81 ms 80 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
15 87 ms 80 ms 80 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]

You have a TON of hops in multiple locations around the US. More so than normal:

8 26 ms 25 ms 23 ms te4-3.ccr01.boi01.atlas.cogentco.com [154.54.40.
98] - Boise, ID
9 35 ms 34 ms 31 ms te0-0-0-8.ccr21.slc01.atlas.cogentco.com [154.54
.40.89] - Salt Lake City, UT
10 46 ms 42 ms 44 ms be2127.ccr22.den01.atlas.cogentco.com [154.54.25
.69] - Denver, CO
11 56 ms 64 ms 52 ms be2129.mpd21.mci01.atlas.cogentco.com [154.54.26
.114] - I have no clue who this is. A quick Google search on it's domain did yield a ton of people unhappy about packet loss through that node.


These are all Houston, TX racks:

12 73 ms 67 ms 74 ms te0-4-0-3.mpd22.ord01.atlas.cogentco.com [154.54
.30.177]
13 83 ms 78 ms 81 ms be2079.ccr21.yyz02.atlas.cogentco.com [154.54.27
.182]
14 80 ms 81 ms 80 ms te7-1.mag02.yyz02.atlas.cogentco.com [154.54.40.
166]
15 87 ms 80 ms 80 ms te4-1.ccr01.yyz03.atlas.cogentco.com [154.54.45.
118]

I get the feeling that you may have trace routed the wrong IP. You don't seem to be hitting Montreal or any known providers Square goes through at all. Can you double check the IP that ffxi.exe is connecting to?

[aquelia]

Started having the rubber banding/people warping around /r0 for several seconds then everything starts going issue as of Monday evening 5pm pst 09/16/2013. Continues to persist every night when I play until now. Never had this issue in all of the beta even during stress test etc.

[min99]

I'm with Wavebroadband in Washington state and the trace is to 184.107.107.176. I'm not sure how to check what IP that ffxi.exe is connected to.

edit

No proxy or firewall.

edit edit Found it and I'm connected to 199.91.189.48. Did a ping and 100% packet loss

[faeyte]

I have had absolutely no connection issues from P3 Beta until last night's maintenance. Since then I've had nothing but 90000 disconnects after loading, constant lagspikes and even lobby server issues. Half the time the game wouldn't load properly and then 90000 error. Now it works fine to log in, but the porting around and lagging is insane.

My original thought was there must of been congestion somewhere on the route across canada. Done a traceroute to the server I am on (on the montreal datacenter), and not one hop is above 60ms.

My ISP does not throttle anything, there are no real limits on bandwidth, and there is sufficient bandwidth speeds to run probably 10 or more games on this connection.

Regardless, this is frustrating =/

[min99]

Here's the trace to the ip ffxiv is connecting to:

Tracing route to 199.91.189.48 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms www.asusnetwork.net [192.168.1.1]
2 9 ms 20 ms 9 ms 10.30.0.1
3 7 ms 7 ms 9 ms static-24-113-126-225.wavecable.com [24.113.126.
225]
4 35 ms 12 ms 31 ms 64.146.252.253
5 10 ms 8 ms 11 ms ae0-124.sea23.ip4.tinet.net [216.221.158.97]
6 124 ms 111 ms 160 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
7 116 ms * 116 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
8 121 ms * 118 ms 192.34.76.2
9 * 127 ms 117 ms 199.91.189.234
10 128 ms 140 ms 113 ms 199.91.189.48

Trace complete.