Lag spikes in game-- I don't know how to fix it.

Hello. I have been experiencing quite frequent lag spikes within the game. Things will stop, then catch up to themselves. Sometimes I do not see a cast bar or void zone before I am hit by an attack.

Here are a few trace routes to Excalibur (based off of arrstatus.com listed IP) that I did just for this post. I can reproduce this as frequently as I wish just by starting the trace. My ISP is Comcast; I have 32MB down and 7MB up (from Speedtest.net). Wired connection.

Code:

C:\Users\[redacted]>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 2 ms <1 ms <1 ms [redacted] 2 85 ms 42 ms 35 ms [redacted] 3 10 ms 15 ms 9 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 29 ms 13 ms 14 ms xe-2-0-11-0-ar03.nashville.tn.nash.comcast.net [ 162.151.9.21] 5 23 ms 11 ms 18 ms ae-3-0-ar01.goodslettvll.tn.nash.comcast.net [68 .86.148.69] 6 20 ms 23 ms 23 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 37 ms 37 ms 31 ms 23.30.207.98 8 60 ms 56 ms 57 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 61 ms 62 ms 59 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 62 ms 60 ms 59 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 58 ms 55 ms 58 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 56 ms 56 ms 71 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 60 ms 92 ms 58 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 193 ms 236 ms 238 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 45 ms 59 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 16 58 ms 63 ms 58 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 52 ms 52 ms 52 ms 192.34.76.10 18 53 ms 54 ms 52 ms 199.91.189.242 19 54 ms 68 ms 53 ms 199.91.189.38 Trace complete.

Code:

C:\Users\[redacted]>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms [redacted] 2 27 ms 29 ms 24 ms [redacted] 3 9 ms 8 ms 9 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 44 ms 11 ms 13 ms xe-2-0-11-0-ar03.nashville.tn.nash.comcast.net [ 162.151.9.21] 5 26 ms 13 ms 15 ms ae-3-0-ar01.goodslettvll.tn.nash.comcast.net [68 .86.148.69] 6 19 ms 20 ms 22 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 34 ms 31 ms 32 ms 23.30.207.98 8 55 ms 54 ms 58 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 62 ms 81 ms 58 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 57 ms 56 ms 56 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 58 ms 60 ms 58 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 59 ms 56 ms 59 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 58 ms 60 ms 57 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 60 ms 56 ms 56 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 241 ms 208 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 16 64 ms 57 ms 56 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 55 ms 57 ms 57 ms 192.34.76.10 18 54 ms 52 ms 53 ms 199.91.189.242 19 52 ms 99 ms 54 ms 199.91.189.38 Trace complete.

Code:

C:\Users\[redacted]>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms [redacted] 2 33 ms 29 ms 25 ms [redacted] 3 9 ms 12 ms 10 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 106 ms 16 ms 11 ms xe-2-0-11-0-ar03.nashville.tn.nash.comcast.net [ 162.151.9.21] 5 11 ms 18 ms 12 ms ae-3-0-ar01.goodslettvll.tn.nash.comcast.net [68 .86.148.69] 6 19 ms 19 ms 19 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 33 ms 42 ms 34 ms 23.30.207.98 8 59 ms 60 ms 60 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 58 ms 61 ms 57 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 82 ms 56 ms 57 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 68 ms 55 ms 58 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 58 ms 60 ms 55 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 55 ms 56 ms 57 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 60 ms 59 ms 56 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 125 ms * 48 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 16 60 ms 59 ms 58 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 56 ms 52 ms 54 ms 192.34.76.10 18 52 ms 54 ms 53 ms 199.91.189.242 19 52 ms 55 ms 55 ms 199.91.189.38 Trace complete.

Code:

C:\Users\[redacted]>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms [redacted] 2 38 ms 30 ms 29 ms [redacted] 3 42 ms 12 ms 12 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 13 ms 11 ms 11 ms xe-2-0-11-0-ar03.nashville.tn.nash.comcast.net [ 162.151.9.21] 5 12 ms 19 ms 13 ms ae-3-0-ar01.goodslettvll.tn.nash.comcast.net [68 .86.148.69] 6 22 ms 22 ms 22 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 39 ms 35 ms 31 ms 23.30.207.98 8 51 ms 53 ms 52 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 59 ms 54 ms 57 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 57 ms 58 ms 57 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 54 ms 56 ms 62 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 58 ms 56 ms 60 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 59 ms 59 ms 58 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 53 ms 214 ms 232 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 46 ms * 48 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 16 58 ms 58 ms 58 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 90 ms 52 ms 53 ms 192.34.76.10 18 54 ms 53 ms 51 ms 199.91.189.242 19 52 ms 68 ms 52 ms 199.91.189.38 Trace complete.

Is there anything I can do besides paying for something like pingzapper?

Help appreciated.

EDIT: I just did another trace. I did have packet loss at hop 7, but this time hop 15 timed out completely.

Code:

C:\Users\[redacted]>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms [redacted] 2 37 ms 25 ms 28 ms [redacted] 3 24 ms 11 ms 9 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 11 ms 14 ms 14 ms xe-2-0-11-0-ar03.nashville.tn.nash.comcast.net [ 162.151.9.21] 5 10 ms 11 ms 12 ms ae-3-0-ar01.goodslettvll.tn.nash.comcast.net [68 .86.148.69] 6 28 ms 23 ms 19 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 * 35 ms 33 ms 23.30.207.98 8 62 ms 59 ms 58 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 58 ms 61 ms 69 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 59 ms 58 ms 60 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 59 ms 62 ms 62 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 58 ms 61 ms 59 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 60 ms 63 ms 59 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 157 ms 225 ms 225 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 * * * Request timed out. 16 58 ms 62 ms 63 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 53 ms 54 ms 52 ms 192.34.76.10 18 68 ms 52 ms 54 ms 199.91.189.242 19 56 ms 54 ms 54 ms 199.91.189.38 Trace complete

Oh look, we have something in common. Fix your stuff SE Please.

Code:

tracert 199.91.189.23 2 39 ms 28 ms 9 ms 3 31 ms 12 ms 8 ms 4 16 ms 15 ms 48 ms 5 20 ms 20 ms 22 ms 6 20 ms 35 ms 19 ms xe-8-2-3.edge3.Denver1.Level3.net [4.28.20.29] 7 62 ms 62 ms 65 ms vlan52.ebr2.Denver1.Level3.net [4.69.147.126] 8 79 ms 66 ms 66 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62] 9 65 ms 63 ms 94 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189] 10 65 ms 65 ms * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] 11 64 ms 111 ms 63 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 12 68 ms * 68 ms 192.34.76.10 13 64 ms 94 ms 63 ms 199.91.189.242 14 64 ms 63 ms * 199.91.189.23 15 82 ms 66 ms * 199.91.189.23 16 66 ms 66 ms 63 ms 199.91.189.23 Trace complete.

Code:

Tracing route to 199.91.189.23 over a maximum of 30 hops 2 12 ms 10 ms 9 ms 3 10 ms 12 ms 9 ms 4 67 ms 17 ms 13 ms 5 * 62 ms 36 ms host-72-175-5-65.grf-mt.client.bresnan.net [72.1 75.5.65] 6 136 ms 114 ms 21 ms xe-8-2-3.edge3.Denver1.Level3.net [4.28.20.29] 7 65 ms 97 ms 62 ms vlan52.ebr2.Denver1.Level3.net [4.69.147.126] 8 61 ms 73 ms 63 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62] 9 68 ms 100 ms 98 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189] 10 70 ms * 65 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] 11 65 ms 64 ms 69 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 12 63 ms 65 ms 108 ms 192.34.76.10 13 78 ms 82 ms 78 ms 199.91.189.242 14 66 ms 66 ms 65 ms 199.91.189.23 Trace complete.

Code:

Tracing route to 199.91.189.23 over a maximum of 30 hops 2 10 ms 10 ms 42 ms 3 14 ms 9 ms 9 ms 4 17 ms 12 ms 12 ms 5 43 ms 53 ms 21 ms 6 19 ms 19 ms * xe-8-2-3.edge3.Denver1.Level3.net [4.28.20.29] 7 63 ms 100 ms 78 ms vlan52.ebr2.Denver1.Level3.net [4.69.147.126] 8 61 ms * 66 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62] 9 * 62 ms 94 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189] 10 184 ms 216 ms 221 ms ae-10-10.car2.Montreal2.Level3.net [4.69.153.86] 11 72 ms 67 ms 66 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 12 69 ms 63 ms 62 ms 192.34.76.10 13 81 ms * 62 ms 199.91.189.242 14 78 ms 81 ms 63 ms 199.91.189.23

You either have to use a VPN, like WTFast, pingzapper, battleping, ect (which also require subscriptions and is not always a 100% fix), change your ISP, or wait until the problem sorts itself out.

Just as Vanroe suggested, try out those, I have 25mb down/2.5mb up and never had lag during alpha, beta 1, and 2. But started seeing more and more lag, specially once I hit Titan HM it was to a point I couldn't play. (couldn't dodge land slide even if I did on my screen)

Pingzapper lets you try out for free forever with a 1 hour per usage restriction, so you may want to try it out using that, if it works, I know it sucks but buying monthly subs to keep the connection going would be good. I didn't want to pay extra but at same time I want to keep on playing XIV so I just paid it, you get 2 simultaneous connection so if you're like me with me and my wife both playing, it covered both of us.

Aside from this we can only hope it gets fixed from SE's/ISP's end.

it's sad how we have to use a third party program... to get the ping that we need to play the game correctly. While they promote not using third party programs

Quote:

Originally Posted by Mikeo

it's sad how we have to use a third party program... to get the ping that we need to play the game correctly. While they promote not using third party programs

Yeah, there are a plethora of people with similar issues which you are experiencing (myself included). It's a pity no reps have been commenting on this.

Today's trace routes:

Code:

C:\Users\>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms 1 ms 2 40 ms 29 ms 12 ms 3 13 ms 13 ms 10 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 13 ms 11 ms 18 ms xe-2-0-11-0-ar03.nashville.tn.nash.comcast.net [ 162.151.9.21] 5 35 ms 23 ms 11 ms ae-3-0-ar01.goodslettvll.tn.nash.comcast.net [68 .86.148.69] 6 20 ms 27 ms 23 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 40 ms 56 ms 39 ms 23.30.207.98 8 63 ms 67 ms 65 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 62 ms 66 ms 66 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 70 ms 68 ms 63 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 63 ms 65 ms 67 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 73 ms 63 ms 65 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 65 ms 65 ms 98 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 97 ms 240 ms 213 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 248 ms 219 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 16 64 ms 67 ms 65 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 53 ms 54 ms 55 ms 192.34.76.10 18 51 ms 52 ms 52 ms 199.91.189.242 19 55 ms 54 ms 59 ms 199.91.189.38 Trace complete.

Code:

C:\Users\>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 2 38 ms 28 ms 18 ms 3 11 ms 10 ms 10 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 10 ms 9 ms 9 ms xe-11-3-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.85.174.22] 5 18 ms 12 ms 12 ms xe-0-0-8-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.53] 6 20 ms 20 ms 23 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 34 ms 33 ms 82 ms 23.30.207.98 8 61 ms 63 ms 61 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 62 ms 61 ms 60 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 64 ms 59 ms 60 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 63 ms 63 ms 65 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 62 ms 63 ms 62 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 61 ms 60 ms 60 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 120 ms 209 ms 88 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 46 ms * * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 16 65 ms 64 ms 63 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 54 ms 54 ms 55 ms 192.34.76.10 18 47 ms 47 ms 48 ms 199.91.189.242 19 53 ms 52 ms 54 ms 199.91.189.38 Trace complete.

Quote:

Originally Posted by Priya

Today's trace routes:

Code:

C:\Users\[redacted]>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms 1 ms [redacted] 2 40 ms 29 ms 12 ms [redacted] 3 13 ms 13 ms 10 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 13 ms 11 ms 18 ms xe-2-0-11-0-ar03.nashville.tn.nash.comcast.net [ 162.151.9.21] 5 35 ms 23 ms 11 ms ae-3-0-ar01.goodslettvll.tn.nash.comcast.net [68 .86.148.69] 6 20 ms 27 ms 23 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 40 ms 56 ms 39 ms 23.30.207.98 8 63 ms 67 ms 65 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 62 ms 66 ms 66 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 70 ms 68 ms 63 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 63 ms 65 ms 67 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 73 ms 63 ms 65 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 65 ms 65 ms 98 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 97 ms 240 ms 213 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 248 ms 219 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 16 64 ms 67 ms 65 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 53 ms 54 ms 55 ms 192.34.76.10 18 51 ms 52 ms 52 ms 199.91.189.242 19 55 ms 54 ms 59 ms 199.91.189.38 Trace complete.

Code:

C:\Users\[redacted]>tracert 199.91.189.38 Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 2 36 ms 20 ms 22 ms 3 10 ms 9 ms 9 ms xe-11-0-0-32767-sur01.murfreesboro.tn.nash.comca st.net [68.86.149.109] 4 9 ms 9 ms 9 ms xe-11-3-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.85.174.22] 5 16 ms 24 ms 12 ms xe-0-0-8-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.53] 6 23 ms 19 ms 19 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.189] 7 34 ms 32 ms 35 ms 23.30.207.98 8 61 ms 61 ms 77 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 9 65 ms 61 ms 62 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 10 61 ms 62 ms 62 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 11 62 ms 60 ms 59 ms ae-58-58.ebr1.NewYork1.Level3.net [4.69.201.69] 12 66 ms 61 ms 61 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 13 61 ms 59 ms 61 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 14 59 ms 60 ms 62 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 15 104 ms 158 ms 173 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 16 60 ms 60 ms 61 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 17 55 ms 53 ms 53 ms 192.34.76.10 18 48 ms 47 ms 48 ms 199.91.189.242 19 54 ms 56 ms 54 ms 199.91.189.38 Trace complete.

Looks better. You're still getting some dropped packets at the Level3 Montreal node:

15 248 ms 219 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

Looks better though.

Why are you going though a VLAN?

8 61 ms 61 ms 77 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]

Also, why are you being routed though Atlanta when you're in TN?

I don't know the answer to any of those questions. :(

I'm also moving in a month, so in all likelihood my new ISP is going to route differently; it won't be Comcast. I know I have to use like Battleping or Pingzapper at least until I leave here, but I figured I'd just spam this thread with daily trace routes. I don't want SE thinking it's all good and close it.

I replaced that second one with one that I did right after which lost more packets; but it typically always looks like those. One or two times just now I got a clean trace with 40ms across the board... if only it would stay that way.

This happens to me as well - Severe Rubberbanding - Comcast

It's interesting that all of your tracerts are showing montreal as the problem.
I wish I had run some myself last night, but this is the first time that it's been really bad for me and I couldn't figure out what was going wrong.

Quote:

Originally Posted by Vanroe

change your ISP, or wait until the problem sorts itself out.

Your suggestion as far as changing ISPs, think harder:
- Typically a large cancellation fee involved as many are under a contract.
- Some areas don't have other ISP options.
- If this player is satisfied with everything their ISP offers and have zero issues with other Internet Services. Why should they switch due too one issue aka FFXIV?
- For me, my distance has nothing to do with the problem. FFXIV is the only problem and it's not my ISP's problem either.
- Switching ISP's isn't a solution, its a gamble. Your location isn't changed, who says the routing will bypass the affected hop(s).

This issue has been going on for more than a month and it wasn't an issue prior.

The problem at hand is SE needs to work with Level 3 and fix the issue as it is affecting their customers and their level of service. Whether it is routing, hardware, or bandwidth. Level 3 is the first hop for thousands right outside of SE's own network in Montreal. It is common practice for companies that provide a service via Internet.

I am still waiting patiently for resolve (my current option). I've taken all avenues even though it is not even my responsibility. Yet there are thousands of posts, hundreds of tracert and packet loss results pointing to Level 3 Montreal. Still, not a peep from SE.

If they don't resolve it. Well, its already happening, customers complaining or not. They are and will be losing subs as Level 3 has a large share of Networks in and out of Montreal, a major artery to SE's heart.

Exact same issue. Been happening the past few weeks, and never before that.
Also of note -- it's ONLY on Verizon. I play on my friend's Comcast connection and don't have a problem.
Packet loss at Level3 Montreal... see below.

Code:

Tracing route to 199.91.189.23 over a maximum of 30 hops 1 5 ms <1 ms <1 ms 2 5 ms 4 ms 4 ms 3 8 ms 7 ms 7 ms G0-6-1-6.PHLAPA-LCR-22.verizon-gni.net [130.81.1 83.108] 4 8 ms 6 ms 7 ms ae0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.209.1 86] 5 * 9 ms 9 ms 0.xe-2-1-0.BR2.IAD8.ALTER.NET [152.63.5.245] 6 32 ms 31 ms 29 ms ae17.edge1.washingtondc12.level3.net [4.68.62.13 7] 7 42 ms 42 ms 41 ms vl-3601-ve-225.ebr2.Washington12.Level3.net [4.6 9.158.34] 8 39 ms 39 ms 39 ms ae-56-56.ebr1.NewYork1.Level3.net [4.69.201.61] 9 43 ms 39 ms 39 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74] 10 53 ms 39 ms 37 ms ae-82-82.ebr2.NewYork1.Level3.net [4.69.148.41] 11 159 ms 141 ms 247 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 12 20 ms 19 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 13 40 ms 39 ms 42 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 14 35 ms 34 ms 34 ms 192.34.76.10 15 41 ms 39 ms 39 ms 199.91.189.242 16 35 ms 34 ms 34 ms 199.91.189.23 Trace complete.

Our house has also been experiencing dramatic lag spikes. It'll hit my BF and I at separate times even though we're on the same ISP. We've no issues with any other games or aspects of our network: just ffxiv. The lag spikes hitting us at different times has made it rough to play together. If his lag isn't making the game unplayable, mine is.

Traces from now.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 1 ms <1 ms <1 ms 2 10 ms 9 ms 8 ms 3 8 ms 15 ms 9 ms 4 9 ms 9 ms 8 ms xe-8-3-0-0-sur01.murfreesboro.tn.nash.comcast.ne t [68.86.148.94] 5 8 ms 9 ms 9 ms xe-11-2-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.86.176.110] 6 27 ms 21 ms 12 ms xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105] 7 21 ms 19 ms 19 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101] 8 36 ms 37 ms 36 ms 23.30.207.98 9 61 ms 61 ms 68 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 10 65 ms 62 ms 61 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 11 61 ms 62 ms 63 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 12 62 ms 61 ms 60 ms ae-57-57.ebr1.NewYork1.Level3.net [4.69.201.65] 13 62 ms 61 ms 62 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 64 ms 63 ms 61 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 62 ms 64 ms 64 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 16 * * 45 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 17 63 ms 63 ms 63 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 18 51 ms 53 ms 51 ms 192.34.76.10 19 52 ms 51 ms 53 ms 199.91.189.242 20 52 ms 53 ms 53 ms 199.91.189.38 Trace complete.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 2 10 ms 9 ms 10 ms 3 10 ms 8 ms 11 ms 4 9 ms 9 ms 8 ms xe-8-3-0-0-sur01.murfreesboro.tn.nash.comcast.ne t [68.86.148.94] 5 10 ms 9 ms 9 ms xe-11-2-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.86.176.110] 6 10 ms 17 ms 10 ms xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105] 7 21 ms 19 ms 19 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101] 8 39 ms 39 ms 38 ms 23.30.207.98 9 64 ms 63 ms 68 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 10 64 ms 63 ms 62 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 11 64 ms 71 ms 67 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 12 63 ms 76 ms 64 ms ae-57-57.ebr1.NewYork1.Level3.net [4.69.201.65] 13 67 ms 64 ms 61 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 65 ms 68 ms 64 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 69 ms 205 ms 69 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 16 * 47 ms 46 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 17 72 ms 64 ms 63 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 18 51 ms 51 ms 51 ms 192.34.76.10 19 52 ms 67 ms 53 ms 199.91.189.242 20 53 ms 53 ms 52 ms 199.91.189.38 Trace complete.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 2 9 ms 14 ms 9 ms 3 9 ms 10 ms 9 ms 4 9 ms 9 ms 9 ms xe-8-3-0-0-sur01.murfreesboro.tn.nash.comcast.ne t [68.86.148.94] 5 8 ms 9 ms 9 ms xe-11-2-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.86.176.110] 6 11 ms 14 ms 22 ms xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105] 7 20 ms 20 ms 19 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101] 8 39 ms 40 ms 39 ms 23.30.207.98 9 65 ms 68 ms 66 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 10 66 ms 65 ms 65 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 11 65 ms 63 ms 65 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 12 65 ms 63 ms 64 ms ae-57-57.ebr1.NewYork1.Level3.net [4.69.201.65] 13 65 ms 61 ms 61 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 65 ms 82 ms 63 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 265 ms 223 ms 203 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 16 60 ms 45 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 17 71 ms 63 ms 63 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 18 51 ms 52 ms 51 ms 192.34.76.10 19 52 ms 52 ms 52 ms 199.91.189.242 20 51 ms 51 ms 52 ms 199.91.189.38 Trace complete.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 2 14 ms 10 ms 9 ms 3 12 ms 10 ms 10 ms 4 9 ms 19 ms 10 ms xe-8-3-0-0-sur01.murfreesboro.tn.nash.comcast.ne t [68.86.148.94] 5 8 ms 8 ms 11 ms xe-11-2-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.86.176.110] 6 22 ms 11 ms 17 ms xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105] 7 19 ms 19 ms 23 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101] 8 38 ms 42 ms 41 ms 23.30.207.98 9 71 ms 65 ms 66 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 10 65 ms 65 ms 65 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 11 66 ms 65 ms 62 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 12 63 ms 64 ms 68 ms ae-57-57.ebr1.NewYork1.Level3.net [4.69.201.65] 13 65 ms 64 ms 66 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 63 ms 65 ms 69 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 75 ms 63 ms 64 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 16 * 48 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 17 65 ms 68 ms 66 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 18 51 ms 53 ms 52 ms 192.34.76.10 19 51 ms 70 ms 61 ms 199.91.189.242 20 52 ms 58 ms 52 ms 199.91.189.38 Trace complete.

Just a bump. Same stuff. (At noon on a Saturday, no less.)

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 1 ms 1 ms <1 ms 2 10 ms 12 ms 9 ms 3 9 ms 37 ms 10 ms 4 9 ms 11 ms 8 ms xe-8-3-0-0-sur01.murfreesboro.tn.nash.comcast.ne t [68.86.148.94] 5 10 ms 9 ms 9 ms xe-11-2-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.86.176.110] 6 10 ms 22 ms 11 ms xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105] 7 22 ms 20 ms 19 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101] 8 34 ms 33 ms 33 ms 23.30.207.98 9 47 ms 47 ms 47 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 10 47 ms 46 ms 47 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 11 52 ms 52 ms 48 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 12 52 ms 59 ms 54 ms ae-57-57.ebr1.NewYork1.Level3.net [4.69.201.65] 13 49 ms 47 ms 45 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 48 ms 48 ms 48 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 47 ms 47 ms 49 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 16 99 ms 206 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 17 50 ms 46 ms 45 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 18 54 ms 53 ms 52 ms 192.34.76.10 19 48 ms 48 ms 50 ms 199.91.189.242 20 52 ms 55 ms 54 ms 199.91.189.38 Trace complete.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 1 ms 1 ms <1 ms 2 8 ms 9 ms 8 ms 3 8 ms 9 ms 13 ms 4 11 ms 9 ms 9 ms xe-8-3-0-0-sur01.murfreesboro.tn.nash.comcast.ne t [68.86.148.94] 5 11 ms 9 ms 15 ms xe-11-2-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.86.176.110] 6 11 ms 36 ms 11 ms xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105] 7 22 ms 19 ms 19 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101] 8 31 ms 32 ms 30 ms 23.30.207.98 9 46 ms 49 ms 64 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 10 50 ms 46 ms 45 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 11 45 ms 47 ms 45 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 12 48 ms 48 ms 54 ms ae-57-57.ebr1.NewYork1.Level3.net [4.69.201.65] 13 55 ms 49 ms 50 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 45 ms 46 ms 46 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 159 ms 211 ms 213 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 16 45 ms 47 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 17 46 ms 47 ms 47 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 18 53 ms 54 ms 51 ms 192.34.76.10 19 56 ms 49 ms 47 ms 199.91.189.242 20 50 ms 52 ms 53 ms 199.91.189.38 Trace complete.

Sick of this now... Would be great to have a single response on the matter from a mod/dev but I doubt we'll get it, as SE responding to our problem is SE acknowledging their is a problem in the first place.

Blind eyes have been turned.

I've just contacted Level 3 directly, here is the link to the contact form if you wish to do the same.

http://www.level3.com/en/forms/contactus_prim/

If anyone uses the above form, you can put N/A in the company part.

Bump. Traces done at 7:15pm Central time.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 2 ms <1 ms <1 ms 2 10 ms 9 ms 10 ms 3 13 ms 9 ms 10 ms 4 8 ms 9 ms 10 ms xe-8-3-0-0-sur01.murfreesboro.tn.nash.comcast.ne t [68.86.148.94] 5 42 ms 9 ms 16 ms xe-11-2-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.86.176.110] 6 11 ms 12 ms 25 ms xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105] 7 21 ms 19 ms 19 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101] 8 36 ms 36 ms 36 ms 23.30.207.98 9 63 ms 64 ms 64 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 10 64 ms 62 ms 64 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 11 69 ms 64 ms 60 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 12 62 ms 63 ms 64 ms ae-57-57.ebr1.NewYork1.Level3.net [4.69.201.65] 13 63 ms 61 ms 63 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 63 ms 63 ms 65 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 66 ms 63 ms 62 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 16 * 46 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 17 62 ms 62 ms 63 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 18 54 ms 52 ms 50 ms 192.34.76.10 19 48 ms 47 ms 50 ms 199.91.189.242 20 51 ms 52 ms 51 ms 199.91.189.38 Trace complete.

Code:

Tracing route to 199.91.189.38 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 2 9 ms 8 ms 9 ms 3 9 ms 9 ms 8 ms 4 10 ms 16 ms 17 ms xe-8-3-0-0-sur01.murfreesboro.tn.nash.comcast.ne t [68.86.148.94] 5 18 ms 9 ms 9 ms xe-11-2-0-0-sur02.murfreesboro.tn.nash.comcast.n et [68.86.176.110] 6 12 ms 17 ms 12 ms xe-0-0-9-0-ar01.goodslettvll.tn.nash.comcast.net [68.86.176.105] 7 21 ms 20 ms 19 ms he-5-5-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.90.101] 8 35 ms 36 ms 35 ms 23.30.207.98 9 61 ms 60 ms 59 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62] 10 64 ms 65 ms 62 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10 6] 11 62 ms 70 ms 62 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143. 214] 12 58 ms 61 ms 66 ms ae-57-57.ebr1.NewYork1.Level3.net [4.69.201.65] 13 60 ms 64 ms 63 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 14 61 ms 62 ms 63 ms ae-62-62.ebr2.NewYork1.Level3.net [4.69.148.33] 15 128 ms 215 ms 220 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5] 16 * 45 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1] 17 65 ms 62 ms 61 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178. 74] 18 51 ms 52 ms 52 ms 192.34.76.10 19 47 ms 47 ms 49 ms 199.91.189.242 20 52 ms 52 ms 51 ms 199.91.189.38 Trace complete.

Please see this thread, though specifically about FIOS, helps prove your Montreal2 routing center issue.

We have no solution at this time.

I know the players in tech support can't fix anything; however, I will continue to occasionally bump this, because if a thread goes too long with nothing SE moves it to "resolved." This hasn't been resolved, yet.

I've linked this thread in a few places; it wasn't in the FIOS one so I've added it. Thanks.

Fix your shit SE

Sure ill use a 3rd party program to get the required ping, oh wait im a PS3 user I cant do that... Fix your shit SE

If you're running through that Montreal server there's really not a lot you can do aside from the afformentioned VPN service, changing your ISP or just waiting it out.

Quote:

Originally Posted by Lurkios

If you're running through that Montreal server there's really not a lot you can do aside from the afformentioned VPN service, changing your ISP or just waiting it out.

I have pingzapper. I go through Chicago with it, and most of the time it is stable enough. It works better than going through New York anyway. I've never had to use one before, and I'm not happy about it. I'm waiting, but I will keep posting traces anyway. I don't really have a reason to bump without them as it's present everytime I trace; time of day or day of the week has no bearing.

As for ISP, I'm moving soon and there is only one option at my new place. It's a local phone company, and it travels the s ame route as my current Comcast does once it hits Atlanta. I've done traces on it with the same results. I will have no choice then.

Quote:

Originally Posted by Priya

I have pingzapper. I go through Chicago with it, and most of the time it is stable enough. It works better than going through New York anyway. I've never had to use one before, and I'm not happy about it. I'm waiting, but I will keep posting traces anyway. I don't really have a reason to bump without them as it's present everytime I trace; time of day or day of the week has no bearing.

I'm in pretty much the same boat. Using BattlePing myself, it's cleared up the issue for me entirely - but I'm not overly happy about having to pay for an additional service to play just this one game smoothly either (every other game I own works fine, datacenter location for FFXIV is just terrible).

You know what, pingzapper doesn't even help now... I know I said it helps but dunno what SE or who did what but damn the lag spikes in the last week or two has been horrible. I reset my router, checked that pingzapper is running correctly and routed to different tunnels to see if it'll help if I take a different route to SE's server but nothing is working. I get lag at Revenants Toll & worse lag spikes inside instanced dungeon/primal battles/CT. I contacted pingzapper customer service and they are looking into the matter on their end.

Does anyone know how to check routing after connecting to services like pingzapper? Traceroute only works directly from your PC to the server right? I know VPN will change that but pingzapper is just a proxy so guessing it handles differently, only for that game/program being used for rerouting. The ping rate showing on pingzapper, I'm guessing is from your PC to their routing server.

Quote:

Originally Posted by Reinheart

You know what, pingzapper doesn't even help now... I know I said it helps but dunno what SE or who did what but damn the lag spikes in the last week or two has been horrible.

I don't know how to check pingzapper's route, but that is something I'd like to know as well; I'm not very network savvy. I can recommend staying far away from NewYork2 though, assuming you get the same server options as me. It's been coming back with very frequent ??? when I ping it in pingzapper which I assume is something akin to packetloss. For me Chicago2 is the most stable. I see jumps at all the other northern options.

Quote:

Originally Posted by Priya

I don't know how to check pingzapper's route, but that is something I'd like to know as well; I'm not very network savvy. I can recommend staying far away from NewYork2 though, assuming you get the same server options as me. It's been coming back with very frequent ??? when I ping it in pingzapper which I assume is something akin to packetloss. For me Chicago2 is the most stable. I see jumps at all the other northern options.

It used to be fine on Los Angeles 2, then I switched to Chicago 2, then New York 1, but right now everything seems bad ><

I don't mean to change where your hate is directed, but as a player who's experienced this all through 2.1, here's what you should know:
I'm on Verizon FIOS. From what I've seen, we all port through Level3. Level3 gets overloaded and causes packet loss. The only way we can fix this is by calling your ISP, notifying them of the issue and to contact Level3, and/or ask for a different route.

I have been having this issue for the past week too. Never had lagspikes before.

I dont know how to word this correctly as I was told by a friend. Most house hold internet run on a stack 3 very basic tranmitting data.. You want to call you isp and ask for a stack 5.. Your internet will get slower download rate but packets are sent twice and more stable... Basically normal adsl2 is a foot ib the door for gaming, adsl2 stack 5 is both feet in the door

Quote:

Originally Posted by Zor

I dont know how to word this correctly as I was told by a friend. Most house hold internet run on a stack 3 very basic tranmitting data.. You want to call you isp and ask for a stack 5.. Your internet will get slower download rate but packets are sent twice and more stable... Basically normal adsl2 is a foot ib the door for gaming, adsl2 stack 5 is both feet in the door

Interesting. I'll be sure to ask for this and see what happens. Especially as I'll be on dsl when I move; right now it's cable. Thank you.

Quote:

Originally Posted by Zor

I dont know how to word this correctly as I was told by a friend. Most house hold internet run on a stack 3 very basic tranmitting data.. You want to call you isp and ask for a stack 5.. Your internet will get slower download rate but packets are sent twice and more stable... Basically normal adsl2 is a foot ib the door for gaming, adsl2 stack 5 is both feet in the door

Do you mean the protocol stack suites? Client/Host data translations normally dictate what stack the traffic is shaped on. If the suite is different, they client/host may ignore eachother. All the stacks are is layer of suite sequencing that the ISP may be able to change (changing ICMP to FTP), but in the long run hurt you.

Do you mean having your IPvxx changed on the ISP side? Most if not all IPv's are backward compatible with one another so if you use IPv6 and the host is IPv5, IPv6 will change it's sequencing over.

You could also mean the shaping of the data from client to host, which you CANNOT do (changing ICMP to TCP/UDP). XIV uses ICMP data shaping. If the host doesn't see ICMP traffic, it will likely ignore it.

http://en.wikipedia.org/wiki/Internet_protocol_suite

http://netlab.gmu.edu/networkbench/Ch01.pdf

Quote:

Originally Posted by Rose-Wild

I have been having this issue for the past week too. Never had lagspikes before.

Have had lagspike issue from Monday at least. Haven't been able to do any content because of it.

Playing from Finland on Balmung, not having any other issues with internet connection. My husband playing from same address also has lag spikes at the same time I do.