 CUBS_FANNext Year Again..
join:2005-04-28
Chicago, IL
kudos:1
 ·Vonage
 ·Comcast
·magicjack.com
| [Connectivity] North Side Chicago/ What's going on?? Pages crawling all the sudden.. Anyone else in the N/W Side of Chicago?
Tracing route to a1526.dscg.akamai.net [157.238.74.202]
over a maximum of 30 hops:
1 42 ms 3 ms 12 ms MY-WIRELESS [192.168.1.1]
2 59 ms 57 ms 42 ms 98.213.160.1
3 78 ms 13 ms 12 ms te-2-5-ur02.chicago201.il.chicago.comcast.net [68.86.115.25]
4 19 ms 21 ms 26 ms te-0-6-0-5-ar01.area4.il.chicago.comcast.net [68.87.211.61]
5 44 ms 21 ms 60 ms he-3-5-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.95.237]
6 2358 ms 3208 ms 2643 ms ix-8-0-3-0.tcore1.CT8-Chicago.as6453.net [64.86.137.25]
7 * 3538 ms 2459 ms 64.86.78.18
8 1768 ms 1859 ms 2866 ms ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221]
9 2152 ms 2379 ms 2469 ms 157.238.74.202
Trace complete. |
|
|
|
CUBS_FANNext Year Again..
join:2005-04-28
Chicago, IL
kudos:1 Reviews:
·Vonage
·Comcast
·magicjack.com
| Big swing of latency.
Pinging 64.86.137.29 with 32 bytes of data:
Reply from 64.86.137.29: bytes=32 time=980ms TTL=59
Reply from 64.86.137.29: bytes=32 time=692ms TTL=59
Reply from 64.86.137.29: bytes=32 time=1054ms TTL=59
Reply from 64.86.137.29: bytes=32 time=503ms TTL=59
Reply from 64.86.137.29: bytes=32 time=579ms TTL=59
Reply from 64.86.137.29: bytes=32 time=919ms TTL=59
Reply from 64.86.137.29: bytes=32 time=745ms TTL=59
Reply from 64.86.137.29: bytes=32 time=369ms TTL=59
Reply from 64.86.137.29: bytes=32 time=938ms TTL=59
Reply from 64.86.137.29: bytes=32 time=616ms TTL=59
Reply from 64.86.137.29: bytes=32 time=427ms TTL=59
Reply from 64.86.137.29: bytes=32 time=27ms TTL=59
Reply from 64.86.137.29: bytes=32 time=42ms TTL=59
Reply from 64.86.137.29: bytes=32 time=23ms TTL=59
Reply from 64.86.137.29: bytes=32 time=17ms TTL=59
Reply from 64.86.137.29: bytes=32 time=61ms TTL=59
Reply from 64.86.137.29: bytes=32 time=84ms TTL=59
Reply from 64.86.137.29: bytes=32 time=496ms TTL=59
Reply from 64.86.137.29: bytes=32 time=724ms TTL=59
Reply from 64.86.137.29: bytes=32 time=808ms TTL=59
Reply from 64.86.137.29: bytes=32 time=1653ms TTL=59
Reply from 64.86.137.29: bytes=32 time=1062ms TTL=59
Reply from 64.86.137.29: bytes=32 time=494ms TTL=59
Reply from 64.86.137.29: bytes=32 time=559ms TTL=59
Reply from 64.86.137.29: bytes=32 time=536ms TTL=59
Reply from 64.86.137.29: bytes=32 time=373ms TTL=59
Reply from 64.86.137.29: bytes=32 time=418ms TTL=59
Ping statistics for 64.86.137.29:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 1653ms, Average = 562ms |
|
 pflogBueller? Bueller?Premium,MVM
join:2001-09-01
El Dorado Hills, CA
kudos:3 | reply to CUBS_FAN
Looks localized, but it would help to see your signal levels.
--
"I drank what?" -Socrates |
|
Reviews:
·Comcast
| reply to CUBS_FAN
The 6th hop in your trace is out of Comcast's network.
Things look fine from my end, too, but there was a nice jitter at the 2nd hop (out of the gateway)
Tracing route to a1526.dscg.akamai.net [205.234.225.210]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms *-static.hfc.comcastbusiness.net
2 907 ms 100 ms 31 ms *
3 55 ms 11 ms 10 ms te-0-2-0-4-sur03.elmhurst.il.chicago.comcast.net [68.86.116.13]
4 19 ms 23 ms 23 ms te-2-8-0-9-ar01.area4.il.chicago.comcast.net [69.139.185.189]
5 20 ms 23 ms 23 ms he-3-5-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.95.237]
6 13 ms 13 ms 14 ms be-12-pe03.350ecermak.il.ibone.comcast.net [68.86.84.190]
7 23 ms 22 ms 22 ms 173.167.57.126
8 15 ms 15 ms 13 ms unknown.scnet.net [205.234.225.210]
Trace complete.
Adding a second trace to the IP yours resolved to:
Tracing route to 157.238.74.202 over a maximum of 30 hops
1 1 ms 1 ms 1 ms *-static.hfc.comcastbusiness.net
2 47 ms 29 ms 10 ms *
3 10 ms 10 ms 8 ms te-0-2-0-4-sur03.elmhurst.il.chicago.comcast.net [68.86.116.13]
4 17 ms 23 ms 35 ms te-2-8-0-13-ar01.area4.il.chicago.comcast.net [69.139.185.205]
5 25 ms 21 ms 23 ms he-3-8-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.49]
6 13 ms 13 ms 13 ms ix-2-3-0-0.tcore1.CT8-Chicago.as6453.net [64.86.137.41]
7 15 ms 44 ms 17 ms 64.86.78.18
8 15 ms 14 ms 15 ms ae-8.r05.chcgil09.us.bb.gin.ntt.net [129.250.4.221]
9 24 ms 27 ms 23 ms 157.238.74.202 |
|
| reply to CUBS_FAN
Re: [Connectivity] North Side Chicago/ What's going on??I'm in the NW suburbs and I started having issues last night. I can restart my modem, but it takes a long time to connect. I was about to call Comcast support, but thought I'd check here to see if others are having an issue.
After I'm connected, I can access stuff, but it's terribly slow.
Here's my traceroute:
Tracing route to www.google.com [74.125.225.211]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms unknown [10.10.10.1]
2 1612 ms 1458 ms 1450 ms 98.228.152.1
3 1979 ms 1923 ms 1770 ms te-9-2-ur03.algonquin.il.chicago.comcast.net [69.139.173.81]
4 1489 ms 1207 ms 1171 ms te-8-4-ur04.algonquin.il.chicago.comcast.net [68.86.189.234]
5 1281 ms 1347 ms 1523 ms te-0-3-0-0-ar01.area4.il.chicago.comcast.net [68.87.230.41]
6 1464 ms 1815 ms 1665 ms he-3-5-0-0-cr01.350ecermak.il.ibone.comcast.net[68.86.95.237]
7 1892 ms 1817 ms 2018 ms pos-0-13-0-0-pe01.350ecermak.il.ibone.comcast.net [68.86.87.250]
8 1217 ms 1048 ms 906 ms 66.208.228.202
9 1164 ms 1031 ms 1559 ms 209.85.254.120
10 1776 ms 1772 ms 1791 ms 72.14.237.133
11 1734 ms 1983 ms 1999 ms 72.14.232.141
12 1168 ms 1249 ms 1129 ms 72.14.239.51
13 1150 ms 1219 ms 1668 ms 216.239.46.151
14 1879 ms 1984 ms 1894 ms 209.85.251.111
15 1857 ms 1644 ms 1906 ms den03s06-in-f19.1e100.net [74.125.225.211]
Here's a screenshot with signal info from my SB6120
»i.imgur.com/fQh0E.png |
|
CUBS_FANNext Year Again..
join:2005-04-28
Chicago, IL
kudos:1 Reviews:
·Vonage
·Comcast
·magicjack.com
| that's right at your Node or so it seems. Do you live in an area with a lot of apartment buildings? Might be crowding?
Tracing route to 98.228.152.1 over a maximum of 30 hops
1 13 ms 3 ms 12 ms MY-WIRELESS [192.168.1.1]
2 51 ms 27 ms 27 ms 98.213.160.1
3 27 ms 16 ms 18 ms te-2-5-ur02.chicago201.il.chicago.comcast.net [68.86.115.25]
4 17 ms 25 ms 13 ms te-0-6-0-5-ar01.area4.il.chicago.comcast.net [68.87.211.61]
5 49 ms 16 ms 20 ms te-3-1-ur04.algonquin.il.chicago.comcast.net [68.87.230.42]
6 18 ms 18 ms 14 ms 98.228.152.1
Trace complete. |
|
 EGThe wings of lovePremium
join:2006-11-18
Union, NJ
kudos:9 | reply to MWags83
Was anything on your LAN /home network accessing the internet at that time ? Is the wireless radio enabled ? If so, do you have it locked down ? |
|
CUBS_FANNext Year Again..
join:2005-04-28
Chicago, IL
kudos:1 Reviews:
·Vonage
·Comcast
·magicjack.com
| said by EG:Was anything on your LAN /home network accessing the internet at that time ? Is the wireless radio enabled ? If so, do you have it locked down ?
I noticed a lot of random times where the connection seems slow and packet loss was occurring. I changed the MAC address on the Wireless Router and rebooted the cable modem and now got a new IP address. I think I was holding on to the same IP address for over a year now. The latency is a lot lower now.
I have a secured regular connection and a open guest account that requires a password when opening a internet browser. The router setup page is password protected as well.
Before : Ping statistics for 64.86.137.29:
Packets: Sent = 27, Received = 27, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 1653ms, Average = 562ms
After: Ping statistics for 64.86.137.29:
Packets: Sent = 279, Received = 279, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 63ms, Average = 18ms |
|
| I've been having issues too... It seems as though they just cleared up though. I am getting path pings to google with 10-15% packet loss and 200-600ms pings. I went as far as downloading TCPView and akamai funneled 300 MB of garbage to my PC in under 30 minutes. It was ridiculous! I haven't been able to do anything for days.
I called comcast twice, they stated my connection was fine... I agreed with them. My connection was fine... it is their connection that is broke! |
|
