pbrubaker
join:2006-03-08
Playa Del Rey, CA
| [Speed] West LA - High latency (4:00pm - 1:00am)
So this has been going on (on and off) for months now. I first started seeing this problem in July of 2006 and its been intermittent since then. When my local area makes the hop to the first ATT router the latency jumps. During the morning and middle afternoon it's fine, but come 4:00pm it starts jumping up. I've tried to call Comcast, and use their online support but I'm tired of being treated like I dont know what's wrong. They offer to send out a tech, who more often knows less about networks than I do. My neighbors are all having this trouble (obviously) and the one guy has been calling to complain for at least a month. It's so bad that I can barely use my connection for what I love to use it for the most. Game.
What do we do?
Here is a traceroute from my Linux box to comcast.net. Notice the 10th hop? That's been the problem router for as long as I can remember.
traceroute: Warning: comcast.net has multiple addresses; using 63.240.76.72
traceroute to comcast.net (63.240.76.72), 30 hops max, 38 byte packets
1 10.235.0.1 (10.235.0.1) 10.389 ms 18.289 ms 9.213 ms
2 68.86.112.109 (68.86.112.109) 9.701 ms 7.897 ms 7.121 ms
3 68.87.208.25 (68.87.208.25) 8.133 ms 7.601 ms 18.898 ms
4 68.87.208.21 (68.87.208.21) 121.186 ms 82.515 ms 80.441 ms
5 68.87.208.17 (68.87.208.17) 8.323 ms 11.631 ms 9.604 ms
6 68.87.208.13 (68.87.208.13) 11.376 ms 11.069 ms 9.841 ms
7 68.87.208.9 (68.87.208.9) 23.408 ms 14.053 ms 6.590 ms
8 68.87.208.169 (68.87.208.169) 9.849 ms 7.859 ms 9.773 ms
9 12.127.137.21 (12.127.137.21) 74.179 ms 67.194 ms 63.871 ms
10 gbr5-p90.la2ca.ip.att.net (12.123.28.193) 132.925 ms 133.339 ms 131.768 ms
MPLS Label=1267 CoS=5 TTL=1 S=0
11 tbr2-p013501.la2ca.ip.att.net (12.122.11.153) 140.989 ms 127.739 ms 127.501 ms
MPLS Label=32686 CoS=5 TTL=1 S=0
12 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 160.373 ms 160.651 ms 167.995 ms
MPLS Label=31640 CoS=5 TTL=1 S=0
13 tbr2-cl7.cgcil.ip.att.net (12.122.10.45) 163.785 ms 167.115 ms 164.763 ms
MPLS Label=32322 CoS=5 TTL=1 S=0
14 tbr1-cl22.cgcil.ip.att.net (12.122.9.133) 174.576 ms 167.295 ms 166.679 ms
MPLS Label=31207 CoS=5 TTL=1 S=0
15 tbr1-cl14.n54ny.ip.att.net (12.122.10.1) 138.014 ms 137.892 ms 134.980 ms
MPLS Label=31337 CoS=5 TTL=1 S=0 |
|
multiword
join:2006-03-07
Atlanta, GA
| Seeing the same issue in Atlanta. There is no packet loss or low ping times but packets take _too_ long to arrive. In some cases so long the handshake has timed out. I've experienced that going to some sites (like google) work, while others (like yahoo) don't. In our area the snippet to the bad set of routers looks like:
6 68.86.106.158 (68.86.106.158) 7.293 ms 8.271 ms 7.862 ms
7 12.124.64.73 (12.124.64.73) 9.455 ms 9.383 ms 7.906 ms
8 gbr5-p53.attga.ip.att.net (12.123.20.170) 25.075 ms 24.956 ms 25.744 ms
9 tbr2-cl17.wswdc.ip.att.net (12.122.10.69) 24.877 ms 23.418 ms 23.111 ms
The next snippets look have better connectivity:
6 68.86.106.158 (68.86.106.158) 8.670 ms 10.039 ms 7.975 ms
7 12.124.64.73 (12.124.64.73) 17.120 ms 9.627 ms 9.585 ms
8 12.123.20.174 (12.123.20.174) 29.561 ms 11.958 ms 11.067 ms
9 br1-a3120s6.attga.ip.att.net (12.123.20.205) 91.881 ms 41.031 ms 229.104 ms
6 68.86.106.158 (68.86.106.158) 13.128 ms 9.398 ms 17.441 ms
7 12.124.64.21 (12.124.64.21) 9.632 ms 9.421 ms 10.746 ms
8 gbr5-p53.attga.ip.att.net (12.123.20.170) 26.352 ms 25.626 ms 25.868 ms
9 tbr2-cl17.wswdc.ip.att.net (12.122.10.69) 27.706 ms 25.056 ms 26.489 ms
So I suspect its something weird when 12.124.64.73 routes through 12.123.20.170. |
|
pikester
join:2005-10-05
Playa Del Rey, CA
| reply to pbrubaker
Shout out to my next door neighbor Pete who started this thread. Yes, Comcast truly does suck on all accounts. I've spent the last five months fighting with them to fix my connection issues (i.e. rebooting my cable modem up to 6 times a day). Now that I have that issue finally resolved, I can start looking at this particular issue at hand.
When using Vonage last night on some phone calls (around 8:30 to 9:00 pm), the outgoing portions of the calls were extensively breaking up. I did a speed test to see that I was only getting 2Mb down, but 350Kb up (download is slow, but shouldn't be causing the problems). I then did a traceroute and came across this:
2 10.235.0.1 (10.235.0.1) 100.111 ms 38.383 ms 64.658 ms
3 68.86.112.109 (68.86.112.109) 138.297 ms 117.762 ms 79.465 ms
4 68.87.208.25 (68.87.208.25) 100.819 ms 166.518 ms 95.038 ms
5 68.87.208.21 (68.87.208.21) 32.593 ms 77.916 ms 26.990 ms
6 68.87.208.17 (68.87.208.17) 168.860 ms 42.656 ms 195.070 ms
7 68.87.208.13 (68.87.208.13) 98.220 ms 57.559 ms 204.400 ms
8 68.87.208.9 (68.87.208.9) 31.699 ms 101.254 ms 120.502 ms
9 68.87.208.173 (68.87.208.173) 305.085 ms 16.015 ms 64.074 ms
10 12.127.137.21 (12.127.137.21) 67.352 ms 24.722 ms 188.578 ms
11 12.123.199.214 (12.123.199.214) 241.199 ms 206.312 ms 278.759 ms
12 tbr2-p013601.la2ca.ip.att.net (12.122.11.157) 83.489 ms 140.316 ms 111.673 ms
13 tbr2-cl21.sl9mo.ip.att.net (12.122.10.13) 291.557 ms 94.150 ms 145.894 ms
14 tbr2-cl7.cgcil.ip.att.net (12.122.10.45) 179.842 ms 170.566 ms 128.321 ms
15 tbr1-cl22.cgcil.ip.att.net (12.122.9.133) 270.062 ms 125.509 ms 96.430 ms
Basically, this is the culprit that Pete sees, just a bit more exagerated last night. |
|
phrider
join:1999-12-17
Los Angeles, CA
| reply to pbrubaker
Nine days from Calif source to Mid-Wilshire Comcast IP | 
Hourly detail from a Calif source to Mid-Wilshire Comcast IP |
For my connection, it seems to start a little before 9pm PST for all days except Friday night and Saturday night.
Here is a plot of pings for the past 9 days, along with hourly detail for the last 1.5 days. Times in the charts are EST. |
|
Tristan9669
join:2004-08-07
Beverly Hills, CA
| reply to pbrubaker
I'm in West LA and I dont seem to have any problems, its 4:38pm right now.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Tristan>tracert comcast.net
Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:
1 6 ms 5 ms 7 ms 10.232.200.1
2 6 ms 6 ms 6 ms 68.87.210.69
3 6 ms 6 ms 10 ms 68.87.208.13
4 6 ms 6 ms 7 ms 68.87.208.9
5 6 ms 6 ms 6 ms 68.87.208.173
6 7 ms 5 ms 6 ms 12.127.137.21
7 13 ms 6 ms 7 ms 12.123.199.214
8 18 ms 8 ms 8 ms tbr2-p013601.la2ca.ip.att.net [12.122.11.157]
9 7 ms 6 ms 7 ms 12.123.222.93
10 14 ms 15 ms 13 ms idf26-gsr12-1-pos-7-0.rwc1.attens.net [12.122.25
5.142]
11 15 ms 15 ms 15 ms rwcsbix12-3-1.attbi.com [63.241.85.242]
12 14 ms 13 ms 14 ms 192.168.64.6
13 15 ms 15 ms 15 ms 192.168.64.77
14 16 ms 15 ms 16 ms www.comcast.net [204.127.195.15]
Trace complete. |
|
pbrubaker
join:2006-03-08
Playa Del Rey, CA
| Hey Tristan,
Where are you located? I have friends up in Santa Monica that dont have any problems. Also I ran a 24hr test the other night and it peaked at 600ms around 9:00-9:30 PM. I'm going to post the image tonight. Can you try it at around then?
My download speeds arent as bad as pikester's but I've noticed that I'm back to 4000/300 as a max. We were part of the 600/768 upgrade that went through a couple of months ago but it appears that it's been reverted in some areas. See:
»forums.comcast.net/thread.jspa?t···tstart=0
--P |
|
Tristan9669
join:2004-08-07
Beverly Hills, CA
4 edits | reply to pbrubaker
Im near Pico and La Cienega, btw Santa Monica doesn't have Comcast, they have Adelphia. I was on last night around 9PM and I didn't notice any lagg.
I remember when comcast upgraded around spring last year and I had really low bandwidth around 1-2Mbps during peak hoours around four pm to midnight. But I haven't noticed and problems since then. |
|
pbrubaker
join:2006-03-08
Playa Del Rey, CA
| Yeah, that's near where my friends are. Tonight the pings are great. In the mid teens to most of the game servers I play on. But then again it is 3:40 in the morning.
Speed is still horrible. I just ran a test and I got these results.
dslreports.com speed test result on 2006-03-11 06:37:40 EST:
3737 / 358
Your download speed : 3737 kbps or 467.1 KB/sec.
That is 18.6% worse than an average user on comcast.net
Your upload speed : 358 kbps or 44.7 KB/sec.
That is 7.7% worse than an average user on comcast.net
I guess it's time to complain again.
--P |
|
Tristan9669
join:2004-08-07
Beverly Hills, CA | reply to pbrubaker
Good Luck, when I had speed problems, comcast didn't do sh!t about it. They just said there are no problems but they can send out someone to check out the problem then they might charge $50 if its your fault. |
|
knoxvillenew
join:2005-11-05
Knoxville, TN
| Ha yeah they just send out a contractor who knows pretty much nothing to goof around your house and then do whatever he can to get out the door. Then when you call back with the same problem they offer to send another one out, "just to make sure, but if he determines its your end with the problem its 50$". They will string you along forever. They should pay YOU for the hassle and lies you have to put up with from their CS department. Chances are they are over subscribed like alot of other places in the country. Ditch them for something, anything else, they strung me along for 3 months until I finally had enough. |
|
