sweeg
@comcast.net
| speed issues / ping spikes
okay, so i recently i've been getting speed drops and lag spikes pretty much constant everyday, worse though in the late afternoon and evenings. gaming is pretty much impossible because the delay is too long and makes movement very difficult. i'm using a motorola sb5120 router and a dlink di-604 router, wired too. heres a speedtest from speakeasy's site and a couple traceroutes:
Download Speed: 2631 kbps (328.9 KB/sec transfer rate)
Upload Speed: 655 kbps (81.9 KB/sec transfer rate)
1 * * * Request timed out.
2 297 ms 271 ms 319 ms GE-1-3-ur01.federalway.wa.seattle.comcast.net [68.86.98.217]
3 272 ms 308 ms * te-5-3-ur02.federalway.wa.seattle.comcast.net [68.86.96.34]
4 215 ms 264 ms 277 ms te-8-4-ar01.seattle.wa.seattle.comcast.net [68.86.96.38]
5 199 ms 198 ms 207 ms te-7-2-ar02.seattle.wa.seattle.comcast.net [68.86.96.174]
6 171 ms 151 ms 130 ms COMCAST-IP.car1.Seattle1.Level3.net [4.79.104.106]
7 202 ms 167 ms 202 ms te-3-2.car1.Seattle1.Level3.net [4.79.104.105]
8 229 ms 182 ms 224 ms ae-23-54.car3.Seattle1.Level3.net [4.68.105.100]
9 305 ms 274 ms 333 ms 4.79.106.26
10 291 ms 258 ms 272 ms ge-0-2-0.pat2.swp.yahoo.com [216.115.110.33]
11 363 ms 380 ms 310 ms so-1-0-0.pat1.pdx.yahoo.com [216.115.110.39]
12 360 ms 311 ms 349 ms so-3-0-0.pat1.sjc.yahoo.com [216.115.110.36]
13 248 ms 261 ms 250 ms g-0-0-0-p170.msr2.sp1.yahoo.com [216.115.107.81]
14 387 ms 369 ms 377 ms te-8-1.bas-a1.sp1.yahoo.com [209.131.32.17]
15 393 ms 423 ms 388 ms f1.www.vip.sp1.yahoo.com [209.131.36.158]
1 * * * Request timed out.
2 89 ms 68 ms 91 ms GE-1-3-ur01.federalway.wa.seattle.comcast.net [68.86.98.217]
3 107 ms 113 ms 130 ms te-5-3-ur02.federalway.wa.seattle.comcast.net [68.86.96.34]
4 92 ms 82 ms 91 ms te-8-4-ar01.seattle.wa.seattle.comcast.net [68.86.96.38]
5 64 ms 66 ms 58 ms 12.86.1.13
6 160 ms 184 ms 176 ms 12.127.6.189
7 147 ms 149 ms 146 ms tbr2.cgcil.ip.att.net [12.122.10.61]
8 138 ms 130 ms 165 ms cr1.cgcil.ip.att.net [12.122.17.217]
9 163 ms 155 ms 147 ms cr1.cl2oh.ip.att.net [12.122.2.206]
10 181 ms 189 ms 211 ms cr2.cl2oh.ip.att.net [12.122.2.126]
11 186 ms 171 ms 159 ms cr2.phlpa.ip.att.net [12.122.2.210]
12 166 ms 152 ms 169 ms tbr2.phlpa.ip.att.net [12.122.20.118]
13 136 ms 161 ms 148 ms gar2.phlpa.ip.att.net [12.123.137.205]
14 157 ms 139 ms 147 ms mdf1-gsr12-1-pos-6-0.nyc3.attens.net [12.122.255.126]
15 113 ms 105 ms 104 ms sccsbix11-1-4.attbi.com [63.240.64.34]
16 * * * Request timed out.
17 * * * Request timed out.
18 133 ms 118 ms 128 ms www.comcast.net [204.127.205.8]
downstream power - 2dBmV
signal to noise ratio - 37dB
upstream power - 52dBmV
any helps appreciated, thanks |
|
deblin
Dark Side of the Moon
Premium,MVM
join:2001-09-01
Middletown, DE
| Upstream power is slightly marginal, the downstream stats look great.
Looks to be a localized issue with your node.
On a trace to your 2nd hop, though, I do see some packet loss.
Definitely could be something weird going on for that area. Have you called support to report the issue?
--
Hello...is there anybody in there? |
|
EG
The wings of love
Premium
join:2006-11-18
Union, NJ
4 edits | reply to sweeg
Hmmmm.....
Pinging 68.86.98.217 with 32 bytes of data:
Reply from 68.86.98.217: bytes=32 time=130ms TTL=235
Reply from 68.86.98.217: bytes=32 time=107ms TTL=235
Reply from 68.86.98.217: bytes=32 time=107ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=108ms TTL=235
Reply from 68.86.98.217: bytes=32 time=105ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=105ms TTL=235
Reply from 68.86.98.217: bytes=32 time=108ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=104ms TTL=235
Reply from 68.86.98.217: bytes=32 time=105ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=105ms TTL=235
Reply from 68.86.98.217: bytes=32 time=107ms TTL=235
Reply from 68.86.98.217: bytes=32 time=104ms TTL=235
Reply from 68.86.98.217: bytes=32 time=107ms TTL=235
Reply from 68.86.98.217: bytes=32 time=105ms TTL=235
Reply from 68.86.98.217: bytes=32 time=105ms TTL=235
Reply from 68.86.98.217: bytes=32 time=108ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=106ms TTL=235
Reply from 68.86.98.217: bytes=32 time=107ms TTL=235
Reply from 68.86.98.217: bytes=32 time=108ms TTL=235
Reply from 68.86.98.217: bytes=32 time=109ms TTL=235
Ping statistics for 68.86.98.217:
Packets: Sent = 28, Received = 28, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 104ms, Maximum = 130ms, Average = 107ms
Control-C
^C
This is the first router that responds after the CMTS.
No loss from this small amount of pings, but slow response times..
Tracing route to GE-1-3-ur01.federalway.wa.seattle.comcast.net [68.86.98.217]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 19 ms 9 ms 9 ms ge-2-4-ur01.union.nj.panjde.comcast.net [68.86.2
20.145]
4 10 ms 9 ms 9 ms po-10-ur02.union.nj.panjde.comcast.net [68.86.20
9.238]
5 85 ms 10 ms 8 ms po-10-ur01.jerseycity.nj.panjde.comcast.net [68.
86.209.242]
6 10 ms 9 ms 10 ms po-10-ur02.jerseycity.nj.panjde.comcast.net [68.
86.209.246]
7 11 ms 9 ms 9 ms po-10-ur01.narlington.nj.panjde.comcast.net [68.
86.209.250]
8 13 ms 9 ms 10 ms po-10-ur02.narlington.nj.panjde.comcast.net [68.
86.158.178]
9 9 ms 9 ms 9 ms po-70-ar01.verona.nj.panjde.comcast.net [68.86.2
09.254]
10 11 ms 14 ms 12 ms te-2-3-ar01.plainfield.nj.panjde.comcast.net [68
.86.72.18]
11 12 ms 14 ms 29 ms te-4-1-cr01.newyork.ny.cbone.comcast.net [68.86.
72.17]
12 17 ms 16 ms 16 ms te-1-1-cr01.boston.ma.cbone.comcast.net [68.86.6
8.10]
13 39 ms 38 ms 39 ms te-9-1-cr01.cleveland.oh.cbone.comcast.net [68.8
6.68.14]
14 47 ms 47 ms 47 ms te-9-1-cr01.chicago.il.cbone.comcast.net [68.86.
68.22]
15 63 ms 62 ms 65 ms te-9-1-cr01.omaha.ne.cbone.comcast.net [68.86.68
.30]
16 74 ms 74 ms 73 ms te-9-1-cr01.denver.co.cbone.comcast.net [68.86.6
8.42]
17 84 ms 85 ms 83 ms te-9-1-cr01.ogden.ut.cbone.comcast.net [68.86.68
.46]
18 102 ms 100 ms 102 ms te-9-1-cr01.seattle.wa.cbone.comcast.net [68.86.
68.50]
19 * 104 ms 102 ms te-9-4-ar01.seattle.wa.seattle.comcast.net [68.8
6.72.66]
20 107 ms 105 ms 105 ms te-5-1-ur02.federalway.wa.seattle.comcast.net [6
8.86.96.37]
21 105 ms 108 ms 103 ms GE-1-3-ur01.federalway.wa.seattle.comcast.net [6
8.86.98.217]
Trace complete.
Maybe not too bad considering this is cross country.. |
|
d0nni3q
join:2006-11-05
Meadville, PA
1 edit | High ping times to the Comcast default gateway could indicate an overloaded node or some local problem. However, that router might just be making the ICMP packets a lower priority and responding slower. Doubtful, though since the upstream power level looks on the high side. I'd try replacing the splitter before the cable modem or making sure it is off of the first split.
As for pings across the US, 75-125ms is normal:
C:\>ping 68.86.98.217
Pinging 68.86.98.217 with 32 bytes of data:
Reply from 68.86.98.217: bytes=32 time=89ms TTL=242
Reply from 68.86.98.217: bytes=32 time=88ms TTL=242
Reply from 68.86.98.217: bytes=32 time=89ms TTL=242
Reply from 68.86.98.217: bytes=32 time=88ms TTL=242
Ping statistics for 68.86.98.217:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 88ms, Maximum = 89ms, Average = 88ms
That's from Pittsburgh, PA on FiOS.
DQ |
|
sweeg
@comcast.net
| reply to sweeg
thanks for the responses guys. weird thing about these slowdowns is they aren't always steadily lagging. it seems to go from time to time spiking up to 200+ for a few minutes but then only to 100+ for a few minutes, its always changing. anyways how would i go about changing the splitter? |
|
Quaoar
join:2004-08-11
Fort Collins, CO
| reply to sweeg
You upstream power of 52 dBmv is marginal to unacceptable. My local Comcast techs tell me that they want to see a max of 48, and somewhere around 40 if possible. The Docsis specs supposedly say that up to 55-58 is within bounds, but my techs tell me that is bogus, at least on my local network.
My comcast cable is elevated on poles, I have high winds up to 90 mph during spring and fall, and I go through this at least once per year when, at an upstream of 50-52 dBmv on my cable specs, both my HDTV and internet go into the dumper. The solution is to check each and every pole connection in my neighborhood. There is usually a loose or damaged pole connection somewhere.
Q |
|
StillLearn
Premium
join:2002-03-21
Streamwood, IL
 ·AT&T Midwest
| reply to sweeg
I can't explain your high times, even to your nearby routers. I will say that your pings and traces do not indicate a splitter or level problem. With those problems, you would lose packets (ignore those hops 16 and 17 with the ***).
It looks like things might be busy.
I would boot into safe mode with networking, and see if the latency drops. It is unlikely to do so. But if it does, it would indicate where to look. Alternatively, unplug your computer and plug in a friend's laptop for the same test. |
|
sweeg
@comcast.net | reply to sweeg
well i booted into safe mode and tried that but with the same results. i also tried another computer, yet the spiking was still present. anything else i should try before i call support? ill be sure to ask them about the upstream power level though. |
|
StillLearn
Premium
join:2002-03-21
Streamwood, IL
·AT&T Midwest
| said by sweeg :
well i booted into safe mode and tried that but with the same results. i also tried another computer, yet the spiking was still present. anything else i should try before i call support? ill be sure to ask them about the upstream power level though.
Since you are not registered, you don't register in the "Last" column. So I did not realize you had responded.
Since the problem was there in safe mode, that would tend to indicate the problem was probably not a worm on your machine.
The traces you posted do not show what I would call spiking. They show slowness.
Maybe you have already fixed your problem. If not,
try pinging your Comcast gateway with
ping -n 1000 yourGateway
where yourGateway represents the IP of your gateway.
Post only the summary -- not the whole thing.
The purpose is to see if there is a problem locally to you. You
can find your gateway by looking for the information in your router
screens. If you use Windows without a router, ipconfig will
tell you the IP of your gateway.
The thousand pings should take about 17 minutes.
If you do not run a home router/gateway, then you can run the
ipconfig command from a command window to find your Default
Gateway.
If you use a home router/gateway, you want to ping your Comcast
gateway rather than your home gateway. The IP of the Comcast
gateway will never be 192.168.*.*.
Your Comcast gateway address will be listed in your home router
pages somewhere. The upper two bytes/numbers will be the same as
your WAN address. The lowest byte/number will be a 1. The
byte/number next to the lowest will either be the same as for your
WAN, or it could be an even number just a little lower.
I also recommend the the standard version of Ping Plotter. |
|
Loki2012
join:2008-02-27
Federal Way, WA
| reply to sweeg
I have been having dropouts in Federal Way for 2 months now. Calls to Comcast follow the same pattern - at first everything is fine, then the Comcast associate will see my connection failing, then the whole neighborhood. I have been calling about twice a week during the dropouts (I work at home). Each associate responds to the issue by saying either there is maintenance being done or there is a "ticket" to get it fixed. The associate would not pass me on to someone who could do something. On Feb 25, I sent an email to Comcast complaining about the dropouts. I recieved an email and an automated call saying they actually fixed the problem. Today I havn't experinced any dropouts, however PingPlotter still showes problems in the Federal Way area (te-8-4-ar01.seattle.wa.seattle.comcast.net 68.86.96.38) The pings have been improving. Time will tell, I guess. |
|
