|
Latency in Granite BayHigh Speed bundle 55 Aris docsis3.0
Not getting advertised speed, it's about half actually. Worse, there's intermittent connectivity and latency issues abound. It usually starts at 8-11pm every night, however noticed tonight it was already bad by 6pm.
Ping plotter to the east coast shows a couple hops locally (after wave, but before getting out of Roseville) which have no named DNS entries, strange. It's there where it all drops off.
Called tech support to be hung up on as the line went dead. Calling back and a recording comes on stating this number's not receiving calls anymore? |
|
|
anon345235
Anon
2014-Aug-13 12:48 am
Also in granite bay and getting terrible speeds along with the long latency as you mentioned. I'm on the 110mb plan. |
|
|
to truckeelink
Me too. Last few weeks. I'm in Rocklin and have the 55 mpbs plan. Latency to Yahoo is over 600 ms. Almost unusable. |
|
bmccoy join:2013-03-18 Port Orchard, WA |
to truckeelink
Could you run a traceroute to see where the problem might be? |
|
|
to truckeelink
Getting the same here. Been doing this the last couple weeks. Will start around peak time (8pm. or so PST.), sometimes even earlier. Using pingplotter you can see it always starts at the 4th hop. The test with no ping/latency issues was at 11:00am on the 11th. When I called Wave they said the same - that once it gets to the 4th hop it's out of their 'service'. My question then, would be, who sends their signal to those points then? Is it determined by the router or modem? - Those are tests to a server in TX, fyi. |
|
|
Marvin
Anon
2014-Aug-13 10:52 pm
I talked to them yesterday regarding the same issue, I've been having these issues for the last 3 months. The tech that I talked to over the phone mentioned that there was a very large ticket list to perform a maintenance that was suppose to fix these issues. But I'm see experiencing the same problems today.
After performing a trace route to Google@ 7:52pm, I am seeing an average of ping from 200-300 from hops 4-10. |
|
|
anon345235
Anon
2014-Aug-13 11:18 pm
Yeah, looks like I am seeing the same thing:
C:\Users\>tracert www.google.com
Tracing route to www.google.com [74.125.239.112] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms router.asus.com [192.168.5.1] 2 11 ms 8 ms 5 ms rk.wavecable.com [xx.xx.xx.xx] 3 15 ms 6 ms 7 ms te-1-2.ar01.rkln-ca.wavecable.com [xx.xx.xx.xx] 4 11 ms 8 ms 8 ms 172.16.17.5 5 238 ms 248 ms 244 ms ip65-46-225-9.z225-46-65.customer.algx.net [65.4 6.225.9] 6 226 ms 257 ms 261 ms ae1d0.mcr1.roseville-ca.us.xo.net [216.156.1.77]
7 246 ms 250 ms 252 ms vb1510.rar3.sanjose-ca.us.xo.net [216.156.0.153]
8 256 ms 244 ms 237 ms ae0.cir1.sanjose2-ca.us.xo.net [207.88.13.73] 9 235 ms 230 ms 245 ms 216.156.85.86.ptr.us.xo.net [216.156.85.86] 10 252 ms 250 ms 263 ms 216.239.49.170 11 237 ms 246 ms 229 ms 66.249.95.29 12 250 ms 233 ms 240 ms nuq05s01-in-f16.1e100.net [74.125.239.112]
Trace complete. |
|
bmccoy join:2013-03-18 Port Orchard, WA |
bmccoy
Member
2014-Aug-14 12:57 am
It looks like a problem with XO Communications, Wave's backbone provider in CA. ALGX.net belongs to XO Communications. |
|
|
to anon345235
Why doesn't Wave get with XO Communications... or maybe we should? » twitter.com/XOCare |
|
truckeelink |
By golly I think they fixed it. Please check your internetz tonight and report back... |
|
jwvo join:2001-07-27 Seattle, WA |
jwvo
Member
2014-Aug-14 9:59 pm
This should be resolved now, there is a bunch of work being done down there to prevent a reoccurrence of the issue.
Thanks, John |
|
|
Actually, no it's not resolved. I'm sorry to report and spoke too soon. |
|
truckeelink |
to jwvo
I think I should have replied to jwvo sorry. So this doesn't seem resolved, very unfortunate.
|
|
|
RickyB6
Member
2014-Aug-14 11:51 pm
Yeah if I do a pingplotter trace right at this moment.. I'm getting 288 ping on the 4th hop (from 15 ping on the 3rd) to 216.55.44.17, with a round trip ping of 279. This is a trace to google @ 8:49 pm PST (Sacramento) |
|
jwvo join:2001-07-27 Seattle, WA |
jwvo
Member
2014-Aug-15 1:06 am
I am checking on it again. This part of the network is not a part I have good visibility into yet but that should be coming soon. Some sort of router issue as I understand it. |
|
|
Is their a reason this is only happening at peak times? (B/t ~7-11pm, PST) is it simply traffic at this time or coincidence? |
|
|
We have been stable with readings like this for over 24 hours... Much thanks goes out to jwvo!
|
|
jwvo join:2001-07-27 Seattle, WA |
jwvo
Member
2014-Aug-23 8:38 pm
The team found the problem, there was an issue related to the crazy way 10G ports on Cisco WS6708-10G 8 port 10G linecards are spread between ASICS that was causing the buses between ports to fill with certain traffic patterns.
Actually, you won't see it other than in the traceroute, but a bunch more upgrades are coming soon there that should help with peering and removing the XO paths.
John |
|