[Dev response requested] Unplayable lag since the hotfixes

I have Time Warner and never had this horrible lag, only in the last week, the game is almost unplayable.

Quote:

---

Originally Posted by Tupsi

It's ok though, it can never be a problem outside of SE, we get that. This reminds me when a large portion of Comcast users couldn't properly stay connected to FFXI for a few weeks yet no one immediately thought it could be SE's ISP, funny how that works.

---

Where did I state this? Tupsi, if you stopped being so defensive and didn't automatically label me as a SE hater/complainer. Maybe you would realize I didn't come into this thread to bash you and/or SE. I provided my findings to help other ppl with the same issue and ISP. Not misdirect them as network issues in general have many variables. Not just SE, the DC's ISP, client's own hardware and ISP, and everything in between as well.

Update from my end. Open world, Mor Dhona, main cities. Zero packet loss now. Latency between 40-60ms now. Before hotfix was 30-40ms. Regardless, no random packet loss resulting in large spikes/pauses. Been in game an hour so far. See what happens prime time.

I too am having these lag issues. I can't do any end game fights due to this massive lag.

I go to speedtest.com to check my internet and it seems on some servers (NYC) I download at 3-6 mbs (suppose to be 50down/25up) and I upload at 30mbs.

I feel there is something very wrong with Verizon, and FFXIV.

Played on Time Warner Durham and Time Warner Wilmington and Time Warner Creedmore all in North Carolina in the last week. No problems at all. Sorry it's happening to you guys.

...and the lagfest is back

Havmt played yet today but last 2 days I had 0sending 2000 plus receiving. At random no matter where I was. AT&T us my isp

Quote:

---

Originally Posted by ReplicaX

Or Ormuco can have equipment issues/upgrades or changes from rerouting that can effect only certain connection types.

---

Oh BTW, where are you seeing Ormuco? I'm showing CogentCo which has a reputation of being the worst upstream provider in existence.

After Midnight EST the servers seem fine... I have to wait to do anything endgame after that time....

Quote:

---

Originally Posted by DSanchez

Oh BTW, where are you seeing Ormuco? I'm showing CogentCo which has a reputation of being the worst upstream provider in existence.

---

They were contracted by Eidos Montreal / SE as their DC solutions provider, however Idk if they provide their upstreaming as well (They do upstreaming). It would really suck if Cogent is infact their upstreamer.

They are on my traces when I hit Montreal, however I'm located in New England and hit all Level3 from New York to Montreal.

Here is their site. I never heard of them until the DC news for NA came out.
http://www.ormuco.com/

im fine no lag here on xfinity

Anybody still getting it?

Quote:

---

Originally Posted by Yugure_Ame

Anybody still getting it?

---

yes... 50ms ping to the server but still experiencing the random screen freezes.

This is the exact same issue I'm getting in WP since the patch, its always at the same locations every time. I have no idea what this Verzion thing is (I dont think I have it anyway) but if its a provider, mine is optus

WP was my favored method of capping myth and as a tank who has yet to get full DL gear I'd really like to see this fixed as I can no longer run WP due to this. No one wants a tank that "stops" right after a pull. I for one refuse to put other players through that.

Note: I should point out I have run a few lower level dungeons since the patch and all seem ok, I've yet to run AK since patch though. I also see no similar symptoms outside of the dungeon.

[EDIT]: Just ran AK a few moments ago, it was horrible, no way in hell I could have been the tank for it. But never have I seen a worse case of freeze-and-fast-forwards kind of lag before. I thought WTFast would fix all these kinds of issues and before the hotfix, it did. To makes things clear, this latest hotfix has made end game (or late game) dungeons and primals out of the question for me.

That means no Phil gear, no Myth gear, no relics and no hope in hell of ever seeing extreme primals.

Please fix this SE, I would love to keep playing :(

I really had bad lag yesterday :(, even in the cities I was getting a lot of lag too. I wonder what happened, maybe the servers just need a reboot.

ive had teh same issues with lag. the teleporting and game frezzes everywhere since 2.1 I do have verizon fios.

These lag issues have been going on since launch. I read on Reddit that some ISPs are treating FFXIV as P2P software and throttling the connection.

As for me I'm on Time Warner in Los Angeles and the lag/rubber banding was so bad that I signed up for battleping. After doing that my lag disappeared.

Sending my packets from Los Angeles to Montreal is like a billion hops. Sqenix needs to stop half assing this and set up a west coast data center.

Same here, my husband and I have Verizon FiOS in the Tampa, FL area, and get screen freeze-and-fast-forwards in all instances, and crafting macros no longer work because of lag, even in remote areas with nobody around. Everything was perfect before the "network maintenance" hotfixes a couple days after the patch, now the trials are pretty much unplayable for us. Dungeons are hit and miss; so far we haven't had lag spikes at crucial moments, but it's only a matter of time.

Lag can happen due to a number of reasons, you should always make sure that the problem isn't your tech or provider first. Lag is caused by (simply put) either a lose of data packages somewhere along the way from point A (you) to point X (destination) or transmission of huge datat packs that take a lot of time to respond back while nothing happens (like when you say "hi" on skype and it takes forever till the other person gets it and you get a response).

To find out if you are losing packages along the way you can try to traceroute them. There are tools for it that you can download for free and there are also websites that let you check your connection. The most common problem causing lag is more often than not that your signal transmitting from A to X goes through stations where it loses data. In that case you have to contact your IP to reroute you. Best example for this is if you're being routed through "atlas.cogentco.com" - just google it and you'll see that every gamer of any mmo had trouble with them and lag before.

You really just have to take a look where you're losing data or where the response (ms) takes significantly longer (if you're from europe you should normally don't get over 80ms per destination in the mid tier, US player should probably stay below 20 per station). Based on that info and a google search you can get an idea who is responsible for your lag, more often than not it is not at the game servers end but somewhere along the way (it can still happen, could also be your router though and whatnot).

PS: I didn't read the whole thread just saw people still complaining on the last page so I hope I didn't just repeat what someone else already told you - but without that info there really is nothing the tech team could possibly do for you, there are too many people with different providers and routes and whatnot, just test it yourself, it's easy.

It's this exactly. Packet loss:

Code:

---

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                  |
|                      Host              -  %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|so-5-0-0-0.NY325-BB-RTR2.verizon-gni.net -    1 | 3780 | 3779 |    5 |    9 |  123 |  58 |
|          0.xe-9-1-0.BR1.NYC1.ALTER.NET -    1 | 3780 | 3779 |    3 |    8 |  90 |    5 |
|          ae11.edge2.NewYork.Level3.net -  34 | 1606 | 1060 |    0 |  31 |  108 |  24 |
|        vlan52.ebr2.NewYork2.Level3.net -    0 | 3783 | 3783 |  23 |  37 |  58 |  39 |
|      ae-46-46.ebr2.NewYork1.Level3.net -    0 | 3784 | 3784 |  24 |  39 |  89 |  35 |
|        ae-5-5.car1.Montreal2.Level3.net -    1 | 3780 | 3779 |  23 |  61 |  436 |  37 |
|      ae-11-11.car2.Montreal2.Level3.net -  23 | 1996 | 1548 |  12 |  43 |  287 |  22 |
|  ORMUCO-COMM.car2.Montreal2.Level3.net -    1 | 3780 | 3779 |  25 |  39 |  64 |  41 |
|                            192.34.76.10 -    1 | 3642 | 3606 |  25 |  41 |  106 |  36 |
|                          199.91.189.242 -    1 | 3650 | 3616 |  30 |  43 |  382 |  42 |
|                          199.91.189.30 -    2 | 3610 | 3566 |  30 |  44 |  82 |  42 |
|________________________________________________|______|______|______|______|______|______|
  WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

---

Level3 needs to get in gear and fix this.

I've called Verizon twice now. I've tried other PC games and they're all running fine.

It would be a miraculous coincidence if ALL Verizon FIOS users suddenly all got lag for the first time since the game came out all on Dec 26 after the Network Maint and all their computers became out of date on the exact same day. SE changed something. They need to figure out how to fix this. No way am I going back to Time Warner Cable and getting throttled to 0.5 MBPS in Prime time, but the game is unplayable with these random freezes.

Quote:

---

Originally Posted by Cupcakehyperion

I've called Verizon twice now. I've tried other PC games and they're all running fine.

It would be a miraculous coincidence if ALL Verizon FIOS users suddenly all got lag for the first time since the game came out all on Dec 26 after the Network Maint and all their computers became out of date on the exact same day. SE changed something. They need to figure out how to fix this. No way am I going back to Time Warner Cable and getting throttled to 0.5 MBPS in Prime time, but the game is unplayable with these random freezes.

---

Wouldn't be the first time I've seen Verizon screw with a game. Not to mention if you look for it, there are several games where this happens with Verizon.

I have Verizon and have been experiencing this problem since 2.1. It got worse after the the 23rd (?).

Add me to the list. Verizon FIOS here and I have wired connection. I highly doubt this issue is on ISP's end because I always get 10 ms ping on speed tests and all my other games run lag free, including different MMO's. Its definitely something caused by this latest update. I either get stupid hiccups or straight up 2-10 sec freezes, which end up in a guaranteed wipe. The fact that I main a healer, yeah the groups don't hesitate to kick you instantly. It's really annoying so SE needs to look into this ASAP.

There are couple ways you can work around it for now.

Quoted from http://forum.square-enix.com/ffxiv/t...onnect../page5

Quote:

---

Originally Posted by Aria_Stars

unfortunately until this is fixed, the best thing I can suggest is to use a proxy tunneling service like Smoothping, WTFast, Battleping, etc (and the many other variants) because it will change the route your internet takes to the FFXIV servers. It's fixed my issues so far.

---

I don't know about the others, but WTFast offers 30 days free trial. So until the issue is fix, you guys should definitely give it a go.

Healing with this lag is a chore, getting out of target zones only to still get hit is bull. Just failed at a Stone Vigil on the last boss because of the lag.

Quote:

---

I highly doubt this issue is on ISP's end because I always get 10 ms ping on speed tests and all my other games run lag free, including different MMO's. Its definitely something caused by this latest update.

---

It's not your ISP directly, it's the route that your data takes to get to the servers and back. i.e. it's a problem between the ISP and SE's servers, not between you and your ISP. Some ISP's use different pipes and routing tables, and from what we're seeing here it seems like Verizon (and my Australian ISP) is routing through addresses that are not in the best of health. Eventually this kind of thing gets sorted out, the routing tables updated, and you get a decent route, the Christmas break is probably slowing that down somewhat.

I do agree that it seems to have been caused by the latest update though, I have never seen anything like this before 2.1. So, something they've done with the configuration of the new datacentres seems to have caused the routes to go bad, either by changing them to different ones or overloading the existing ones with traffic.

Quote:

---

Originally Posted by Luhy

I saw on reddit that this is a thing. I thought I had a night of bad traffic or something.

I have Verizon FIOS and 60 download 15 upload and have never lagged in this game. I'm fine on any sort of test. I can't imagine that this is on my side of things. Freezing for 10 seconds at a time in the middle of Ifrit EX and Twintania is not fair to the rest of my group.

Is this being addressed? Is this known by the devs?

---

Im in the same boat, except mine is 50Mb down/25Mb up on Fios.....and it didnt start till after 2.1 was launched, didnt have the problem prior to 2.1 (other than the normal lag that most almost everyone else had)

Some of you on fios when was the last time you updated your modem from the isp, should get a new one ever year. If leasing it , reading some the speeds not even as good as cable speeds. This comcast speed running faster then your fios http://www.speedtest.net/my-result/3196518540. and game is running amazing now in dungeons. I update my modem ever 2 or one year depends on there updates and sometimes will use the 7 year old router i got range awsome. Comcast just upgraded all there modems for gaming also. my brother gets 1g to 500mb on fios and uploads at 80mb

Quote:

---

Originally Posted by RegnumMagik

There are couple ways you can work around it for now.

Quoted from http://forum.square-enix.com/ffxiv/t...onnect../page5

I don't know about the others, but WTFast offers 30 days free trial. So until the issue is fix, you guys should definitely give it a go.

---

Its worth a try I suppose, I already use WTFast and I still get this problem :(