Quote Originally Posted by Marishi-Ten View Post
Verizon, though meaning well, is inaccurate in stating the issue is with the Game Provider. Looking over your parsing data, I see that you have low ping times. I don't see a whole lot of fluctuation. What I do see is the glaring time out requests. Your connection to the server port (Tata) is either congested or is dropping due to load. Yours is an excellent example of how the server you're connecting to behaves when congested or not specd to handle the amount of volume it's seeing.

Your issue unfortunately cannot be corrected by any via client side means. This is an issue with the actual server load and shows that the racks are congested and cannot negotiate with the amount of users it sees at this time. Until the server provider expands the servers (partition/addition) and redistributes the port assignments, the issue will persist.

Apologies for the long post!
Quote Originally Posted by Marishi-Ten View Post

Verizon, though meaning well, is inaccurate in stating the issue is with the Game Provider. Looking over your parsing data, I see that you have low ping times. I don't see a whole lot of fluctuation. What I do see is the glaring time out requests. Your connection to the server port (Tata) is either congested or is dropping due to load. Yours is an excellent example of how the server you're connecting to behaves when congested or not specd to handle the amount of volume it's seeing.

Your issue unfortunately cannot be corrected by any via client side means. This is an issue with the actual server load and shows that the racks are congested and cannot negotiate with the amount of users it sees at this time. Until the server provider expands the servers (partition/addition) and redistributes the port assignments, the issue will persist.

Apologies for the long post!
Thanks for recognizing what I was actually trying to communicate. The issue isn't with Square-Enix at all, it's with an ISP someplace inbetween us and them. I dealt with this kind of crap in Iraq for a year, it's a bad cable or a overloaded device someplace no one really pays attention that has any interest in the game.

I haven't been able to isolate it, but from what I can tell, BOTH of these hops have issues. Both are TINET.net.

I've seen multiple other posts where people blame the ormuco-gw server IP, which is the same one I mention. They ARE NOT in Northern Virginia.

Logic would tell me that the tinet.net run systems are the problem.

I've had the same packet loss to both of these hops...

8 41 ms 39 ms 37 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 41 ms 37 ms 40 ms ormuco-gw.ip4.tinet.net [216.221.156.110]