HUGE CONNECTION PROBLEM

[Raist]

Denial of Service attacks have gotten considerably more complex over the years. These Distributed Denial of Service are particularly difficult because they are distributed across multiple points of origin. You literally could be getting attacked from hundreds/thousands of different cities from anywhere around the globe. Some of the fast and dirty countermeasures can't be put in place because it would break the game clients.

They're making progress though... some nodes have been cleared and it is allowing some players in unfetterred now. It's just going to take time to flush things out and clear all the nodes so that everyone can gain access again.

As for compensation... may not be happening. You aren't paying specifically for game time. You are effectively paying to keep your login active for x number of days so you may access all game related content (Lodestone Data and such... not JUST playing the game) that would otherwise be denied with an inactive login (barring uncontrollable events like natural disasters or internet outages). In other words, you aren't getting 43,000 minutes of FFXIV playtime dumped into an account like when adding minutes to a phone. It's more like keeping your phone service active for 30 more days so that you can use it when every you need to within those 30 days---but if you are in an area that has no coverage for whatever reason, the phone company is under no obligation to give you additional time. Not the best analogy, just one off the top of my head that many may relate to better.

[Riguel]

Getting 90k and 2002 on Levithan can't even log in!

[Whovian]

And now up to https errors before I even get to log in (as the launcher loads).

Wooo!

[Detoxy]

I am kind of relieved to see this isn't an isolated incident. PS4 player here, and I've been encountering these issues too- though my connection is stable. Tried to run a couple of DF instances and it was very hard to even clear let alone complete due to the lag spikes causing spells/skills to not register, or error 9000. Quite frustrating, sometimes causing me to be booted out of the dungeon due to a followup error 2002. Hopefully they will address these issues in the next maintenance.

PS4 player here to and the lag spikes on my end are bad. I have a feeling it may be do to PSN having issues and what not lately (past week for me). I just got a new router from TWC today just to be on the safe side and it im still getting lag spikes/ packet loss. I guess next step would be to get my lines tested in my APT if its not a issue on Sonys end (wich I think it is).

[Tyverus]

I have a similar issue. Not getting a 90k error code but randomly disconnecting from the game. This seems to occur randomly; I can get disconnected while running around in Ishgard or any other area or I get disconnected in dungeons - both old and new. I'm not sure how to fix this as I'm not seeing an actual error code.

EDIT: Playing on PC port, haven't tried PS4 port.

[reefer69]

last few weeks the lag has been ridiculous i often do pvp and part of the day its fine. as soon as its evening and esp around 11pm i cannot play properly as i get 90k every 5 mins.

today i started to 90k during the day to make matters worse. tested my cables bought a new router and called my isp for a booost. everything is brand new and upgraded yet i cannot enjoy my game..

hope se fixes this shit soon.

[Raist]

last few weeks the lag has been ridiculous i often do pvp and part of the day its fine. as soon as its evening and esp around 11pm i cannot play properly as i get 90k every 5 mins.

today i started to 90k during the day to make matters worse. tested my cables bought a new router and called my isp for a booost. everything is brand new and upgraded yet i cannot enjoy my game..

hope se fixes this shit soon.

It's likely not a local issue, but upstream. Most often we see the signs of congestion around the exchange points with the third/fourth party peering along the route to Ormuco (SE's ISP). Need a proper analysis of the route done to rule out known potential routing issues like these. It is something your ISP's Tier3 team should have the resources to sort out for you.

[Lexie]

last two days have been running into this with a raid team to lead, when I connect cannot stay connected for long traceroute looks fine, contacted internet company and speedtested the net coming in at 4M up and 60M down, new router, cables, hardwired in, I can stream with great quality when I can stay in the game but havent even tried for 2 weeks now due to the disconnects.

let me clairfy something the 90ks have been over the past two weeks but consistently getting worse, the 2002s have been just over the past two days

[Raist]

Charter was getting a lot of reports of issues in St. Louis the other day...may be more of the same.

Those "speed tests" are actually bandwidth tests...anything beyond about 5mb of bandwidth can be overkill for this game. That is usually the minimum bursting rate on the modems...and the game barely requires 1mbit of bandwidth for typical game play. Watch your S/R numbers while playing---that is how many bytes you are sending and receiving (multiply by 8 to get he bit rate). Alternatively you could monitor through your router tools or even resource monitor. You will typically only see it spike really high during things like initial zone loads or where there are tons of active players to process.

As for your traces...just out of curiosity, are you using the IP your client uses or one of the neolobby addresses? I only ask because I see a lot of people testing g addresses not even related to the game. And did you see any * events or more than about a 15% deviation in response times between the pings? Under proper conditions they should be consistently tight--too much jitter can indicate potential congestion issues. This game depends on consistent, timely, and orderly delivery of packets. Any delays causing high retransmission causes problems.

[Lexie]

yup that would probably be it near stl charter hub and charter is only cable provider here,
tracerouting the ip my client uses only 5 ms difference in response times, no * events