i was wondering if anyone in xoo has had or knows a lot about cable modems and nodes and amps would be willingly to help me with my problems as far as very bad lag. this has been a problem since mid February. i mean, i get very low to high pings. from 9ms to 1000+ ms. this crap has been happening mostly during the hours of 8:30 pm to midnight est. (it's like clock work. i could set my watch to it. today, it's been an ongoing problem... throughout the day. in game at night, sometimes, i'm on the verge of laging out or ci-ing. this problem comes and goes like a Hawaii wave. it happens for a 1 minute, then it's fine for 5 minutes and starts lagging again. i don't use any p2p sharing, and i know it's not any dl's for updates. ISP: Knology Cable (i'm a bundled customer TV, phone, and internet) Region/city: Columbus, GA I go through a wtrg 54 router: i'm on cable not wireless though. it's security enabled. Modem name Arris RF Parameters Downstream Freq/Power: 585.000 MHz -7 dBmV Signal to Noise Ratio: 38 dB Modulation: QAM256 Upstream Freq/Power: 24.500 MHz 35 dBmV Channel Type: DOCSIS 1.x (TDMA) Symbol Rate: 2560 kSym/sec Modulation: QPSK i have had 5 techs out to my house since mid feb. but they don't find a thing wrong on my end. i have a guy coming out on tuesday and i'm going to have him monitor the line to see what is going on so they can see. adding a couple of trace routes from 10 pm est sunday night.... Trace complete. C:\Users\Tim>tracert yahoo.com Tracing route to yahoo.com [206.190.60.37] over a maximum of 30 hops: 1 1 ms 1 ms 2 ms 192.168.2.1 2 29 ms 22 ms 20 ms dynamic-216-186-241-1.knology.net [216.186.241.1 ] 3 285 ms 83 ms 67 ms dynamic-75-76-40-181.knology.net [75.76.40.181] 4 646 ms 285 ms 231 ms user-24-96-198-125.knology.net [24.96.198.125] 5 146 ms 141 ms 154 ms user-24-96-198-121.knology.net [24.96.198.121] 6 30 ms 15 ms 21 ms ge.1-1-2.cr-Atla.GA.US.knology.net [24.214.0.221 ] 7 17 ms 23 ms 73 ms GigabitEthernet3-4.ar1.ATL2.gblx.net [64.208.222 .209] 8 27 ms 28 ms 29 ms yahoo-1.ar1.MIA2.gblx.net [64.215.195.130] 9 100 ms 67 ms 69 ms ge-0-3-2-p198.pat2.sjc.yahoo.com [216.115.96.22] 10 52 ms 44 ms 47 ms ae1-p150.msr2.re1.yahoo.com [216.115.108.21] 11 48 ms 45 ms 49 ms te-8-3.bas-a1.re4.yahoo.com [216.39.49.1] 12 90 ms 71 ms 62 ms w2.rc.vip.re4.yahoo.com [206.190.60.37] Trace complete. C:\Users\Tim>tracert yahoo.com Tracing route to yahoo.com [206.190.60.37] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.2.1 2 19 ms 18 ms 24 ms dynamic-216-186-241-1.knology.net [216.186.241.1 ] 3 76 ms 95 ms 46 ms dynamic-75-76-40-181.knology.net [75.76.40.181] 4 118 ms 1124 ms 713 ms user-24-96-198-125.knology.net [24.96.198.125] 5 203 ms 211 ms 386 ms user-24-96-198-121.knology.net [24.96.198.121] 6 131 ms 114 ms 130 ms ge.1-1-2.cr-Atla.GA.US.knology.net [24.214.0.221 ] 7 74 ms 103 ms 111 ms GigabitEthernet3-4.ar1.ATL2.gblx.net [64.208.222 .209] 8 44 ms 66 ms 35 ms yahoo-1.ar1.MIA2.gblx.net [64.215.195.130] 9 67 ms 72 ms 46 ms ge-0-3-2-p198.pat2.sjc.yahoo.com [216.115.96.22] 10 50 ms 44 ms 48 ms ae2-p140.msr1.re1.yahoo.com [216.115.108.57] 11 123 ms 108 ms 86 ms te-9-3.bas-a1.re4.yahoo.com [216.39.49.3] 12 400 ms 292 ms 116 ms w2.rc.vip.re4.yahoo.com [206.190.60.37] Trace complete. C:\Users\Tim> thx.
dude, I just started having the same issues this past week when you mentioned it to me like a week or something ago. Literally the same issues as you. But im in florida..
ive had this happen to me as well, though your's is your ISP look at hops 4 and 5 respectively. its still in the knology.net range, so its them. that makes it likely that they are throttling your bandwidth due to peak hours and/or you are in a heavy density subcriber area for knology... meaning the massive numbers of people in the area are slowing their whole system. either way, they should be contacted. if they are willing to help, then i would say you're lucky. my ISP has been very helpful but my tracert spikes after it leaves their control. though it's odd that of the 12 hops in the good times, 6 are knology. can you tracert something else to compare?
Not to hijack Khane, because im having the same issue as well. But with me, I will get massive lag, in wow and in vent jumping to 30k ping sometimes and or trying to browse the web, and then it will be fine... But it is at odd times through out the day and then literally around 9pm I get it all the time.
I used to get that on my ISP over here. Its like what was mentioned above, busy area and the ISP throttles the bandwidth used by online games so you end up getting massive spikes of 20k+ ping. There isnt any way around it except to put up with it or find a better ISP that is more friendly towards gamers -_-
here are 2 trace routes, 1 to the ventrilo, the other to the cod4 server. Tracing route to 8.9.12.168 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 192.168.2.1 2 13 ms 11 ms 11 ms dynamic-216-186-241-1.knology.net [216.186.241.1] 3 9 ms 12 ms 11 ms dynamic-75-76-40-181.knology.net [75.76.40.181] 4 9 ms 12 ms 12 ms user-24-96-198-125.knology.net [24.96.198.125] 5 10 ms 12 ms 12 ms user-24-96-198-121.knology.net [24.96.198.121] 6 89 ms 12 ms 13 ms ge.1-1-2.cr-Atla.GA.US.knology.net [24.214.0.221] 7 13 ms 12 ms 12 ms GigabitEthernet3-4.ar1.ATL2.gblx.net [64.208.222.209] 8 32 ms 39 ms 33 ms INTERNAP.ae0.411.ar1.DAL2.gblx.net [208.51.41.58] 9 46 ms 49 ms 133 ms border4.pc2-bbnet2.ext1.dal.pnap.net [216.52.191.94] 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 ^C C:\Users\Tim>tracert 69.12.98.74 Tracing route to 69.12.98.74 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 192.168.2.1 2 12 ms 13 ms 10 ms dynamic-216-186-241-1.knology.net [216.186.241.1] 3 10 ms 9 ms 9 ms dynamic-75-76-40-181.knology.net [75.76.40.181] 4 9 ms 9 ms 12 ms user-24-96-198-125.knology.net [24.96.198.125] 5 12 ms 11 ms 12 ms user-24-96-198-121.knology.net [24.96.198.121] 6 11 ms 12 ms 12 ms ge.1-1-2.cr-Atla.GA.US.knology.net [24.214.0.221] 7 13 ms 14 ms 12 ms 207.13.126.69 8 12 ms 12 ms 16 ms sl-crs2-atl-0-4-0-0.sprintlink.net [144.232.18.134] 9 36 ms 37 ms 37 ms sl-crs2-rly-0-4-2-0.sprintlink.net [144.232.20.175] 10 32 ms 34 ms 34 ms sl-crs2-dc-0-12-2-0.sprintlink.net [144.232.19.221] 11 38 ms 38 ms 39 ms sl-st31-ash-0-8-0-0.sprintlink.net [144.232.19.6] 12 32 ms 34 ms 35 ms 4.68.63.205 13 39 ms 36 ms 34 ms vlan89.csw3.Washington1.Level3.net [4.68.17.190] 14 40 ms 53 ms 35 ms ae-84-84.ebr4.Washington1.Level3.net [4.69.134.185] 15 38 ms 36 ms 37 ms ae-3-3.ebr1.NewYork1.Level3.net [4.69.132.94] 16 40 ms 52 ms 39 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66] 17 38 ms 37 ms 38 ms ge-7-0.ipcolo2.NewYork1.Level3.net [4.68.97.14] 18 38 ms 38 ms 38 ms 166.90.136.34 19 38 ms 38 ms 40 ms 69.12.98.74 Trace complete. C:\Users\Tim> i just did these at 11 am est. i just called and asked if i could have be connected to an it guy who can work this problem since it's not a physical location problem. yet, the only thing this guy could do is schedule a tech to come out. this will make # 6 in 1 month.
Those numbers look fine, but that doen't mean that the node isn't congested or that there isn't something causing interference on those frequencies. First thing I ALWAYS suspect is the cable router though... have you tried plugging right into the cable modem and tested it? A speed test site is a good way to test your bandwidth. http://www.dslreports.com/ It's very possiable though that the ISP is just over subscribed for the area... a few crazy bit torrent users can suck up an entire nodes worth of bandwidth if it's not controlled... If it's perfect in the day or late night (3am and on) and slowly gets worse near 4pm or so that sounds like congestion. (peak usage starts around 7pm and goes through to about 1am for us)
traceroutes are not a great way to trouble shoot. First the packets can use one path for outbound, and another for inbound... traceroutes will not show that at all, second a lot of routers drop ICMP packets totally, meaning the timeouts are not really a sign of a problem. Next if you do look at your trace route, you start on Knology.net. You stay on that network (I assume your ISP) for 6 hops with no problems. You then move onto gblx.net for 2 hops and then onto pnap.net. IF those time outs are legit problems, the problem is not your ISP, it's a problem with pnap.net... The second traceroute is well onto Level3 which is a backbone provider... If your seeing problems that far into a traceroute, it's not your ISPs issue. To sum up, those traceroutes don't really tell anyone anything. If you can connect to 8.9.12.168 (vent? or cod server?) then your traceroute isn't dead at those timeouts... if it was dead then you couldn't connect to the end location. The only real value in traceroutes these days is to look for large ping spikes and even that can be misleading as if your hitting a router at the same time as it's doing a BGP update or something like that, the ICMP request is very low in the priority list so the ping is going to be much higher then real traffic is really passing though the router.
Why would they throttle bandwidth used by online games? (I sorta suspect that they were not doing that... and that was just a rumor) Game traffic is very small compared to HTTP, YouTube, BitTorrent and would do nothing to help them with bandwidth costs or congestion. Just to give an example, at the moment my ISP is seeing about 4Gb/s of bittorrent traffic, another 4Gb/s of HTTP and about 1Gb/s of YouTube traffic... while we only see about 100Mb/s of Gaming traffic (not all games are tracked but a lot of the big ones are... cod, wow, eq etc)
lol they are on crack then... P2P sure, but throttling gaming indicates someone that hasn't bothered to look at the amounts of traffic the different apps generate. I could also see them tossing everything except port 80 into a throttled offer of some type just to make things easier, but then I would call that making HTTP high priority over other apps, not limiting the rest
I know, i made several calls to them saying im not a heavy user (I had a 40gb limit and rarely went above 20-25gb) but they said they would still throttle P2P and games whilst limiting my speed. I dont have a link but the last time i was at home and did a speed test i has 300kb down and 80kb up.... Thinking of switching to another ISP in the summer, no way can i play with that connection after using my uni one for 8-9 months ><
It means they didn't do their homework is my guess... like I say gaming is small time... and they should be putting that traffic with voip traffic as a priority to give their customers a proper internet experiance.
i've posted on my isp forums on dslreports http://www.dslreports.com/forum/r22114545-NorthEast-Columbus-SLow-internet-at-nights#22114545 reading through, i've found that i'm on hub B of columbus, which is a hub for 2 zip codes. it would be nice to get docis 3.0 in my area sooner than later.
for me, it just started happening like 2 weeks ago or so. Feels like someone downloading shit. Never had an issue though before, but now it is out of control. I have road runner as my ISP but it goes through the cable which is Bright house. Old TWC iirc.
C:\Documents and Settings\Administrator>tracert xoo.ventrilo.org Tracing route to xoo.ventrilo.org [8.9.2.168] over a maximum of 30 hops: 1 <1 ms <1 ms 1 ms 8.9.2.168.ip.divo.net [8.9.2.168] 2 9 ms 10 ms 7 ms 10.195.0.1 3 10 ms 9 ms * 118.233.95.24.cfl.res.rr.com [24.95.233.118] 4 * * * Request timed out. 5 * 23 ms 24 ms ge-1-3-0.cr1.atl20.tbone.rr.com [66.109.6.104] 6 * 23 ms 24 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177] 7 26 ms 30 ms 25 ms TenGigabitEthernet9-2.ar1.ATL2.gblx.net [64.212. 108.69] 8 * 62 ms 62 ms INTERNAP-Chicago.GigabitEthernet3-1.ar5.CHI1.gbl x.net [64.209.102.46] 9 56 ms 66 ms 66 ms border8.po2-bbnet2.chi.pnap.net [216.52.128.76] 10 * * * Request timed out. 11 * * 57 ms 8.9.2.168.ip.divo.net [8.9.2.168] Trace complete.
Tracing route to knology.net [69.73.24.30] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms 192.168.2.1 2 23 ms 18 ms 17 ms dynamic-216-186-241-1.knology.net [216.186.241.1 ] 3 162 ms 144 ms 194 ms dynamic-75-76-40-181.knology.net [75.76.40.181] 4 178 ms 83 ms 172 ms user-24-96-198-125.knology.net [24.96.198.125] 5 130 ms 90 ms 56 ms user-24-96-198-121.knology.net [24.96.198.121] 6 211 ms 267 ms 300 ms gig15-1-0.Wspt.GA.US.knology.net [24.214.2.46] 7 154 ms 87 ms 81 ms eth1-0-0.Wstp.GA.US.knology.net [24.214.0.2] 8 108 ms 114 ms 262 ms www.knology.net [69.73.24.30] Trace complete. C:\Users\Tim>tracert knology.net Tracing route to knology.net [69.73.24.30] over a maximum of 30 hops: 1 2 ms 1 ms 1 ms 192.168.2.1 2 22 ms 17 ms 20 ms dynamic-216-186-241-1.knology.net [216.186.241.1 ] 3 79 ms 89 ms 87 ms dynamic-75-76-40-181.knology.net [75.76.40.181] 4 120 ms 64 ms 44 ms user-24-96-198-125.knology.net [24.96.198.125] 5 57 ms 48 ms 97 ms user-24-96-198-121.knology.net [24.96.198.121] 6 63 ms 46 ms 25 ms gig15-1-0.Wspt.GA.US.knology.net [24.214.2.46] 7 169 ms 114 ms 132 ms eth1-0-0.Wstp.GA.US.knology.net [24.214.0.2] 8 143 ms 227 ms 200 ms www.knology.net [69.73.24.30] Trace complete.
ok, i got a tech to come out and he saw it do it at 9:15 pm est. and it's being turned over to maintenance. a-men.