lordz
join:2003-01-02
San Francisco, CA | reply to lordz
Re: Attn: Frustrated users in Davis, CA please rea
Nevermind! Please lock this topic mods! It's directly related to this thread:
»Near 56k speeds in Davis, CA.
Seems to have been solved. Thanks =D |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC
 ·Verizon Online DSL
 ·Skype
| reply to lordz
100.1 is usually your modem.
Your first hop is horked. No need to test beyond that. Your modem stands between your router and your first hop.
So it's either the link between router and modem or between modem and first hop.
--
Robb Topolski -= http://www.funchords.com/ =- Hillsboro, Oregon USA
... Did you wake up grouchy this morning or did you let her sleep in? ... |
|
lordz
join:2003-01-02
San Francisco, CA | reply to lordz
1 to 2 ms rarely. my router has nothing to do with it. |
|
funchords
Hello
Premium,MVM
join:2001-03-11
Washington, DC | reply to lordz
Re: Attn: Frustrated users in Davis, CA please read
can you ping 192.168.100.1 ? |
|
lordz
join:2003-01-02
San Francisco, CA
 ·Comcast
|  I don't think I've ever seen such extreme latency in my life. I'd literally be better off with a 56k connection. I've called Comcast at least 3 times and have had 3 truck rolls already. They have NOT fixed the issue even after nightly calls. I can't really get 3mbit SBC DSL cuz it's not fast enough for the combined bandwidth that my housemates suck up.
These traceroute and speed tests are NOT fabricated:
Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 3107 ms * 3663 ms 10.184.16.1
3 4147 ms 3149 ms 2273 ms 12.244.16.33
4 * 2863 ms 2560 ms 12.244.69.197
5 * * 1516 ms 12.244.69.185
6 2350 ms 2549 ms 3872 ms 12.127.32.85
7 2620 ms * * idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * 935 ms www.comcast.net [204.127.195.15]
Trace complete.
Tracing route to comcast.net [204.127.195.15]
over a maximum of 30 hops:
1 2 ms 1 ms 2 ms 192.168.1.1
2 * 2685 ms 2428 ms 10.184.16.1
3 2779 ms 2155 ms * 12.244.16.33
4 * * 1852 ms 12.244.69.197
5 * 3603 ms * 12.244.69.185
6 * * * Request timed out.
7 1431 ms * 611 ms idf22-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
8 * 1581 ms 589 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
9 * * * Request timed out.
10 * * * Request timed out.
11 * 1883 ms * www.comcast.net [204.127.195.15]
12 * * 2235 ms www.comcast.net [204.127.195.15]
Trace complete.
From my *nix box:
Name :
traceroute to comcast.net (204.127.195.15), 30 hops max, 40 byte packets
1 10.184.16.1 (10.184.16.1) 3855.357 ms * 677.310 ms
2 * 12.244.16.33 (12.244.16.33) 399.034 ms 553.772 ms
3 12.244.69.197 (12.244.69.197) 4640.788 ms * 361.433 ms
4 * 12.244.69.185 (12.244.69.185) 1950.203 ms 624.737 ms
5 * 12.127.32.85 (12.127.32.85) 1895.197 ms 138.930 ms
6 idf22-gsr12-1-pos-6-0.rwc1.attens.net (12.122.255.222) 1809.926 ms 721.792 ms 2390.170 ms
7 rwcsbix11-1-6.attbi.com (63.241.85.238) 175.493 ms * *
8 * * * Request timed out.
9 * * * Request timed out.
10 www.comcast.net (204.127.195.15) 1120.733 ms 1754.549 ms 1888.249 ms
Trace complete
Speed test.
2005-11-08 02:43:09 EST: 12 / 5
Your download speed : 12 kbps or 1.6 KB/sec.
Your upload speed : 5 kbps or 0.7 KB/sec.
My signal is perfect. I know at least 3 of my friends who are Comcast subscribers in Davis are having the same problem. All of them have called in about this problem. Only at night does this happen....what do you guys think about this issue?
Why do they keep giving us the runaround? I get absolutely no replies in the official Comcast forum. I can never get in contact with an engineer regardless of what I do. |
|
