unreasonable lag since last maintenance

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?

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

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

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.

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

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.

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

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.

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.

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

I was lagging like this before the maintenance, I've had no problems since then. Dunno what's happening to you guys.

I'm still lagging a tiny bit, but way less since the last maintenance.

It seems that every maintenance they resolve some of the peoples lagging problems but at the same time manages to cause a completely entire group to have the lag.

Still having the issue :/

I've been skipping frames like I am some sort of bad stop-motion animation. :(
This never happened until recently...

I've always had some lag, but never this bad!

Tracing route to 199.91.189.18 over a maximum of 30 hops

1 629 ms 141 ms 27 ms cpe-108-184-240-1.socal.res.rr.com [108.184.240.1]
2 12 ms 14 ms 36 ms tge0-7-0-5.vnnzca2401h.socal.rr.com [76.166.5.133]
3 22 ms 13 ms 30 ms agg11.vnnycajz01r.socal.rr.com [72.129.14.96]
4 34 ms 52 ms 14 ms agg29.lsancarc01r.socal.rr.com [72.129.13.0]
5 27 ms 17 ms 13 ms bu-ether26.lsancarc0yw-bcr00.tbone.rr.com [66.109.6.212]
6 13 ms 17 ms 32 ms 107.14.19.138
7 28 ms 32 ms 104 ms 66.109.9.122
8 95 ms 88 ms 99 ms vlan70.csw2.LosAngeles1.Level3.net [4.69.144.126]
9 89 ms 89 ms 109 ms ae-72-72.ebr2.LosAngeles1.Level3.net [4.69.137.21]
10 88 ms 94 ms 90 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
11 87 ms 86 ms 85 ms ae-93-93.csw4.Dallas1.Level3.net [4.69.151.169]
12 99 ms 90 ms 87 ms ae-91-91.ebr1.Dallas1.Level3.net [4.69.151.162]
13 115 ms 89 ms 89 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]
14 95 ms 96 ms 96 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]
15 99 ms 89 ms 111 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
16 * * * Request timed out.
17 91 ms 87 ms 92 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
18 107 ms 118 ms 113 ms 10.2.2.1
19 135 ms 122 ms 120 ms 192.34.76.2
20 125 ms 150 ms 136 ms 199.91.189.234
21 * 105 ms 141 ms 199.91.189.18

Trace complete.

Can I get a post from a moderator addressing the issue? Why is it that it takes them less than 15 minutes to shutdown posts that have "already been solved," but they just leave us to complain among ourselves when there's an issue that has not been addressed?

Can we at least get an acknowledgement of the problem?

My tracert always shows problems at Montreal1.Level3.net and Montreal2.Level3.net during peak times.
I'm in upstate NY and have TWC.

I finally decided to capture it on video because it happens every night and seemingly is getting worse...
http://www.youtube.com/watch?v=HvkL3M9zsCU

find the ip of your servers on this website http://www.arrstatus.com/ and ping it , open the command window by type in the search box cmd, and then type: ping xxx.xx.xxx.xx -t (note this is an infinity loop,so stop it manually with ctrl-c)
I think most of you who live in the US don't have latency problem but the package lost problem. check the result of the percentage of the packet lost.

the command "tracert xxx.xx.xxx.xx" will show you the route that the signal takes to get from your computer to the server and the ping of each individual router along the way. If you run that a few times during prime time in your area, one or more of the addresses will have lost packets and/or unusually high latency likely from data loss. I pasted my results below for the diabolos server.


Tracing route to 199.91.189.38 over a maximum of 30 hops

1 39 ms 17 ms 32 ms
2 18 ms 11 ms 11 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
3 12 ms 11 ms 13 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
4 15 ms 13 ms 12 ms rdc-74-76-243-78.alb.east.twcable.com [74.76.243.78]
5 25 ms 23 ms 22 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 20 ms 23 ms 23 ms 107.14.19.26
7 21 ms 22 ms 22 ms 66.109.1.36
8 21 ms * 20 ms ae9.edge3.Newark1.Level3.net [4.68.63.21]
9 35 ms 36 ms 37 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
10 51 ms 34 ms 34 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
11 155 ms 214 ms 236 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
12 29 ms * 30 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
13 37 ms 31 ms 31 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
14 42 ms 44 ms 79 ms 10.2.2.1
15 * 45 ms 43 ms 192.34.76.2
16 43 ms 44 ms 44 ms 199.91.189.234
17 44 ms 43 ms 41 ms 199.91.189.38

Trace complete.

Tracing route to 199.91.189.38 over a maximum of 30 hops

1 41 ms 27 ms 16 ms
2 12 ms 31 ms 12 ms gig8-45.schnny52-rtr001.alb.northeast.rr.com [24.29.46.197]
3 27 ms 11 ms 13 ms rdc-74-76-241-78.alb.northeast.rr.com [74.76.241.78]
4 13 ms 44 ms 11 ms rdc-74-76-243-78.alb.east.twcable.com [74.76.243.78]
5 27 ms 22 ms 23 ms rdc-74-76-241-193.alb.northeast.rr.com [74.76.241.193]
6 25 ms 23 ms 23 ms 107.14.19.26
7 60 ms 37 ms 22 ms 66.109.1.36
8 22 ms 21 ms 22 ms ae9.edge3.Newark1.Level3.net [4.68.63.21]
9 32 ms 52 ms 33 ms ae-31-51.ebr1.Newark1.Level3.net [4.69.156.30]
10 33 ms 35 ms 34 ms ae-2-2.ebr1.NewYork1.Level3.net [4.69.132.97]
11 29 ms 28 ms 30 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
12 * * 93 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]
13 30 ms 32 ms 33 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
14 45 ms 44 ms 48 ms 10.2.2.1
15 56 ms 42 ms 44 ms 192.34.76.2
16 43 ms 44 ms 44 ms 199.91.189.234
17 42 ms 43 ms 44 ms 199.91.189.38

Trace complete.

Quote:

---

Originally Posted by Sushi

find the ip of your servers on this website http://www.arrstatus.com/ and ping it , open the command window by type in the search box cmd, and then type: ping xxx.xx.xxx.xx -t (note this is an infinity loop,so stop it manually with ctrl-c)
I think most of you who live in the US don't have latency problem but the package lost problem. check the result of the percentage of the package lost.

---

ARRStatus is not necessarily showing the IP of the cluster your client is connecting to--look at each world and you will see the same IP's listed on different worlds. Likewise, some worlds may use multiple IP's as well. For instance, I am using .74 and .31 when in game (.31 is only in certain situations, but .74 is always listed)--but ARRStatus is listing .28 for Midgard.

If you are on a newer version of Windows, you can run the Resource Monitor (resmon if you want to launch it from Search or Run box), expand the Network and/or TCP sections, and find the FFXIV executable listed with the IP's it is using while you are in game.

If you are on an XP box, open a cmd prompt (Start/Run, type the letters "cmd" in the box and press <enter>), get all the way in game and then alt-tab out to that DOS window you opened up and type the command "netstat" and press the <enter> key. It should print out a list of all recent connections. This command is also available in newer Windows versions, but resmon may be easier for some to use.

Look for IP's starting with 199 and 124. These are the ones your client is actually using--the 199 IP's are in Canada and the 124 IP's are in Japan. NA/EU users will have both showing, but the JP ones are idle for the most part.

It's been about a week now, and I had to leave a winning Titan group for my BLM relic because I started lagging uncontrollably again, starting at around 7pm EST. Already cancelled my recurring subscription, and I will be forced to just stop playing altogether if this continues...

It seems that there have not been any further posts about this concern being an ongoing issue. Because of this, we are considering it to be resolved. If this does continue to be a concern, please create another thread to further discuss resolutions or contact the Support Center at support.na.square-enix.com for assistance.

- Furlamseere