Quote Originally Posted by Slipikin View Post
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.