asiandiscovery Posted December 21, 2007 CID Share Posted December 21, 2007 Couple weeks ago I was getting terrible bandwidth, comcast technician came 2 days ago changed the modem and now im getting 10-13mbps (which should have gone down to 6, but hasnt). Even with the great bandwidth, im pinging a lot more than I should, which makes me think its a routing issue (which of course comcast denies). I mostly play counter-strike and team fortress 2. I'ved ran spyware/virus scans, hooked the modem directly to my comp, and installed steam on another comp in my house just to make sure its not my comp causing the problem. Before I switch isp's I need to make sure I didnt overlook anything. If any1 knows any reason other than my isp that could be causing the problem, please tell me. Link to comment Share on other sites More sharing options...
coknuck Posted December 21, 2007 CID Share Posted December 21, 2007 The extra speed you are getting is boost for a short period then goes back to normal. Could you run a tracert and post it here? Link to comment Share on other sites More sharing options...
asiandiscovery Posted December 21, 2007 Author CID Share Posted December 21, 2007 Tracing route to 66.128.57.22 over a maximum of 30 hops 1 1 ms <1 ms <1 ms 192.168.1.1 2 5 ms 6 ms 6 ms 73.2.56.1 3 7 ms 7 ms 7 ms 68.85.251.229 4 9 ms 7 ms 12 ms 68.85.244.145 5 9 ms 9 ms 7 ms 68.85.244.149 6 14 ms 13 ms 14 ms COMCAST-IP.edge3.Dallas1.Level3.net [4.71.198.10] 7 41 ms 43 ms 42 ms xe-11-3-0.edge3.Dallas1.Level3.net [4.71.198.9] 8 42 ms 41 ms 44 ms ae-41-99.car1.Dallas1.Level3.net [4.68.19.195] 9 42 ms 46 ms 46 ms INTERNAP-NE.car1.Dallas1.Level3.net [209.246.152.246] 10 43 ms 161 ms 43 ms border3.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.191.83] 11 42 ms 45 ms 43 ms globalcon-9.border3.ext1.dal.pnap.net [63.251.32.102] 12 42 ms 44 ms 44 ms 66.128.57.22 Trace complete. This is a trace to a Dallas game server I play counter-strike on. Now 44-45, is not high ping by any means, but I usually get 15-20 ping on this server (at 6mbps, i assume it should be even faster with the speed boost). And when it comes to counter-strike, ping can make a huge difference. Also I should be pinging around 45-55 to LA servers, but im getting 75-85. Link to comment Share on other sites More sharing options...
coknuck Posted December 21, 2007 CID Share Posted December 21, 2007 Theres nothing wrong with that tracert. Wish it was mine. Tracing route to 66.128.57.22 over a maximum of 30 hops 1 14 ms 5 ms 6 ms 74-138-160-1.dhcp.insightbb.com [74.138.160.1] 2 7 ms 16 ms 7 ms 74-128-22-109.dhcp.insightbb.com [74.128.22.109] 3 13 ms 12 ms 11 ms 74-128-16-101.dhcp.insightbb.com [74.128.16.101] 4 18 ms 20 ms 27 ms 74.128.8.233 5 20 ms 28 ms 24 ms sl-gw25-atl-10-0.sprintlink.net [144.232.212.249] 6 37 ms 22 ms 50 ms sl-bb21-atl-5-0.sprintlink.net [144.232.22.13] 7 43 ms 21 ms 40 ms sl-crs1-atl-0-4-0-3.sprintlink.net [144.232.12.148] 8 40 ms 35 ms 56 ms sl-crs1-fw-0-12-0-2.sprintlink.net [144.232.18.147] 9 46 ms 47 ms 40 ms sl-st20-dal-12-0-0.sprintlink.net [144.232.9.193] 10 39 ms 40 ms 38 ms sl-internap-93948-0.sprintlink.net [144.228.250.126] 11 177 ms 252 ms 241 ms border3.tge4-1-bbnet2.ext1.dal.pnap.net [216.52.191.83] 12 39 ms 45 ms 40 ms globalcon-9.border3.ext1.dal.pnap.net [63.251.32.102] 13 43 ms 41 ms 42 ms 66.128.57.22 Trace complete. Link to comment Share on other sites More sharing options...
asiandiscovery Posted December 21, 2007 Author CID Share Posted December 21, 2007 Heres another trace to www.google.com Tracing route to www.l.google.com [72.14.253.99] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms 192.168.1.1 2 5 ms 5 ms 5 ms 73.2.56.1 3 10 ms 9 ms 10 ms 68.85.251.221 4 9 ms 9 ms 9 ms 68.85.244.149 5 17 ms 14 ms 15 ms COMCAST-IP.edge3.Dallas1.Level3.net [4.71.198.10] 6 44 ms 43 ms 43 ms xe-11-3-0.edge3.Dallas1.Level3.net [4.71.198.9] 7 45 ms 53 ms 54 ms vlan69.csw1.Dallas1.Level3.net [4.68.19.62] 8 44 ms 53 ms 54 ms ae-62-62.ebr2.Dallas1.Level3.net [4.69.136.137] 9 60 ms 69 ms 58 ms ae-2.ebr1.Denver1.Level3.net [4.69.132.105] 10 58 ms 68 ms 71 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38] 11 90 ms 90 ms 90 ms ae-2.ebr2.Seattle1.Level3.net [4.69.132.53] 12 89 ms 207 ms 83 ms ae-21-52.car1.Seattle1.Level3.net [4.68.105.34] 13 84 ms 86 ms 85 ms GOOGLE-INC.car1.Seattle1.Level3.net [4.79.104.74] 14 89 ms 89 ms 87 ms 66.249.95.208 15 92 ms 91 ms 90 ms 209.85.250.147 16 91 ms 91 ms 91 ms 216.239.46.198 17 98 ms 92 ms 105 ms 72.14.233.18 18 92 ms 92 ms 92 ms po-in-f99.google.com [72.14.253.99] Trace complete. Link to comment Share on other sites More sharing options...
coknuck Posted December 21, 2007 CID Share Posted December 21, 2007 Mine a little better on that one. Tracing route to google.com [64.233.187.99] over a maximum of 30 hops: 1 15 ms 7 ms 7 ms 74-138-160-1.dhcp.insightbb.com [74.138.160.1] 2 32 ms 11 ms 7 ms 74-128-22-109.dhcp.insightbb.com [74.128.22.109] 3 11 ms 13 ms 12 ms 74-128-16-101.dhcp.insightbb.com [74.128.16.101] 4 23 ms 26 ms 19 ms 74.128.8.233 5 41 ms 60 ms 66 ms sl-gw25-atl-10-0.sprintlink.net [144.232.212.249] 6 46 ms 41 ms 36 ms sl-bb21-atl-5-0.sprintlink.net [144.232.22.13] 7 23 ms 20 ms 19 ms sl-bb24-atl-9-0.sprintlink.net [144.232.12.30] 8 24 ms 22 ms 27 ms sl-st20-atl-0-0-0.sprintlink.net [144.232.20.115] 9 20 ms 37 ms 23 ms 144.223.47.234 10 20 ms 44 ms 21 ms 64.233.174.84 11 48 ms 40 ms 26 ms 72.14.236.19 12 31 ms 43 ms 26 ms 216.239.49.222 13 35 ms 24 ms 25 ms jc-in-f99.google.com [64.233.187.99] Trace complete. When I go through Level3 I have problems also. Link to comment Share on other sites More sharing options...
asiandiscovery Posted December 21, 2007 Author CID Share Posted December 21, 2007 If its not a routing problem, what other problem do you think could be causing me to be having 20-30 more ping than I usually get? Link to comment Share on other sites More sharing options...
coknuck Posted December 21, 2007 CID Share Posted December 21, 2007 When I go through Level3 backbone I have latency also. Link to comment Share on other sites More sharing options...
TimPawlak Posted December 21, 2007 CID Share Posted December 21, 2007 Tracing route to 66.128.57.22 over a maximum of 30 hops 1 9 ms 9 ms 6 ms 74-140-0-1.dhcp.insightbb.com [74.140.0.1] 2 7 ms 6 ms 8 ms 74-132-0-185.dhcp.insightbb.com [74.132.0.185] 3 10 ms 8 ms 6 ms 74.128.8.209 4 15 ms 15 ms 14 ms so-7-0-0.edge6.Chicago1.Level3.net [4.71.182.25] 5 21 ms 24 ms 28 ms ae-32-52.ebr2.Chicago1.Level3.net [4.68.101.62] 6 25 ms 16 ms 17 ms ae-68.ebr3.Chicago1.Level3.net [4.69.134.58] 7 51 ms 39 ms 50 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61] 8 40 ms 52 ms 56 ms ae-1-100.ebr1.Denver1.Level3.net [4.69.132.37] 9 50 ms 48 ms 54 ms ae-2.ebr2.Dallas1.Level3.net [4.69.132.106] 10 57 ms 54 ms * ae-92-92.csw4.Dallas1.Level3.net [4.69.136.150] 11 48 ms 49 ms 48 ms ae-41-99.car1.Dallas1.Level3.net [4.68.19.195] 12 50 ms 51 ms 50 ms INTERNAP-NE.car1.Dallas1.Level3.net [209.246.152 .246] 13 217 ms 210 ms 219 ms border3.tge3-1-bbnet1.ext1.dal.pnap.net [216.52. 191.22] 14 49 ms 55 ms 52 ms globalcon-9.border3.ext1.dal.pnap.net [63.251.32 .102] 15 48 ms 49 ms 47 ms 66.128.57.22 Trace complete. Tracing route to www.l.google.com [64.233.167.147] over a maximum of 30 hops: 1 8 ms 11 ms 12 ms 74-140-0-1.dhcp.insightbb.com [74.140.0.1] 2 9 ms 10 ms 7 ms 74-132-0-185.dhcp.insightbb.com [74.132.0.185] 3 7 ms 6 ms 7 ms 74.128.8.205 4 15 ms 16 ms 16 ms so-2-0-0.gar2.Chicago1.Level3.net [4.79.74.17] 5 15 ms 15 ms 39 ms ae-11-51.car1.Chicago1.Level3.net [4.68.101.2] 6 15 ms 17 ms 15 ms GOOGLE-INC.car1.Chicago1.Level3.net [4.79.208.18 ] 7 20 ms 17 ms 16 ms 66.249.94.133 8 16 ms 16 ms 21 ms 72.14.232.70 9 18 ms 16 ms 16 ms py-in-f147.google.com [64.233.167.147] Trace complete. Link to comment Share on other sites More sharing options...
Recommended Posts