HUGE CONNECTION PROBLEM

[Raist]

Yep.

Tracing route to 184.107.107.176 over a maximum of 30 hops

As detailed earlier in the thread, that IP is NOT tied into the game. Need to be using the IP your client actually uses (or at least your actual lobby server) so that you are hitting a route to Ormuco (SE's ISP) and then a server actually used by the game. The Canadian IP's start with 199, and most of the Japan ones will start with 124.

TATA started having issues last night as well as the ongoing problems with Level3. TWC switched me back to Cogent lines via Atlanta, and my connection is once again stable.

Hate to keep beating the dead horse.... but once again proof that there IS something your ISP in fact can do about the issue when it is found to be in route to Ormuco.

[wasago]

after lastest patch i geting 90k error im on ps4 server ragnarog

[Runsell]

I am having Losses from ORUMCO Routers heading to SE Servers. No local problems from my ISP I had run lot of ping tests and traceroutes with no issues until I do it to SE Servers I see packet drops and latency when reaching ORUMCO.

[Askaniz]

I'm getting DC every 5 minutes since yesterday's night. 90k errors all the way.

[Jeza]

I am a member of one of the largest and most active FC's on Coeurl server, at least a quarter of our membership are having issues with lag and inability to log in to the game because of 2002 errors in the lobby and 90k disconnects in game. Lag is causing havoc with raids and events not to mention lower levels trying to run dungeons and do quests/leves ect.

That's alot of people from all over the world to suddenly, out of nowhere, have the exact same problem at the exact same time. There IS a problem and it is NOT user side. Our FC isn't the only one having this problem, we have been hearing about the exact same difficulty happening to FC's and players server wide.

FIX IT.

[Raist]

There IS a problem and it is NOT user side.

Exactly the point that has been made over and over in various threads on this issue. It is typically not a local problem, so when you call in and talk to the tier1/tier2 guys (that handle localized issues), they find nothing. The problem is typically upstream, between you and SE's ISP. As I tried to outline in another thread (complete with maps from the Tier1 ISP's mind you, this isn't speculation here), there are a limited number of pathways into Canada that we ALL have to use. It's like 8 from the US side, and one or two that come directly from from the UK into Canada. Everyone else around the world gets routed through the US, mostly through Southern California or the North East, then up through these limited paths into Canada. Note that all these routes are not used globally across all ISP's. There are a few Tier1 ISP's, each one controls a few of these routes. So from the US, you may have 3 optional ISP's as a routing partner, each one with only 2 or 3 routes into Montreal). If your route is bad, your ISP can either contact that partner for assistance or switch you to another partner.

For instance, there is a MAJOR trunk that runs from Tokyo to LA. If Cogent subscribers in North America want to get to/from Tokyo (as In SE Japan), they are likely to be sent through LA to get there. If there are issues with the lines in the LA area, it can dramatically impact ALL Cogent users in NA trying to communicate with Tokyo. Note that Cogent is a Tier1 ISP who YOUR ISP has peering agreements for connecting you to Tokyo--AT&T, TWC, Verizon, etc. typically do NOT run you everywhere on their network alone, but often use a third party to get you to someone else's network. Likewise, congestion can build up really quick around all the centralized exchange points like LA/San Jose, Boston, Chicago (hello, NSA scan we all go through), New York, Nova Scotia, Vancouver, Toronto, and Montreal--that's just a handful of the common choke points, there are others but the names escape me.

So, basically, when it goes bad for one of the big 3 peering/transit providers, it can impact entire REGIONS at once. This is why when you look at the maps for various services at the downdetector.com site, you will see problems pop up consistently in the same regions, even though you are dealing with different last mile ISP's like AT&T, Comcast, TWC, Verizon, etc. The "middleman" networks that provide the peering/transit to other people's networks are having issues along specific ports/routes and affect a widespread number of users all at once.

Think of it like the PS3/PS4 issues with PSN--when it has issues (or Sony takes it down for maintenance), the consoles have access issues because this game relies on PSN for access. Likewise, if the Cogent/PsiNet peer exchanges are having issues getting people through to Ormuco's VLAN, then EVERYONE assigned to that route has issues, but those that are using TATA may not because they aren't having congestion issues at that time.

This is why it is so important that you make sure you are dealing with at least Tier3 support when addressing the matter with your ISP. They are the ones that can provide escalation to conduct a proper investigation and contact the people that can adjust your route. It's not the guys at your nearby office that can swap modems/cables/connectors/traps/splitters.... this is a much higher tier of the network that needs to be addressed higher up the chain, typically in another city or state.

[Jeza]

How very unfortunate for FFXIV:ARR to be connected to so many unreliable ISPs that keep their players (from all over the world, east and west coast US and all over the map betwixt the two, Canada, England, Japan, Malaysia, Kuwait and all points in between) who play the game on consoles and computers, through Steam and not, from connecting to the game at the SAME TIME...

Gosh, what horrible, completely coincidental, luck for such a large company! They must just be heartbroken for all those poor customers that just happen to be connected to them through such a shoddy system.

Maybe they should contact other game companies who aren't having such a large scale and widespread issue and see if they can't find out why their games are fine but sadly it seems the interwebs doesn't want FFXIV customers to play their game anymore?

Poor SQ-ENIX, all those ISP's ruining their player's ability to play their game...maybe its a conspiracy! And here I am, all out of tinfoil to make a protective hat....

FIX IT!

[neko5490]

Been having 90k since patch, every 15 min or so. Really annoying... On PS4 if it matters, Comcast, Florida here.

[Raist]

Been having 90k since patch, every 15 min or so. Really annoying... On PS4 if it matters, Comcast, Florida here.

Sony has been having issues with PS4 and PSN since the console launched, was especially bad last week with the DDoS attacks also. Their still having issues... not sure if it's the same attacks or the usual stuff. Their map at downdetector doesn't look too good at the moment for Europe... also still showing the normal issues along the US coasts. This image will update periodically, so it may look better or worse when you come back later:



http://downdetector.com/status/playstation-network

With how much the PS4 version depends on PSN, this could be a factor at play, regardless if Comcast has gotten it's act together or not... but both Comcast and TWC have been having their share of issues across the Southeast and other regions as well (the pending merger under review doesn't sound good for us either). Again, this map will update and may show different regions with issues later, at present Florida has light congestion, but there is a band of issues cutting across the Southeast that could be at play:



http://downdetector.com/status/comcast-xfinity

Sorry I didn't get into this earlier... duties started queuing up steadily again and I wanted to be able to load these maps for demonstration. But, yeah... the PS4 crowd has been having it rough for a while now because of Sony's issues with their network that are compounding matters even further. Might still be worth getting your routes looked at though... if you don't use the PC also, you wont have a solid picture of your specific server unless you can capture the IP the PS4 uses through your router's admin. You can forward the lobby server addresses to your ISP's Tier3 folks for testing though. They run from neolobby01.ffxiv.com through to neolobby06.ffxiv.com. The odd numbered names are for Japan, the even ones are for Canada.

[kram]

Bump! again and again!
Still getting 90k errors and lobby errors.

Oh well, what's new? These problems existed several months ago (as per other threads in this forum), and we are the fortunate players to receive this misery.