unreasonable lag since last maintenance

[Seaside8]

I've been lagging a lot since the last maintenance. Basically, everything stops then teleports to where it should be. I never had this issue before inside a dungeon, but now I can't tank Coil due to this lag. On the side note, I am still not lagging in any other games I play.

Are other people having this issue? If it is specific to me, what are the steps I need to take to address this issue?

[Fadian]

I'm having the same problem. spikes of lag of 5-6 seconds, happening on a constant 2-2 1/2 min cycle.

[Azryol]

Nope, i've been lagging like crazy too since the previous maintenance too

[Cidel]

Great. Now I don't feel like I'm the only one.

Hadn't had an issue with everything pausing every 10 seconds (except on Mondays after resets) until the last maintenance.

Seriously considering pingzapper or whatever its called because of it.

[Splice]

I'm willing to try anything I have the exact same issue every 2-3min. i get a 3-10 sec lag spike where everything stops on my screen (I AM STILL DOING STUFF IN GAME!!) and then the game goes in super fast forward mode and cetches up. I was in T5 coil final phase for the first time and this happenedd for a solid 20-30 sec. where I was unable to see anything I was doing but I was still doing ws's according to mumble users in my FC. Dives is nearly unplayable... praying its not the same tonight

[Logician]

I'm having the same problem except at the end of the lag spike I disconnect with an error 90000. Sometimes it happens as soon as I log in, other times I can play for a couple of minutes followed by a disconnect.

[Soloblade]

I've been getting massive lag too. Same error Code.
seems like they MIGHT have messed up last patch?

[Lurkios]

Error 90000 is just a timeout, pretty general unfortunately. Try pinging the SE servers while you're playing and see if there's any spikes in latency when you begin to lag in-game.

[Fadian]

I found the IP of the server I'm connecting to. Did some continuous ping tests and getting packet loss. I then did a trace and I noticed just before it gets to the Canada Data Server, there is a skip. before it goes and gets routed within the data center.

C:\Users\Nick>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 10.0.0.1
2 34 ms 36 ms 22 ms 69.254.103.1
3 10 ms 62 ms 10 ms xe-11-1-0-32767-sur02.ashgroverd.tn.nash.comcast
.net [68.85.135.253]
4 11 ms 11 ms 14 ms xe-5-0-9-0-ar01.goodslettvll.tn.nash.comcast.net
[68.86.176.61]
5 19 ms 24 ms 19 ms he-5-4-0-0-cr01.56marietta.ga.ibone.comcast.net
[68.86.90.189]
6 34 ms 37 ms 36 ms 23.30.207.98
7 92 ms 64 ms 63 ms vlan51.ebr1.Atlanta2.Level3.net [4.69.150.62]
8 60 ms 59 ms 59 ms ae-6-6.ebr1.Washington12.Level3.net [4.69.148.10
6]
9 62 ms 65 ms 61 ms ae-1-100.ebr2.Washington12.Level3.net [4.69.143.
214]
10 64 ms 72 ms 62 ms 4.69.201.69
11 61 ms 63 ms 64 ms ae-91-91.csw4.NewYork1.Level3.net [4.69.134.78]

12 63 ms 64 ms 62 ms ae-92-92.ebr2.NewYork1.Level3.net [4.69.148.45]

13 106 ms 276 ms 230 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
14 50 ms * 118 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

15 98 ms 114 ms 99 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
16 * * * Request timed out.
17 58 ms 43 ms 43 ms 192.34.76.2
18 43 ms 44 ms 43 ms 199.91.189.234
19 43 ms 43 ms 42 ms 199.91.189.38

Trace complete.

[JillyBean]

Can someone remind me how to do a ping check to the Montreal server?