Screw it, im done. This lag is no longer acceptable.

[Vezzian]

you could also just bring up the command line on your Windows PC and type the following:

ping www.google.com -l 1024 -t

This will ping Google's server with 1024 bytes of data continuously every second for as long as you need.
The -l 1024 switch add a load to the request and the -t switch just forces the ping request to continue indefinitely or until you cancel it.

Run it for a while and see if you are getting any packet loss.

[Stryker]

snip

Actually you were the one that threw out the disclaimer about your profession and your time spent as a gamer in an attempt to add weight to your opening post. That's fine, many people do it. I was just giving you the common courtesy to tell you that it's a pointless thing to do on the internet. Apparently you found it offensive.

Also you never stated that you had used pingtest you just claimed that it couldn't be your ISP. I was just merely trying to cover all the bases, so to say that my post adds nothing to the discussion is a bit silly.

But since you've done everything you can and still experience lag all I can say is that sucks, hopefully you can get it fixed if not I bid you adieu.

[Istym]

deleted

/10 chars

[KujinRen]

Let me better explain what I mean by strobe light. Players will be moving then everything stops.. Just stops. Then everything super speeds up to catch up with what really happened. Sometimes the pause is a second, some times its 10 seconds. If it was a FPS issue this would happen 24 hours a day. But it doesn't. It happens between the same time frame every single day, and clears up towards the evening. Pretty sure the problem isn't my video card only working half of the day each day.

This is spot on!!

From closed beta 1 all the way up until 3 weeks after launch, I didn't experience any of these issues. It was after a certain maintenance that I started to experience the "freeze and speed up" lag. I also notice that it seems more common on Mondays and Tuesdays (which are the two busiest days after a weekly reset) where everyone is trying to queue up for AK to farm Mythology tomes or people starting a fresh CoB run.

[ntall1]

Actually you were the one that threw out the disclaimer about your profession and your time spent as a gamer in an attempt to add weight to your opening post. That's fine, many people do it. I was just giving you the common courtesy to tell you that it's a pointless thing to do on the internet. Apparently you found it offensive.

Also you never stated that you had used pingtest you just claimed that it couldn't be your ISP. I was just merely trying to cover all the bases, so to say that my post adds nothing to the discussion is a bit silly.

But since you've done everything you can and still experience lag all I can say is that sucks, hopefully you can get it fixed if not I bid you adieu.

I did not take offense, and did not mean to be offensive. I apologize if it came off that way.

[avaughnimous]

I've found that any time someone says the words "Gaming Rig", they don't have a decent PC.

That's probably not true. But hey, you eeked out a couple of likes saying something snarky and useless. Good job, bro!

[teoulas]

In my server today we were in a 8 man group doing fates in Northern Thanalan and 2 of the party members were experiencing unreal lagspikes. On my screen fate was over teammate was dead and he was telling us from TS that he is still alive and doing the fate. The lag wasnt seconds but mins. After 2-3 mins he died on his screen. The other one had the same problem and they werent playing from same connection or area. While he was dead on my screen I could see his corpse moving lol. We had such a good laugh! Make more games like this pls. Oh and ppl saying that the game hasnt a lag problem: Have u browsing this forum lately? Its full of lag posts that unfortunately disappear strangely.

[Marishi-Ten]

Sorry to hear you are having issues with lag. I play mostly evenings, and while I get a bit of lag here and there it's nothing like you are complaining about (unless trying to do Odin or something where there are massive numbers of players all in one area).

I too am a network admin and I'm not convinced it's an issue with the servers at all.

They have bought some really high end hardware!

I believe the issue is with the internet backbone the datacenter/s are connected to.

I believe the infrastructure of these datacenters, specifically the fiber optic trunk line is not sufficient enough to carry the traffic and is causing these lag spikes at certain times of the day.

I know this doesn't help you.....

I agree. I personally make my living as a Systems Admin for a mid size company monitoring and regulating servers. The packet loss and high latency times points towards the backbones ports being overloaded by so much traffic it drops the connection and throws the dreaded MD5 flag. When all of the data is reaffirmed and the client can confirm all data sent with the host the speed up of everything on your screen is seen. The client has to resend it's packets to the host, the host has to confirm packets, the host sends packets to the client where the client has to confirm delivery at the same time maintaining the synchronization of host and client time.

Some hops are worse than others and it seems that Square knows this and tries to re route some clients away from latency ridden datacenters. It's a delicate balance though. You re route too much, you are in the same place you were. You don't re route and the problem persists. You also have to field these concerns with the fiber provider and backbones where they have to investigate the issue, confirm it, and either upgrade the hardware (yeah right), re distribute port assignments, or re route traffic (yeah right).

I don't know what kind of hardware they have, but if I were the Sr Systems Admin at the Montreal offices, I wouldn't want to spend anything as I already have racks available to me. I would only upgrade if I was told to and even then, I have to send in the price quote, get approval from corporate, contact the distributor, order the parts, wait for them to arrive, receive the parts, schedule a time for the change out (confirming with corporate and waiting for the head honchos to give me the dates), get the techs to perform the change out, QA the hardware, network the new hardware with the old and intermesh, load the software, QA The software, and finally boot the system up again.

This process can take weeks depending on man power, stock, and backordering processes.

It is possible that by adding more racks they can change the route paths and ease up on the overloading, but this is only treating the symptom, not curing the disease. The main problem is their backbone not having enough bandwidth to funnel all the users connecting efficiently and without packet loss.

[Marishi-Ten]

Actually you were the one that threw out the disclaimer about your profession and your time spent as a gamer in an attempt to add weight to your opening post. That's fine, many people do it. I was just giving you the common courtesy to tell you that it's a pointless thing to do on the internet. Apparently you found it offensive.

Also you never stated that you had used pingtest you just claimed that it couldn't be your ISP. I was just merely trying to cover all the bases, so to say that my post adds nothing to the discussion is a bit silly.

But since you've done everything you can and still experience lag all I can say is that sucks, hopefully you can get it fixed if not I bid you adieu.

There isn't a need to check that site when you can run a trace route to the end point IP to find where the bottleneck occurs (not on the local ISP side):

4 boid-agw1.inet.qwest.net (184.99.65.65) 20.875 ms 18.362 ms 27.125 ms
5 sea-brdr-02.inet.qwest.net (67.14.41.18) 31.322 ms 44.643 ms 55.797 ms
6 ix-1-0-0-0.tcore1.00s-seattle.as6453.net (64.86.123.77) 31.431 ms 30.914 ms 31.687 ms
7 if-11-0-0-5.core1.00s-seattle.as6453.net (64.86.124.25) 192.185 ms
if-13-0-0-4.core1.00s-seattle.as6453.net (64.86.124.13) 315.271 ms 54.614 ms
8 if-4-1-0-0.tcore2.ct8-chicago.as6453.net (64.86.124.10) 104.565 ms 96.403 ms 95.589 ms
9 if-3-2.tcore1.w6c-montreal.as6453.net (66.198.96.45)
106.126 ms 157.243 ms 97.227 ms
10 66.198.96.50 (66.198.96.50) 99.638 ms 99.754 ms 101.073 ms
11 192.34.76.2 (192.34.76.2) 102.590 ms 103.997 ms 100.751 ms

4 boid-agw1.inet.qwest.net (184.99.65.65) 20.875 ms 18.362 ms 27.125 ms
5 sea-brdr-02.inet.qwest.net (67.14.41.18) 31.322 ms 44.643 ms 55.797 ms
6 ix-1-0-0-0.tcore1.00s-seattle.as6453.net (64.86.123.77) 31.431 ms 30.914 ms 31.687 ms
7 if-11-0-0-5.core1.00s-seattle.as6453.net (64.86.124.25) 192.185 ms
if-13-0-0-4.core1.00s-seattle.as6453.net (64.86.124.13) 315.271 ms 54.614 ms
8 if-4-1-0-0.tcore2.ct8-chicago.as6453.net (64.86.124.10) 104.565 ms 96.403 ms 95.589 ms
9 if-3-2.tcore1.w6c-montreal.as6453.net (66.198.96.45) 106.126 ms 157.243 ms 97.227 ms
10 66.198.96.50 (66.198.96.50) 99.638 ms 99.754 ms 101.073 ms
11 192.34.76.2 (192.34.76.2) 102.590 ms 103.997 ms 100.751 ms

sudo ping neolobby02.ffxiv.com
PING neolobby02.ffxiv.com (199.91.189.74): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 199.91.189.74: icmp_seq=1 ttl=54 time=537.147 ms
64 bytes from 199.91.189.74: icmp_seq=2 ttl=54 time=458.225 ms
64 bytes from 199.91.189.74: icmp_seq=3 ttl=54 time=379.185 ms
64 bytes from 199.91.189.74: icmp_seq=4 ttl=54 time=386.048 ms
64 bytes from 199.91.189.74: icmp_seq=5 ttl=54 time=169.980 ms
64 bytes from 199.91.189.74: icmp_seq=6 ttl=54 time=134.348 ms
64 bytes from 199.91.189.74: icmp_seq=7 ttl=54 time=115.387 ms
64 bytes from 199.91.189.74: icmp_seq=8 ttl=54 time=108.769 ms
64 bytes from 199.91.189.74: icmp_seq=9 ttl=54 time=104.653 ms
64 bytes from 199.91.189.74: icmp_seq=10 ttl=54

[Sphinxy]

The lag is getting bad in primetime.

Comcast. Illinois on goblin server.

Everything else works perfect except this game.