Hello everyone,
I've read the multiple posts about speed issues the past few days and it seems posters are from all over the country. If anyone has the same kind of speed problems in the Chicago area please feel free to reply here in case someone from Comcast is checking out the forum and can do something about it.
I'm on the Blast plan and I had up to 57Mbit down / 10 Mbit up for several months, probably more than a year, until the past few days. The connection is now intermittent, lots of drop-offs, lots of slow speeds, etc. I'm on a wired PC with a Motorola SB6141 modem and an Asus RT-N56U router.
When I run the speed tests at http://www.speedtest.net/ and http://speedtest.comcast.net/ all kinds of weird things are happening. The tests often stall during the transfer stage and some times they don't even complete. During the downstream or upstream phase, the connection speed may go up to 50/10 for a second or two but it will immediately drop to zero and then hover around a much lower speed level than 50/10.
Today it's been the worst yet:
http://www.speedtest.net/result/3214948736.png
I changed my Comcast IP yesterday in case that was a local switch issue, also did the modem and router power-cycle, PC reboots, DNS flush, etc, but there's no improvement.
This is definitely not an end user problem since so many are having the exact same issues with their connection. On my end, there haven't been any hardware or software changes to justify such a dramatic drop in connection speeds.
I hate to call tech support for this because I'll fall into the endless trap of people reading scripts for basic troubleshooting - when they can even read them, that is.
Come on Comcast, help, please!
=== added tracert and ping info ===
traceroute to comcast.net:
Tracing route to comcast.net [162.150.0.50]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms router.asus.com [192.168.1.1]
2 29 ms 29 ms 28 ms c-98-206-32-1.hsd1.il.comcast.net [98.206.32.1]
3 13 ms 31 ms 10 ms 68.86.118.73
4 17 ms 19 ms * te-0-6-0-3-ar01.elmhurst.il.chicago.comcast.net [68.87.210.57]
5 1833 ms 15 ms 15 ms he-0-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.94.45]
6 * 3921 ms 15 ms pos-0-3-0-0-ar01.northlake.il.ndcchgo.comcast.net [68.86.94.150]
7 16 ms 14 ms 28 ms te-0-3-0-0-ur03-d.northlake.il.ndcchgo.comcast.net [69.139.217.218]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 te-0-3-0-0-ur03-d.northlake.il.ndcchgo.comcast.net [69.139.217.218] reports: Destination net u
nreachable.
Trace complete.
======= start of ping results =======
C:\>ping -t www.comcast.net
Pinging a1526.dscg.akamai.net [23.62.97.112] with 32 bytes
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=17ms TTL=58
Request timed out.
Reply from 23.62.97.112: bytes=32 time=2864ms TTL=58
Reply from 23.62.97.112: bytes=32 time=29ms TTL=58
Reply from 23.62.97.112: bytes=32 time=2386ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Request timed out.
Reply from 23.62.97.112: bytes=32 time=2698ms TTL=58
Request timed out.
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=15ms TTL=58
Reply from 23.62.97.112: bytes=32 time=27ms TTL=58
Reply from 23.62.97.112: bytes=32 time=2806ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=2661ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=23ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=11ms TTL=58
Reply from 23.62.97.112: bytes=32 time=27ms TTL=58
Reply from 23.62.97.112: bytes=32 time=29ms TTL=58
Reply from 23.62.97.112: bytes=32 time=14ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=2795ms TTL=58
Reply from 23.62.97.112: bytes=32 time=16ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=15ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=44ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=3051ms TTL=58
Reply from 23.62.97.112: bytes=32 time=42ms TTL=58
Reply from 23.62.97.112: bytes=32 time=14ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=1572ms TTL=58
Reply from 23.62.97.112: bytes=32 time=30ms TTL=58
Reply from 23.62.97.112: bytes=32 time=428ms TTL=58
Reply from 23.62.97.112: bytes=32 time=29ms TTL=58
Reply from 23.62.97.112: bytes=32 time=13ms TTL=58
Reply from 23.62.97.112: bytes=32 time=12ms TTL=58
Reply from 23.62.97.112: bytes=32 time=15ms TTL=58
Reply from 23.62.97.112: bytes=32 time=2830ms TTL=58
Reply from 23.62.97.112: bytes=32 time=14ms TTL=58
Reply from 23.62.97.112: bytes=32 time=14ms TTL=58
Ping statistics for 23.62.97.112:
Packets: Sent = 54, Received = 51, Lost = 3 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 3051ms, Average = 486ms
Control-C
^C
==== End of ping resuts ===