I have been experiencing 5-60 seconds of lag in the evening hours Central Time for over the past month. I have checked with my ISP (Google Fiber) and after performing the pathping traceroute I am getting a lot of packet loss on hop 8-12 all of which are outside of Google's network. They suggested I contact you regarding this issue. I would be happy to forward those emails to you as well as show you the results of the traceroute. I pay good money to play FFXIV and have been playing ever since beta. Please HELP!!!
5-60 seconds of Lag
Printable View
-
11-05-2014, 08:58 AMMetalios5-60 seconds of Lag
-
11-05-2014, 09:51 AMCronolith
Experiencing the same issues (packet loss resulting in 5-60 second lag, 90k disconnects and a couple 10105s) but my ISP is Cox and have confirmed it is not their network but outside of it. Same thing here that is on the last few hops where the issues are occurring.
-
11-06-2014, 04:42 AMKamitechi
I'm having the same issues, no 90k's or other errors, but since last week I Have been having these freezes almost all the time during the evening-night on european time, I tried to contact with my provider, but it doesn't seem to be a problem with them, any other game/internet service is working flawlessly, before last week my connection to the game was good.
Just for reference, ill leave my isp name and server, it might help:
ISP : Netvision
Server: Cerberus
Country: IL -
11-06-2014, 04:52 AMKerwin
Most likely going to be fixed in tonight's hot fix. I swear they hot fix a hot fix more then anything lol.
-
11-06-2014, 05:15 AMRaphaelDDLthey hot fix a hot fix to keep them from becoming cold :vQuote:
Originally Posted by Kerwin
-
11-11-2014, 02:51 AMMetalios
This issue is still not fixed! Devs Please Help
Code:0 HEIMDALL.home [192.168.1.126]
1 networkbox.home [192.168.1.1]
2 10.26.0.17
3 ae6.ar02.mci101.googlefiber.net [192.119.17.130]
4 ae10.ar02.mci101.googlefiber.net [192.119.17.70]
5 ae0.ar01.ord101.googlefiber.net [192.119.17.55]
6 ae3.ar01.ord101.googlefiber.net [192.119.17.65]
7 xe-1-3-0.chi11.ip4.gtt.net [199.229.231.109]
8 xe-1-0-0.mtl10.ip4.gtt.net [89.149.185.41]
9 ormuco-gw.ip4.gtt.net [216.221.156.110]
10 192.34.76.2
11 199.91.189.234
12 199.91.189.26
Computing statistics for 765 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 HEIMDALL.home [192.168.1.126]
0/ 255 = 0% |
1 0ms 0/ 255 = 0% 0/ 255 = 0% networkbox.home [192.168.1.1]
0/ 255 = 0% |
2 --- 255/ 255 =100% 255/ 255 =100% 10.26.0.17
0/ 255 = 0% |
3 1ms 0/ 255 = 0% 0/ 255 = 0% ae6.ar02.mci101.googlefiber.net [1
92.119.17.130]
0/ 255 = 0% |
4 6ms 0/ 255 = 0% 0/ 255 = 0% ae10.ar02.mci101.googlefiber.net [
192.119.17.70]
0/ 255 = 0% |
5 12ms 0/ 255 = 0% 0/ 255 = 0% ae0.ar01.ord101.googlefiber.net [1
92.119.17.55]
0/ 255 = 0% |
6 12ms 0/ 255 = 0% 0/ 255 = 0% ae3.ar01.ord101.googlefiber.net [1
92.119.17.65]
0/ 255 = 0% |
7 13ms 0/ 255 = 0% 0/ 255 = 0% xe-1-3-0.chi11.ip4.gtt.net [199.22
9.231.109]
18/ 255 = 7% |
8 110ms 30/ 255 = 11% 12/ 255 = 4% xe-1-0-0.mtl10.ip4.gtt.net [89.149
.185.41]
0/ 255 = 0% |
9 101ms 28/ 255 = 10% 10/ 255 = 3% ormuco-gw.ip4.gtt.net [216.221.156
.110]
0/ 255 = 0% |
10 100ms 24/ 255 = 9% 6/ 255 = 2% 192.34.76.2
0/ 255 = 0% |
11 100ms 18/ 255 = 7% 0/ 255 = 0% 199.91.189.234
5/ 255 = 1% |
12 100ms 23/ 255 = 9% 0/ 255 = 0% 199.91.189.26
Trace complete.
-
11-11-2014, 03:34 AMJayHiro
i am getting the exact same issues, been dealing with this 2 or 3 days after 2.4 dropped. this is becoming an issue. to the point where its unplayable. its not my net. i made 100% sure of it. nothing else lags for me. its just all this rubberbanding in game. makes raiding close to impossible.
-
11-11-2014, 05:30 AMSqua11_Leonhart
oh look, this thread again (number 9001).
-
11-11-2014, 08:22 AMRaistAnd once again the problem may be staring us in the face... and it isn't something that SE can address.Quote:
Originally Posted by Squa11_Leonhart
For the umpteenth time... you need to be dealing with Tier3 techs, forwarding this data and pushing for escalation. There is a problem with Google's routing partner (tinet) that THEY are responsible for addressing on your behalf. Google is electing to put you on their network, which is causing problems. SE can't do anything about Google Fiber's routing policies.
Run some traces (not pathping, normal tracert/traceroutes) to your client's server as well as some other services. If you capture results showing high jitter at times and low jitter at others, save them to forward them to Google's Tier3 department. If the tier1/tier2 guys you get stuck with on the phone keep giving you the run-around about not seeing a problem or not being able to do anything about problems beyond their network, or otherwise refuse to escalate you to a higher tier that actually can, go to their support website or forums to get the contact information. Tier3 (or their network admins) need to see these numbers so they know where to look and who to pull in to address your problems. They CAN and SHOULD fix this. They have a host of other partners to choose from. Here is just a snippet of the ASN's they have ties with (selection may be limited in some regions, but the big 3 are likely available out there in/around Kansas--for example, Level3 has multiple exchanges around Wichita, Topeka, and Kansas City...as do others):Code:6 12ms 0/ 255 = 0% 0/ 255 = 0% ae3.ar01.ord101.googlefiber.net [192.119.17.65]
0/ 255 = 0% |
7 13ms 0/ 255 = 0% 0/ 255 = 0% xe-1-3-0.chi11.ip4.gtt.net [199.229.231.109]
18/ 255 = 7% |
8 110ms 30/ 255 = 11% 12/ 255 = 4% xe-1-0-0.mtl10.ip4.gtt.net [89.149.185.41]
http://bgp.he.net/AS15169
http://chart.googleapis.com/chart?ch...er&chco=346090
If they still refuse to investigate/address your concerns after laying them out with such detail, then you may be able to go after your local regulatory authority so they can lean on them to take action (provided your area has such enforcement). If they are accountable to regulatory oversight in your area, the contact information for that authority will be included with your bill, or at the very least they will provide link/number you can call to get the information. They would have to provide this information by law if they are under such authority--especially if you request it from them directly (which can sometimes put a fire under their butts too if you ask them directly for the contact info when you have them on the phone discussing your problems). Otherwise, you may be able to file a complaint with a higher authority like the FTC and such (unfair practices clause and whatnot). The point is, it is our ISP's responsibility to investigate and address the problems bound to their service and we need to find ways to hold them accountable for those decisions. It is their policies that are keeping people locked into shotty routes.