Help With Connection Issue

[Slipikin]

Hi,

I contacted my Internet provider and they did line tests, said I have zero packet loss, and that my connection speed was fine, but every time I go into instances I get 9000, 10105, and 3102 error messages when disconnected. It has been happening all day and is getting annoying.

A friend said to do a traceroute which I did and these are the results. I don't know what this means or how to proceed so any help would be appreciated.

Thanks!

[Darwyn_Ulondarr]

You're not alone:

http://forum.square-enix.com/ffxiv/t...0-All-Day-Long

Do you live in the south eastern US by any chance?

[Slipikin]

I do. I live in Florida. Thanks for the link. :]

[JillyBean]

Hi Slipikin, what is your ISP and how do you run that trace thingie?

[JillyBean]

Also, are you still having problems?

[kaya_suzumiya]

Hi Slipikin, what is your ISP and how do you run that trace thingie?

u can do it by opening command promt then typing in: tracert ipaddress
just change ipaddress with the server ipadress which u can get from arrstatus website.

another way to do it if u want to see packet loss % is to use a program called winmtr then type in server address and run it will tracert and show u packet loss % on each jump to figure out the problem. test can be done for as long as u want with winmtr if u want to see a better result for tracert


also another thing is its only happening to na/eu servers. it doesnt happen to japan servers by what i noticed so by what i can tell is it might be a routing issue so problem with one of jumps along path from your internet to server. a way to check it is either using winmtr program or do tracert via command prompt

[Slipikin]

I did it using the command prompt and typed in tracert neolobby02.ffxiv.com

I am still having issues. I called Brighthouse who is my ISP about something unrelated to this but got into a conversation with the tech and he is a big WoW player. He asked me to send him my traceroute info and said that there has always been problems stemming from Atlanta after major updates in WoW and he didn't think FFXIV would be in different. I didn't really understand everything he said but he stated that when the server traffic changes drastically like it can after updates, some type of network in Atlanta can view the information as faulty or suspect (not sure how he worded it really) and so it will stop the transmission. He says this shouldn't happen since gaming is the second most important things viewed on the networks.

Anyway, he's putting in a report but says that SE will have to do the same.

Hope this is somehow helpful.

[Evander_Lefoux]

I did it using the command prompt and typed in tracert neolobby02.ffxiv.com

I am still having issues. I called Brighthouse who is my ISP about something unrelated to this but got into a conversation with the tech and he is a big WoW player. He asked me to send him my traceroute info and said that there has always been problems stemming from Atlanta after major updates in WoW and he didn't think FFXIV would be in different. I didn't really understand everything he said but he stated that when the server traffic changes drastically like it can after updates, some type of network in Atlanta can view the information as faulty or suspect (not sure how he worded it really) and so it will stop the transmission. He says this shouldn't happen since gaming is the second most important things viewed on the networks.

Anyway, he's putting in a report but says that SE will have to do the same.

Hope this is somehow helpful.

Actually quite helpful in pinpointing the issue. What he has said corroborates the information I'm gleaning from my own TraceRoutes and PathPings. Everything is stopping dead at the Level3 Atlanta Node.



While the traceroute may manage to make it beyond the Atlanta node intermittently to obtain data from the remaining hops, a PathPing stops completely at the Level3 Atlanta Node with a packet loss ranging from 24% to 89%.

Myself, and others in my region, are having the self-same issues - and it seems to come back to the Level3 Atlanta Node, as that is where we route through the national backbone in the majority of the Southeastern United States.

I hope that this information will further assist the investigation and lead to a resolution, as the game currently remains unplayable for many due to lag, stuttering, freezing, and rampant Error 90000s and Error 2002s.

[Raist]

Level3... repeat offender... WoW and Diablo players of old are no stranger to that company. TATA (as6453) doesn't have the greatest track record either. Cogentco has been cleaning up their act in some areas, but still has pockets around the country that are having issues.

The problem isn't isolated to JUST one point of failure, but collectively it can usually be narrowed down to some specific corridors like Southern California, Seatle, Denver, Austin/Houston/Dallas, Atlanta/Orlando/Jacksonville, Charlotte/Raleigh, DC/Ashburn, Chicago/Milwaulkee, and multiple hubs around Ohio and NY states. There's a lot more in the US, but those are the most common areas that routinely have routing issues in general. Then there's the mess throughout Canada because of the limited backbones.. Vancouver, Winnipeg, Edmonton, Toronto, Nova Scotia, and Montreal itself. Europe hasn't faired too well either... most of the UK in general gets shafted frequently by way of BT and their partners, but it's not uncommon for problems to crop up in the larger hubs like London, Amsterdam/The Hague, Cologne, Frankfurt, Munich, Paris, Zurich to name a few, as well as some of the smaller hubs like Dublin, Glasgow, Luxembourg, Dresden, Stockholm and Oslo among others.

The point is there are systemic problems in the routes being used. Analytics aren't run often enough to keep up with the rapid shifts in usage patterns, and there's been a massive increase over the last year... even in just the last two quarters even. All the advancement in smart devices is leading to everyone dropping their traditional providers and moving to web-based and wireless delivery, and the infrastructure just hasn't been prepared for the increased loads in many countries/states. Why it's important to contact the ISP's on it when we spot problematic routing---point them in the right direction, since they don't seem to be doing too good a job of finding it on their own. Japan has been dealing with such changes much longer than the rest of us, and they are much better equipped for it in general--could be part of the problem... SE is based in Tokyo after all.

There is a light at the end of the tunnel though... the larger companies are trying to roll out more fiber and such to increase capacities in more markets, which should eventually lead to better routes once the segments are established and made available to the exchanges. Atlanta and Charlotte have recently gotten new fiber, and a handful of markets in NC are trying to get approvals from local boards right now. LA and NY, and parts of Texas currently have expansion going on as well (not just the Google Fiber in that area, but other companies like AT&T and such are trying to roll out new lines as well).

Just wish things could move a little faster..... but progress is being made.