The Night Fox.6018 Posted May 4, 2018 Share Posted May 4, 2018 Now this is an odd one. I recently switch to google fiber 100 (plan gives up to 100 Mbps in DL and UL speeds) this month in the Nashville area. Around 5:00 PM Central Time, GW2 ping is 250, and persists till 9:00 to 11:00 pm. I have not gathered much data because the rubberbanding and delay on skill usage is aggravating, making pvp and raiding unplayable. Strangely, before 5:00 PM, my AVG ping is <30. I've restarted my router several times which does not reduce ping. Anyone else out there had any trouble with google fiber? Any hotfixes that are known that I am not aware of? Link to comment Share on other sites More sharing options...
Inculpatus cedo.9234 Posted May 4, 2018 Share Posted May 4, 2018 Often, when there are issues at certain time-periods of the day, it is due to throttling. You can ask your IS Provider if that is the case (though they may deny it). Also, when I first switched to a 100Mb plan, I was not getting high download speeds; it took a couple of months before I saw a difference (and yes, I called and was told it was a personal [my side of things] problem - of course, it was not). Sometimes, there is high traffic and/or intermittent problems on the backbone your service uses, as well. If so, you usually just have to wait it out, but you can call your provider and ask them to call theirs. Good luck. Link to comment Share on other sites More sharing options...
The Night Fox.6018 Posted May 4, 2018 Author Share Posted May 4, 2018 Hm, maybe there is an issue with the Google Fiber infrastructure being in its infancy that service is rough later in the day? I will contact them in the meantime. Seems to be a large issue then that ISP's are goofing around. Link to comment Share on other sites More sharing options...
hailtonothing.5283 Posted May 4, 2018 Share Posted May 4, 2018 Probably the best thing you can do is run and keep a historical log of http://speedtest.net/ results (or similar) at various times of day to help your case. Link to comment Share on other sites More sharing options...
The Night Fox.6018 Posted May 4, 2018 Author Share Posted May 4, 2018 > @"hailtonothing.5283" said: > Probably the best thing you can do is run and keep a historical log of http://speedtest.net/ results (or similar) at various times of day to help your case. Strange, according to that test I have 2 ping, 100, 100, but I have GW2 up and running saying I got Avg:270 (still high rubberbanding/delay). I've called Fiber, they reconnected me in efforts to solve the issue. Their diagnostics say the service is running fine. That must mean it's either my machine is not connected to the wifi properly (ethernet), which I doubt is the issue after checking, or my location is having trouble connecting to GW2 servers? Seems like the ball is in Anet's court regarding these issues, but I'm confused as to why I would have problems now when I switch ISP's when I didn't have difficulties before. Link to comment Share on other sites More sharing options...
Inculpatus cedo.9234 Posted May 4, 2018 Share Posted May 4, 2018 Because they take a different route to the servers? This is why VPNs often solve connection issues. Link to comment Share on other sites More sharing options...
hailtonothing.5283 Posted May 4, 2018 Share Posted May 4, 2018 > @"The Night Fox.6018" said: > > Strange, according to that test I have 2 ping, 100, 100, but I have GW2 up and running saying I got Avg:270 (still high rubberbanding/delay). > > I've called Fiber, they reconnected me in efforts to solve the issue. Their diagnostics say the service is running fine. > That must mean it's either my machine is not connected to the wifi properly (ethernet), which I doubt is the issue after checking, or my location is having trouble connecting to GW2 servers? > > Seems like the ball is in Anet's court regarding these issues, but I'm confused as to why I would have problems now when I switch ISP's when I didn't have difficulties before. Okay so it's not with your ISP directly then, unless they are throttling traffic over whatever ports ArenaNet uses. Someone has linked a ping/diagnostic tool on these forums - have a look around some of the other posts about latency issues and you should find it pretty quickly. Likely there'll be a hop somewhere along the route that is problematic. If you can find it, you might be able to ask the ISP about it and see if there is anything they can do to avoid or solve the problem. Link to comment Share on other sites More sharing options...
The Night Fox.6018 Posted May 4, 2018 Author Share Posted May 4, 2018 > @"Inculpatus cedo.9234" said: > Because they take a different route to the servers? This is why VPNs often solve connection issues. Wouldn't this mean the latency issues would persist throughout the day instead of localized around the evening? In any case, I turned on IVPN based off your hunch, connected to Chicago, and wahbam.... 56 ping. No rubberbanding or massive delay in actions. I'm thoroughly confused but I'm glad I have the tools required to play this fricken game. Do you know of any alternative solutions to this seemingly ISP problem with connectivity? Or am I just the odd-one who gets boned? Link to comment Share on other sites More sharing options...
The Night Fox.6018 Posted May 4, 2018 Author Share Posted May 4, 2018 > Okay so it's not with your ISP directly then, unless they are throttling traffic over whatever ports ArenaNet uses. > If you can find it, you might be able to ask the ISP about it and see if there is anything they can do to avoid or solve the problem. It has to be throttling, or w/e is going on with the ISP and Anet's servers. I'll check with them tomorrow. Thanks for all the help. Link to comment Share on other sites More sharing options...
hailtonothing.5283 Posted May 4, 2018 Share Posted May 4, 2018 I think this was the one https://pingplotter.com/fix-your-network I've used basic "tracert" in the command prompt to alert my ISP to issues before. They may be able to reroute traffic, or get in contact with provider of that network to resolve issues, or maybe they can't do anything - I'd say it's grounds to leave any contract you might be under though if they can't resolve it. Link to comment Share on other sites More sharing options...
The Night Fox.6018 Posted May 4, 2018 Author Share Posted May 4, 2018 > @"hailtonothing.5283" said: > > I think this was the one > https://pingplotter.com/fix-your-network > > I've used basic "tracert" in the command prompt to alert my ISP to issues before. They may be able to reroute traffic, or get in contact with provider of that network to resolve issues, or maybe they can't do anything - I'd say it's grounds to leave any contract you might be under though if they can't resolve it. I sure hope they can resolve it. Using an IVPN isnt that big of a deal, and google Fiber is hella cheap compared to competitors in Music City. Link to comment Share on other sites More sharing options...
hailtonothing.5283 Posted May 4, 2018 Share Posted May 4, 2018 Having to work around the issue is annoying, for sure, but if it's still better than your other options, then you're probably still in an okay position. But gather some diagnostics at different times of day (do it over multiple days, a week) to prove the hours it's happening and that it's an ongoing issue, and see what they can do to fix it! Link to comment Share on other sites More sharing options...
The Night Fox.6018 Posted May 4, 2018 Author Share Posted May 4, 2018 Posted below are the issues I think are caused between Anet and Fiber. I think those 100% associated with 10.26.0.169 are the issue. The test also explicitly says 10.26.0.169 reports: Destination net unreachable. Is there a way to turn this information over to Google Fiber? Do I just call and tell them 10.26.0.169 is having issues? Link to comment Share on other sites More sharing options...
The Night Fox.6018 Posted May 4, 2018 Author Share Posted May 4, 2018 > @"The Night Fox.6018" said: > Tracing route to 64.25.33-1.ncsoft.com [64.25.39.1] > over a maximum of 30 hops: > 0 DESKTOP-P93TK4I [192.168.1.195] > 1 192.168.1.1 > 2 10.26.0.169 > 3 192-119-18-232.mci.googlefiber.net [192.119.18.232] > 4 192-119-18-139.mci.googlefiber.net [192.119.18.139] > 5 * * * > Computing statistics for 50 seconds... > Source to Here This Node/Link > Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address > 0 DESKTOP-P93TK4I [192.168.1.195] > 0/ 50 = 0% | > 1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1 > 0/ 50 = 0% | > 2 --- 50/ 50 =100% 50/ 50 =100% 10.26.0.169 > 0/ 50 = 0% | > 3 2ms 1/ 50 = 2% 1/ 50 = 2% 192-119-18-232.mci.googlefiber.net [192.119.18.232] > 0/ 50 = 0% | > 4 2ms 0/ 50 = 0% 0/ 50 = 0% 192-119-18-139.mci.googlefiber.net [192.119.18.139] > > Trace complete. > *--> pathping -w 500 -q 50 -4 206.127.158.1 <--* > > Tracing route to 206-127-158-1.ncsoft.com [206.127.158.1] > over a maximum of 30 hops: > 0 DESKTOP-P93TK4I [192.168.1.195] > 1 192.168.1.1 > 2 10.26.0.169 reports: Destination net unreachable. > > Computing statistics for 25 seconds... > Source to Here This Node/Link > Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address > 0 DESKTOP-P93TK4I [192.168.1.195] > 0/ 50 = 0% | > 1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1 > 50/ 50 =100% | > 2 --- 50/ 50 =100% 0/ 50 = 0% DESKTOP-P93TK4I [0.0.0.0] > > Trace complete. > *--> pathping -w 500 -q 50 -4 52.84.139.76 <--* > > Tracing route to server-52-84-139-76.yto50.r.cloudfront.net [52.84.139.76] > over a maximum of 30 hops: > 0 DESKTOP-P93TK4I [192.168.1.195] > 1 192.168.1.1 > 2 10.26.0.169 > 3 192-119-18-232.mci.googlefiber.net [192.119.18.232] > 4 * * * > Computing statistics for 37 seconds... > Source to Here This Node/Link > Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address > 0 DESKTOP-P93TK4I [192.168.1.195] > 0/ 50 = 0% | > 1 0ms 0/ 50 = 0% 0/ 50 = 0% 192.168.1.1 > 0/ 50 = 0% | > 2 --- 50/ 50 =100% 50/ 50 =100% 10.26.0.169 > 0/ 50 = 0% | > 3 2ms 0/ 50 = 0% 0/ 50 = 0% 192-119-18-232.mci.googlefiber.net [192.119.18.232] Link to comment Share on other sites More sharing options...
hailtonothing.5283 Posted May 4, 2018 Share Posted May 4, 2018 > @"The Night Fox.6018" said: > Posted below are the issues I think are caused between Anet and Fiber. I think those 100% associated with 10.26.0.169 are the issue. The test also explicitly says 10.26.0.169 reports: Destination net unreachable. > Is there a way to turn this information over to Google Fiber? Do I just call and tell them 10.26.0.169 is having issues? I'm not sure if that's a fiber problem - sorry I'm not too sure how to read pathping info - when I tracert that IP it is also unreachable for me, so it might be that ping is simply denied on the network, or the IP is just unavailable to begin with. Tracing route to 206-127-158-1.ncsoft.com [206.127.158.1] over a maximum of 30 hops: 1 4 ms 4 ms 4 ms 192.168.43.1 2 * * * Request timed out. 3 46 ms 26 ms 30 ms 10.194.31.209 4 28 ms 16 ms 38 ms 10.194.124.2 5 79 ms 37 ms 19 ms 10.194.124.13 6 40 ms 27 ms 34 ms 10.194.124.202 7 53 ms 31 ms 29 ms 210.49.49.41 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 41 ms 36 ms 38 ms 198.142.250.193 12 188 ms 37 ms 42 ms 198.142.139.114 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Though the first IP is comparatively fine. What I would be looking for is places where the ping is jumping or spiking. Tracing route to 64.25.33-1.ncsoft.com [64.25.39.1] over a maximum of 30 hops: 1 6 ms 4 ms 5 ms 192.168.43.1 2 * * * Request timed out. 3 51 ms 37 ms 38 ms 10.194.31.145 4 184 ms 45 ms 37 ms 10.194.124.2 5 24 ms 19 ms 37 ms 10.194.124.9 6 35 ms 46 ms 29 ms 10.194.124.194 7 187 ms 19 ms 47 ms 210.49.49.41 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * 51 ms 38 ms 198.142.250.193 12 64 ms 35 ms 48 ms 198.142.139.114 13 249 ms 208 ms 219 ms 203.208.174.41 -------See this compared with the previous line? I'm international so this is probably just getting overseas for me, but if you're seeing a jump like that, that's what you would want to report to ISP customer service because you're slowing down from there to here. 14 * * * Request timed out. 15 * * * Request timed out. 16 * 315 ms 317 ms 4.59.197.34 17 577 ms 313 ms 235 ms 64.25.32-9.ncsoft.com [64.25.32.9] 18 252 ms 221 ms 244 ms 64.25.32-26.ncsoft.com [64.25.32.26] 19 356 ms 222 ms 413 ms 64.25.33-1.ncsoft.com [64.25.39.1] Again, having this evidence at multiple times of day, over a few days or a week is going to be better to show a consistent issue. But being able to see that jump from (in this case 198.142.139.114 and 203.208.174.41 (I haven't done a whois on these addresses, I'm just guessing at the moment. Link to comment Share on other sites More sharing options...
hailtonothing.5283 Posted May 4, 2018 Share Posted May 4, 2018 Just confirmed via whois (use this URL and replace the IP https://dig.whois.com.au/ip/203.208.174.41) that the large spike in my ping times is from Australia to Singapore, as I suspected. Yours may simply be across networks, and using whois you should be able to find who that belongs to, report it to your ISP and ask if they can do anything about it. Link to comment Share on other sites More sharing options...
Healix.5819 Posted May 4, 2018 Share Posted May 4, 2018 > @"The Night Fox.6018" said: > Posted below are the issues I think are caused between Anet and Fiber. I think those 100% associated with 10.26.0.169 are the issue. The -diag option is outdated. 64.* and 206.* are the original NCSoft servers, which are no longer in use. 206.* is unreachable because it no longer exists - NCSoft shutdown their EU data center, hence GW2 now being at Amazon. The pathping command stops at the first hop that doesn't respond to pings, making it useless in your case since it stops early on. When you're lagging in-game, type /ip in chat to get the IP of the instance you're in, then use it with PingPlotter and let it run for a while to get a decent sample. Link to comment Share on other sites More sharing options...
The Night Fox.6018 Posted May 4, 2018 Author Share Posted May 4, 2018 > @"Healix.5819" said: > > @"The Night Fox.6018" said: > > Posted below are the issues I think are caused between Anet and Fiber. I think those 100% associated with 10.26.0.169 are the issue. > > The -diag option is outdated. 64.* and 206.* are the original NCSoft servers, which are no longer in use. 206.* is unreachable because it no longer exists - NCSoft shutdown their EU data center, hence GW2 now being at Amazon. > > The pathping command stops at the first hop that doesn't respond to pings, making it useless in your case since it stops early on. When you're lagging in-game, type /ip in chat to get the IP of the instance you're in, then use it with PingPlotter and let it run for a while to get a decent sample. Yeah, apparently 10.26.0.169 is unreachable/discontinued. So that is not the issue. I'll have to wait this evening for the lagging to beginning, and then I'll use pingplotter to figure out what the heck is going on. Link to comment Share on other sites More sharing options...
hailtonothing.5283 Posted May 5, 2018 Share Posted May 5, 2018 It's a good idea to get a "baseline" of when it's running well also, so that you can see the difference and what it should like look when everything is fine. It should make diagnosing the standout issue easier. Link to comment Share on other sites More sharing options...
datatobridge.3785 Posted May 6, 2018 Share Posted May 6, 2018 I'm also on Google Fiber and have high latency right around reset and for a couple hours after. Connecting via a VPN fixes the issue (VPN still adds _some_ latency though). I'm fairly sure that the route to the N. Virginia AWS data center is just congested or the routing is bad. That's probably something only Google can fix. On the other hand, a lot of the people I play with have had increasing connection issues since the switch the AWS. Link to comment Share on other sites More sharing options...
SlippyCheeze.5483 Posted May 6, 2018 Share Posted May 6, 2018 > @"datatobridge.3785" said: > I'm also on Google Fiber and have high latency right around reset and for a couple hours after. Connecting via a VPN fixes the issue (VPN still adds _some_ latency though). I'm fairly sure that the route to the N. Virginia AWS data center is just congested or the routing is bad. That's probably something only Google can fix. On the other hand, a lot of the people I play with have had increasing connection issues since the switch the AWS. Ideally, [follow the (poorly named) PingPlotter guide](https://pingplotter.com/fix-your-network) and figure out exactly where that is happening, then contact either Google Fiber or ANet support -- or potentially both, if it is shared infrastructure -- and ask them to fix it. ANet have identified that there are some slow to update routing annoyances following the switch, but those should clear up soon-ish, so this is a good time to start treating them as problems that need poking to solve. If you are not willing to do that, definitely contact Google Fiber support, and communicate with them about this. Especially with the fact a VPN improves the situation, they should resolve it - or at least identify to you where the issue is. (Though, honestly, most of the time they will start by asking for those same diagnostics, so ... get a head start. ;) Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now