Unplayable Lag

[Tupsi]

And don't you dare complain when you have to pay for a VPN sub to play this MMO when you'll never have to do it for any other.

VPNs only "directs" your connection better, SE doesn't run your ISP or control how they do their hops - so if a VPN fixes your issue, that means you need to talk with your ISP to see what's going on inbetween you/them and SE's datacenter.

Fyi, while being sarcastic you forget to mention that lots of people actually have to use VPNs to access certain online games due to region lockouts.

[Ashira]

Non of my Free Company have been getting these issues, yet non of them are on my ISP (Sky) which also use BT lines.

I've never had these issues before, they started three days ago.

I come to the forums and for the past three days people on my ISP have been having the exact same problems. Wait a minute..

[Ecks007]

No lag for me.

[darzok]

I got this problem its stopping me been able to play my tank at all since it would be unable to tank all i can do now is suffer as a dps since i can still run ct laggy as a smn.

[TeaTimeBear]

Hi everyone,

This issue seems to affect people in a broad scope. No matter what kinda hardware you run the game on, if there is a problem with how you are being routed to their servers in Canada you will see this occure. I have been extensively digging up reports about the issue. Before it grew so wide spread many people with BT were posting in the rubberbanding thread on the tech forum. I cannot say when it began for them but for me it began before the update came to pass. A week before December 23rd I began to see my first symptom of rubberbanding. At the time I didn't know what it was so I decided to change my internet from Comcast to Verizon hoping it would do something.

It didn't, even with FIOS I still had the same problem, and that's when I began to dig. I wanted to find others like me, affected by whatever this is. I've read pretty much everything there is on the beast called the internet, reports in general on the OF, reports on Tech on the OF and reports from FC mates, even reddit. I came to the conclusion that...

BT
Sky
Comcast
Verizon
Timewarner
and even services in Japan are all affected (maybe more than listed even..)

After digging through many answers for PC fixes, I decided to find my own fix for PS3. The only thing I could do was was not connect through that level 3 route. I had to extensively dig in order to find a IP that didn't go there. There is a 170 page post on our tech forums with only 1 reply from the higher ups and that is the OP. This is a serious problem, and if what a poster here said is true that they fixed this for the Japanese relatively quickly than that is extremely disheartening as neither SE nor ISP know the how, what, and why this is occurring. I do not feel we as paying customers should have to put on our tech hats and fix things with our limited resources..

*interesting to note, a friend of mine who has Verizon as well reported no rubberbanding. Not just him but others with Comcast ect.. All that makes me think is it affects some and not others but I'm not tech savy enough to say.

[Kal-El]

I do not feel we as paying customers should have to put on our tech hats and fix things with our limited resources..

This x 100.

Paying SE and ISP and yet they just seem to blame each other. Can't even do Copperbell HM without dying dread to see what coil will be like on Monday :/

[MageBlack]

Has everyone been submitting a Bug Report? If you are having issues, this is the best place to post it and best way to get results. Its also the best way for SE to identify the issues and hopefully correct the problem. Its nice to see people gathering together and seeing how wide spread the issue is through General Discussions but I hope to see the OP put a link to the bug report in the OP. Complaining on the GD will only get you so far.

Best of luck and I hope things get fixed sooner rather than later!

Without following proper procedures for bug reports, complaints like this on GD is a lot like driving your car to the mechanics and saying "Fix it! Its broken" dropping your keys and walking out.

[Kal-El]

quote

I've been in touch with SE and they said "It's probably the ISP not prioritising traffic from FFXIV. We will escalate the issue to be looked into and you can post about the issue on the forums at http://forum.square-enix.com"

Yet my ISP says it's not them it's SE.

[MageBlack]

I've been in touch with SE and they said "It's probably the ISP not prioritising traffic from FFXIV. We will escalate the issue to be looked into and you can post about the issue on the forums at http://forum.square-enix.com"

Yet my ISP says it's not them it's SE.

Were you able to provide the following information to the tech you contacted?

Connection Specs
- Type of internet connection/provider:
- Modem maker/model number:

PC Specs
-=-=-=-=- System Information -=-=-=-=-

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Laptop Model Name:
Laptop Model Number:

This is just a snippet of the requirements for a bug report. i picked this part because I feel its the most important part with as many computer builds and specs as there are computers out there. Its vital for identifying the source of the problem to know what specs you are using.

I don't doubt there are people having issues, My brother is one of them, He lives a few blocks away, uses the same ISP as me, has a newer rig than I do yet I have no issues at all.

Also its important to test again after each patch the do and submit another report if you are experiencing the same issues or new ones. Sometimes their patches can break things and they need to know.

Again, good luck, I remember seeing the OP with complaints before the 2.1 patch. Sorry about your luck.

[Akira_Tenshi]

Non of my Free Company have been getting these issues, yet non of them are on my ISP (Sky) which also use BT lines.

I've never had these issues before, they started three days ago.

I come to the forums and for the past three days people on my ISP have been having the exact same problems. Wait a minute..

I'm with Sky to and the issue started roughly 3 days ago.