http://forum.square-enix.com/ffxiv/threads/74559-Request-for-information-ISPs-and-P2P-throttling
http://forum.square-enix.com/ffxiv/threads/88216-URGENT-ISSUE-All-Verizon-ISP-users-in-Virginia-experiencing-CONSTANT-MAJOR-LAG
https://pay.reddit.com/r/ffxiv/comments/1l9v4e/i_think_verizon_is_throttling_ff14_just_like_that/
http://www.reddit.com/r/ffxiv/comments/1m16es/verizon_isp_users_are_you_lagging/
Ever since September 3rd or 4th, whenever Square Enix took down their own servers for maintenance, there has been excruciating lag throughout the game. It is described as a constant 3-5 second delay causing rubberbands and basically hindering the game unplayable. Other ISP users in my area, such as Cox Communications are not experiencing these problems. There has been multiple posts about this on various websites. I wanted to bring it to the Verizon website to possibly gain some attention. Overall I am very happy with Verizon FiOS. Please help.
Here is some supporting date for this users complaint. I too am having the issue and spent a half hour or more with online tech support today with no comments other than "run this speed test" and "reboot your router".
The problem is obviously not directly on verizon's hardware, but it is someplace in between the Square-Enix servers and the Northern Va route to them.
There are probably 50-100 users alone actively complaining on the Square-Enix forums about issue in the northern va area with FiOS and this game, I'm going to assume the previous users posts highlight them.
The issue is now also coming up on reddit, not just NoVA users. However, the commonality are the TINET.NET routers on hops 8 and 9 in my example.
Verizon, please do anything you can to help resolve. The game provider is so overwhelmed with game launch issues, we're not getting much assistance otherwise.
LOVE my Verizon speed going everywhere else, just not to my FFXIV server... 😞
3 28 ms 14 ms 10 ms G0-9-2-6.WASHDC-LCR-21.verizon-gni.net [130.81.97.106]4 9 ms 8 ms 8 ms ae1-0.RES-BB-RTR1.verizon-gni.net [130.81.209.206]5 11 ms 12 ms 11 ms 0.ae5.XL1.IAD8.ALTER.NET [152.63.8.121]6 9 ms 8 ms 8 ms 0.xe-10-0-1.GW9.IAD8.ALTER.NET [152.63.33.161]7 * 14 ms 14 ms tinet-gw.customer.alter.net [152.179.50.30]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]10 47 ms 41 ms * 192.34.76.211 47 ms 41 ms 42 ms 199.91.189.23412 37 ms 39 ms 38 ms 199.91.189.74Reply from 216.221.156.110: bytes=64 time=39ms TTL=250Reply from 216.221.156.110: bytes=64 time=37ms TTL=250Request timed out.Request timed out.Reply from 216.221.156.110: bytes=64 time=40ms TTL=250Reply from 216.221.156.110: bytes=64 time=34ms TTL=250Reply from 216.221.156.110: bytes=64 time=33ms TTL=250Reply from 216.221.156.110: bytes=64 time=38ms TTL=250Reply from 216.221.156.110: bytes=64 time=32ms TTL=250Request timed out.Reply from 216.221.156.110: bytes=64 time=38ms TTL=250Request timed out.Reply from 216.221.156.110: bytes=64 time=38ms TTL=250Reply from 216.221.156.110: bytes=64 time=38ms TTL=250Reply from 216.221.156.110: bytes=64 time=39ms TTL=250Reply from 216.221.156.110: bytes=64 time=35ms TTL=250Request timed out.Reply from 216.221.156.110: bytes=64 time=38ms TTL=250Reply from 216.221.156.110: bytes=64 time=42ms TTL=250
same issue here
Experiencing the same issues as well since 9/4/13, before that it worked fine.
Started getting this issue Sept. 5 after the maintenance. Never had this issue prior to the maintenance. I'm getting lag spikes that last anywhere from 1-5secs every 5-10 secs. Speedtest, streaming, other applications/games work flawlessly, only seeing this issue pop up in FFXIV. They did maintenance last night that MAY have solved the issue, I haven't checked yet. Can anyone confirm that this is still going on, post-maintenance?
Either way, here is a tracert for the sever (Behemoth) that I play on.
Tracing route to 199.91.189.20 over a maximum of 30 hops
1 3 ms 1 ms 1 ms Wireless_Broadband_Router.home [192.168.1.1]2 10 ms 9 ms 10 ms L100.WASHDC-VFTTP-73.verizon-gni.net [72.83.250.1]3 18 ms 10 ms 19 ms G0-6-4-6.WASHDC-LCR-22.verizon-gni.net [130.81.212.144]4 16 ms 8 ms 9 ms so-14-0-0-0.RES-BB-RTR1.verizon-gni.net [130.81.22.56]5 12 ms 8 ms 9 ms 0.ae4.XL2.IAD8.ALTER.NET [152.63.8.125]6 10 ms 8 ms 9 ms 0.xe-11-2-1.GW9.IAD8.ALTER.NET [152.63.42.2]7 11 ms 17 ms 9 ms tinet-gw.customer.alter.net [152.179.50.30]8 29 ms 29 ms 28 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]9 30 ms 29 ms 28 ms ormuco-gw.ip4.tinet.net [216.221.156.110]10 28 ms 28 ms 28 ms 192.34.76.211 32 ms 36 ms 38 ms 199.91.189.23412 27 ms 38 ms 122 ms 199.91.189.20
Trace complete.
Bumping this thread for any Admin replies.
Thank you.
Yup, still there post-maintenance. Tried to ping the server:
Pinging 199.91.189.20 with 32 bytes of data:Reply from 199.91.189.20: bytes=32 time=33ms TTL=250Reply from 199.91.189.20: bytes=32 time=43ms TTL=250Reply from 199.91.189.20: bytes=32 time=38ms TTL=250Request timed out.Request timed out.Reply from 199.91.189.20: bytes=32 time=46ms TTL=250Reply from 199.91.189.20: bytes=32 time=37ms TTL=250Reply from 199.91.189.20: bytes=32 time=40ms TTL=250Reply from 199.91.189.20: bytes=32 time=38ms TTL=250Request timed out.Reply from 199.91.189.20: bytes=32 time=35ms TTL=250Reply from 199.91.189.20: bytes=32 time=37ms TTL=250Request timed out.Reply from 199.91.189.20: bytes=32 time=45ms TTL=250Reply from 199.91.189.20: bytes=32 time=38ms TTL=250Reply from 199.91.189.20: bytes=32 time=35ms TTL=250Request timed out.Reply from 199.91.189.20: bytes=32 time=37ms TTL=250Reply from 199.91.189.20: bytes=32 time=42ms TTL=250Reply from 199.91.189.20: bytes=32 time=39ms TTL=250
Ping statistics for 199.91.189.20:Packets: Sent = 20, Received = 15, Lost = 5 (25% loss),Approximate round trip times in milli-seconds:Minimum = 33ms, Maximum = 46ms, Average = 38ms
I just spent 30 minutes on the phone with a tinet.net NOC technician. The short answer:5-10% packet loss @ ormuco-gw.ip4.tinet.net [216.221.156.110]This IP is being advertised to multiple circuits (3 maybe?). The tinet.net is running fine. The NOC tech has confidence one of the others was fine too, and pointed me to the NOC for Cogent Communications, cogentco.com.I just sent them an email, hoping to get the same outstanding service Tinet.net provided.
Please forward any information to me if they email you back.
{edited for privacy}
I'm actually in Chesapeake, Virginia, but Virginia nonetheless.
Continuing to have issues as well.
WinMTR Statistics
Lag continues. Below is the trace route taken around 6:50pm EDT on 10/11/2013.
Still having ALTER.NET issues...
Other players have posted traceroutes showing their traffic meeting up on tinet.net before reaching SE's network. C'mon Verizon, fix your stuff!
I'm having the same problom & i'm from texas please fix it
Reston,VA Same problem.
FFXIV Exodus Server. VerizonTech Support is clueless. Punching the clock.
Can we add a "If you work as an IT Professional and Don't Want to Be Told to Restart Your Device Again and get a real Fing Technichician (if you are lottery ticket lucky) on the Line Press 9" to the dialing tree please?
THX
Yes, still waiting for Verizon to sort out their packetloss.
You guys are not alone in this issue. I have expereienced this issue on both Final Fantasy and Planetside 2 since that time and with no other games or locations. After much searching and working around without the help of Verizon support (as all they will ever do is say things like , restart your router, or speed test, and the occasional I have restarted your junction box in your home) I found an article about Verizon's service and how it is lost with Alter.Net and pingplotter and traceroute both came back for both games with that exact same domain between them.
It seems like Verizon is taking the stance that they aren't to blame since it's not their location, and who could honestly blame them. Sadly other companies have taken it upon themselves to contact companies and secure more reliable routes through their systems and Verizon isn't doing the same.
Guess if you want to play any game or visit any website that travels through that domain you're most likely in trouble.
Guess it's a good thing we have so many other options available to us, but I am truely disheartened that I will have to give up a service i love to enjoy doing things I always had in the past.
