dnt408
join:2005-10-07
San Jose, CA
| [Connectivity] Major Slow Down in San Jose, CA? Anyone else in the 95121 area getting major slow down? So slow that I would consider it unuseable. My dial up would be faster. It's been happening since Oct 3, 4, 5, and 6th so far. Basically it only occurs after around 8:30pm or so. Usually doesn't work until late at night. Up until 2am (then I gotta get to bed) Never had this problem before. I've tried resetting the router and modem via power cycling but after I connect it still doesn't work as fast. In the morning when I wake up around 9am... I just need to power cycle it again it works normally and very fast. Any problem/upgrade happening around the evergreen/silver creek area? thanks | |
|
 carlinniss
join:2003-05-12 | Re: [Connectivity] Major Slow Down in San Jose, CA Same thing was happening in Sacramento.
I suspect it's something they're working on that they are being hush hush about, probably speed upgrades. | |
|
dnt408
join:2005-10-07
San Jose, CA
| Okay the problem is still happening for the last two nights. I get the feeling that it won't fix on it's own. Probably should call them out now right. IT can't take that long "upgrade" the system does it?
C:\Documents and Settings\User>tracert www.google.com
Tracing route to www.l.google.com [64.233.161.147]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 * * 11 ms 68.87.197.217
4 * 13 ms 14 ms 68.87.192.37
5 12 ms 14 ms * 68.87.195.34
6 16 ms 12 ms 18 ms 12.124.35.65
7 * 29 ms 14 ms tbr1-p010201.sffca.ip.att.net [12.123.13.150]
8 12 ms 14 ms 13 ms 12.122.80.66
9 * 14 ms 13 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
10 16 ms 55 ms 15 ms ae-1-53.bbr1.SanJose1.Level3.net [4.68.123.65]
11 * 88 ms 84 ms as-3-0.bbr2.Washington1.Level3.net [4.68.128.206
]
12 138 ms 133 ms * ae-12-53.car2.Washington1.Level3.net [4.68.121.8
3]
13 100 ms 85 ms 85 ms 4.79.228.26
14 87 ms 89 ms 88 ms 216.239.47.149
15 106 ms 88 ms 90 ms 216.239.48.198
16 107 ms 92 ms 108 ms 64.233.161.147
Trace complete. | |
|
 | dnt408
join:2005-10-07
San Jose, CA
| Re: [Connectivity] Major Slow Down in San Jose, CA Still going slow and the only thing tech could tell me was to disconnect my modem.... Probably in another 1 hour or so I won't be able to surf at all. Will probably have to use my neighbor's DSL tonight again.
Tracing route to www.comcast.com [164.109.28.3]
over a maximum of 30 hops:
1 2 ms 2 ms 2 ms 192.168.1.1
2 * * * Request timed out.
3 * 12 ms * 68.87.197.217
4 15 ms 13 ms 13 ms 68.87.192.37
5 30 ms 14 ms 13 ms 68.87.195.46
6 * * 46 ms 12.127.32.33
7 34 ms * 17 ms tbr2-p013701.sffca.ip.att.net [12.123.13.177]
8 48 ms 46 ms 68 ms ggr2-p390.sffca.ip.att.net [12.123.13.194]
9 17 ms 41 ms 36 ms att-gw.ashburn.eli.net [192.205.32.74]
10 23 ms 23 ms 18 ms 0.so-0-2-0.XL2.SCL2.ALTER.NEt [152.63.57.50]
11 139 ms * * 0.so-6-0-0.XL1.DCA6.ALTER.NET [152.63.38.70]
12 81 ms 118 ms 78 ms 0.so-6-0-0.GW6.DCA6.ALTER.NET [152.63.41.221]
13 152 ms * 155 ms digex-gw.customer.alter.net [157.130.214.102]
14 118 ms 82 ms 81 ms vlan39.dca2a-fdisa-sw1-msfc1.netsrv.digex.net [1
64.109.3.149]
15 * 109 ms * 164.109.31.219
16 118 ms 82 ms * 164.109.28.3
17 * 83 ms 98 ms 164.109.28.3
Trace complete.
Downstream Value
Frequency 705000000 Hz Locked
Signal to Noise Ratio 29 dB
Power Level -1 dBmV
Upstream Value
Channel ID 3
Frequency 32000000 Hz Ranged
Power Level 24 dBmV | |
|
XTCBoY2K
join:2001-02-14
Santa Clara, CA | The problem is the second hop. My second hop has been down for several weeks now. | |
|
| NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
 ·Pacific Bell - SBC
1 edit | Re: [Connectivity] Major Slow Down in San Jose, CAsaid by XTCBoY2K  :The problem is the second hop. My second hop has been down for several weeks now. Do you mean the hop that fails? Like everybody else's trace routes show? I am told that it's your CMTS, and that is is configured to not respond to ICMP packets; no ping.
10/21/05 01:36:12 Slow traceroute Ikuko
Trace Ikuko (67.171.201.211) ...
192.168.102.1 RTT: 0ms TTL: 64 (Chihiro ok)
192.168.0.1 RTT: 41ms TTL:170 (Suzuka ok)
71.132.15.254 RTT: 28ms TTL:170 (adsl-71-132-15-254.dsl.sntc01.pacbell.net ok)
63.203.51.65 RTT: 27ms TTL:170 (dist1-vlan60.sntc01.pbi.net ok)
64.161.1.145 RTT: 28ms TTL:170 (bb1-g8-0-1.sntcca.sbcglobal.net ok)
151.164.40.170 RTT: 27ms TTL:170 (bb2-p6-0.sntc01.sbcglobal.net ok)
151.164.241.197 RTT: 27ms TTL:170 (core2-p6-2.crscca.sbcglobal.net ok)
151.164.40.62 RTT: 55ms TTL:170 (bb1-p8-0.crscca.sbcglobal.net ok)
151.164.242.230 RTT: 27ms TTL:170 (ex2-p14-0.eqsjca.sbcglobal.net ok)
151.164.191.201 RTT: 28ms TTL:170 (ex1-p9-0.eqsjca.sbcglobal.net ok)
144.223.242.81 RTT: 41ms TTL:170 (sl-st20-sj-0-0.sprintlink.net ok)
144.232.9.67 RTT: 27ms TTL:170 (sl-st21-sj-1-0.sprintlink.net ok)
144.232.9.206 RTT: 55ms TTL:170 (No rDNS)
12.123.13.193 RTT: 83ms TTL:170 (tbr2-p012201.sffca.ip.att.net bogus rDNS: host not found [authoritative])
12.122.12.114 RTT: 55ms TTL:170 (tbr1-cb10.st6wa.ip.att.net bogus rDNS: host not found [authoritative])
12.123.44.145 RTT: 55ms TTL:170 (gar3-p360.st6wa.ip.att.net bogus rDNS: host not found [authoritative])
12.119.199.22 RTT: 69ms TTL:170 (No rDNS)
68.87.216.6 RTT: 55ms TTL:170 (No rDNS)
68.87.216.57 RTT: 55ms TTL:170 (No rDNS)
* * * failed
67.171.201.211 RTT: 68ms TTL: 41 (Ikuko ok)
I noticed quite a few are posting tracer routes going through Level3. I'd kind of take those with a grain of salt, given the peering wars going on.
I also wonder what will go on with the AT&T routers. With SBC poised to buy AT&T, how long will any peering and transit agreements hold?
Comcast may be adding capacity to take up any slack from the AT&T buyout; who knows? I also have no idea about the affect of Comcast lighting up large swaths of the south S.F. Bay Area. Until about nine months ago, Comcast was not available in my neighborhood. That was when they "lit up" the line behind my house. Black sheath with red stripe; fiber on the poles? Could they have added customers in west San José faster than they added capacity, and are now playing "catch up"?
Just rambling. I was suffering serious DSL lag, and decreased down sync rate; worried that the copper was going bad, and I'd maybe have to go over to Comcast. Now that the cable maintenance guy fixed the open on the "ring" side of the loop, all is well again. Took them 48 hours to fix it, though, because of the "protocol". Service techs have to wave their wands over pole connections and cross-connect boxes before they bring in cable maintenance.
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
|
koan-sc
@comcast.net
| I'm having horrible slowdown in Santa Cruz:
Tracing route to www.l.google.com [64.233.161.147
over a maximum of 30 hops:
1 * * * Request timed out
2 174 ms 316 ms 414 ms 68.87.198.149
3 278 ms 471 ms 335 ms 68.87.192.45
4 308 ms 60 ms 134 ms 68.87.192.41
5 210 ms 287 ms 337 ms 68.87.192.37
6 115 ms 289 ms 20 ms 68.87.195.38
7 402 ms 272 ms 645 ms 12.117.240.5
8 363 ms 360 ms 411 ms tbr1011001.sffca.
9 249 ms 457 ms 170 ms 12.122.80.66
10 377 ms 176 ms 189 ms so-8-1.car3.SanJo
11 443 ms 750 ms 431 ms ae-1-53.bbr1.SanJ
12 471 ms 400 ms 532 ms as-3-0.bbr2.NewYo
13 625 ms 595 ms 436 ms ae-21-54.car1.New
14 516 ms 462 ms 663 ms 4.78.164.70
15 445 ms 268 ms 343 ms 64.233.175.105
16 550 ms 340 ms 640 ms 66.249.94.235
17 692 ms 507 ms 732 ms 66.249.95.123
18 514 ms 330 ms 446 ms 216.239.48.198
19 324 ms 220 ms 413 ms 64.233.161.147
It's been terrible for three weeks. I finally got a tech to come out and then the problem miraculously cleared up for the one day they were scheduled to check on it, so they found no issue. Then it went back to being like this. | |
|
| ecko4o8
join:2003-12-08
San Jose, CA | Re: [Connectivity] Major Slow Down in San Jose, CA yeah .. my ping sucks playing counterstrike.. usually its 15-32 ping now its 150+ ping.. i know its not the server because a fellow player with comcast was 400 ping with me when i entered the room..
WTH is up? | |
|
| | ecko4o8
join:2003-12-08
San Jose, CA | Re: [Connectivity] Major Slow Down in San Jose, CA  | |
|
| | | ziggie216
join:2001-04-19 | Re: [Connectivity] Major Slow Down in San Jose, CA it's 10/12/05 10:41pm
wtf is going on with comcast... my upspeed is ok, around 385, but my down speed is around 900 - 1500 kbs | |
|
| | | | ecko4o8
join:2003-12-08
San Jose, CA | Re: [Connectivity] Major Slow Down in San Jose, CA bump because i want an answer  | |
|
randalla
join:2004-04-15
South San Francisco, CA
1 edit | I don't think is just San Jose. I'm up north in So. San Francisco and last night I was getting close to 2000 Kbps for my downloads. They must be doing some work at night that causes the slowdown.
Found this today from the Comcast forums. Jason posted this on the 11th.
"At this time, the only areas remaining to receive the speed upgrade are in the Northern California area, where there is still some network upgrades ocurring. Teams are still working to complete the Northern CA area upgrade and you should see the new speeds soon. We will update the list above when your area has been updated." | |
|
dka69
@comcast.net | I am feeling the same pain here in West San Jose. Sucks ass if you ask me. I am fine with 4 - 5MB's. Everytime they do a speed upgrade I have to suffer with performance hits. Just give me a stable circuit. | |
|
dubb
join:2005-10-14
San Jose, CA
| I'm in San Jose as well, 95117, and I've been experiencing these same problems you guys are describing since around mid-August. My bandwidth is very inconsistent, and it does seem to get worse at night... Also my cable tv and internet will just go out intermitently. These problems seem to be happening after 4pm. I'm getting sick and tired of this... I was getting about 30ms ping on counterstrike and now I get 100+ ping constantly, and I've peaked out as much as a 1 second ping... I'm interested to find out what is causing this... | |
|
randalla
join:2004-04-15
South San Francisco, CA
| Again,
Found this today from the Comcast forums. Jason posted this on the 11th.
"At this time, the only areas remaining to receive the speed upgrade are in the Northern California area, where there is still some network upgrades ocurring. Teams are still working to complete the Northern CA area upgrade and you should see the new speeds soon. We will update the list above when your area has been updated." | |
|
dubb
join:2005-10-14
San Jose, CA | I think that's just comcast's way of trying to retain as many customers as they can... I'm sure they're hearing a high volume of complaints daily. My bet is that comcast doesn't finish their upgrades for another few months... | |
|
| 
dadkins
Can you do Blu?
Premium,MVM
join:2003-09-26
Hercules, CA
1 edit | Re: [Connectivity] Major Slow Down in San Jose, CA? Ah, the end of Summer Autumn Upgrade... | |
|
randalla
join:2004-04-15
South San Francisco, CA | "Ah, the end of Summer Autumn Upgrade..."
Northern California is the only area that hasn't been upgraded. At this rate, it will be the end of the year. | |
|
|
dadkins
Can you do Blu?
Premium,MVM
join:2003-09-26
Hercules, CA
 ·Comcast
| Re: [Connectivity] Major Slow Down in San Jose, CA? said by randalla :"Ah, the end of Summer Autumn Upgrade..." Northern California is the only area that hasn't been upgraded. At this rate, it will be the end of the year. I have the end of year... do I hear 1st Quarter 2006? 
--
Think outside the Fox... Opera | |
|
| | dhavasy
join:2002-05-14
San Jose, CA
| Re: [Connectivity] Major Slow Down in San Jose, CA? I'm in San Jose as well and over the last week i've been getting this same problem starting around 8pm every night and it lasts until i go to sleep. And then in the morning it's back to normal. Unfortunately i don't even get to use the internet much until 7:00 or 8:00 which im sure is the case with lots of people. I think a router somewhere is getting hammered during primetime. Here's my trace.. the slowdown always occurs on my 8th hop in that block of ips so that is definitely the problem area.
Target Name: www.comcast.net
IP: 204.127.195.15
Date/Time: 10/17/2005 9:52:43 PM
1 * * * [-]
2 9 ms 9 ms 8 ms [68.87.197.249]
3 7 ms 8 ms 23 ms [68.87.192.53]
4 8 ms 8 ms 8 ms [68.87.192.49]
5 7 ms 9 ms 9 ms [68.87.192.41]
6 26 ms 13 ms 10 ms [68.87.192.37]
7 13 ms 10 ms 25 ms [68.87.195.50]
8 172 ms 125 ms 97 ms [12.124.35.65]
9 299 ms 282 ms 282 ms tbr2-p033602.sffca.ip.att.net [12.123.13.154]
10 213 ms 215 ms 229 ms [12.123.13.178]
11 339 ms 308 ms 297 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.255.218]
12 278 ms 281 ms 274 ms rwcsbix11-1-6.attbi.com [63.241.85.238]
13 * * * [-]
14 * * * [-]
15 318 ms 331 ms 329 ms www.comcast.net [204.127.195.15]
When i use to have dsl through pac bell way back when, the techs online here would actually help fix the problem. Does that still happen or do i just get a tech out to my place? The tech of course will come out during the day when all is fine so i'm really not sure if that's gonna help  | |
|
lucidgroove
join:2002-12-31
San Jose, CA
| 
Ping Plotter - Lokk at the Packet Loss!! |
C:\Documents and Settings\Administrator>tracert www.google.com
Tracing route to www.l.google.com [64.233.161.147]
over a maximum of 30 hops:
1 * * * Request timed out.
2 12 ms 16 ms 53 ms 68.87.197.253
3 55 ms 16 ms 15 ms 68.87.192.53
4 19 ms 16 ms 15 ms 68.87.192.49
5 15 ms 25 ms 16 ms 68.87.192.41
6 58 ms 17 ms 35 ms 68.87.192.37
7 23 ms 20 ms 18 ms 68.87.195.50
8 132 ms 130 ms 90 ms 12.117.240.5
9 20 ms 17 ms 19 ms tbr1011001.sffca.ip.att.net [12.122.82.74]
10 31 ms 36 ms 45 ms 12.122.80.66
11 78 ms 88 ms 67 ms att-gw.sea.level3.net [192.205.32.206]
12 91 ms 74 ms 79 ms ae-1-55.bbr1.SanJose1.Level3.net [4.68.123.129]
13 151 ms 158 ms 158 ms as-3-0.bbr2.NewYork1.Level3.net [64.159.1.134]
14 162 ms 164 ms 194 ms ae-21-56.car1.NewYork1.Level3.net [4.68.97.180]
15 119 ms 138 ms 139 ms 4.78.164.70
16 120 ms 135 ms 124 ms 64.233.175.105
17 108 ms 117 ms 90 ms 66.249.94.235
18 97 ms 91 ms 99 ms 66.249.95.123
19 93 ms 93 ms 100 ms 216.239.48.198
20 100 ms 97 ms 100 ms 216.239.48.190
21 105 ms 93 ms 114 ms 64.233.161.147
Trace complete.
Not Happy | |
|
| DJTEEL
join:2005-10-25
Garland, TX
| Re: [Connectivity] Major Slow Down in San Jose, CA? i'm in garland texas(the dallas area) and comcast has been very slow for the past week at least. comcast.net loads so slowly my former dialup ip could do as well..also trying to open dallasnews.com to read the paper?? i might as well subscribe to the daily paper..it would be less aggrivating than waiting for their site to load. it's really annoying to me cuz i gave up netzero 3 weeks ago for comcast high speed..and now this cr&pola..this had better get better or i'll be saying goodbye to comcast.
it seems like the pages that load the slowest are pages that contain graphics,which i could understand if i was using dialup. i certainly didn't expect comcast to be a problem in that area. | |
|
randalla
join:2004-04-15
South San Francisco, CA
1 edit | Look at this tracert at 8:58 PM from South San Francisco.
This really stinks.
tracert www.comcast.com
Tracing route to www.comcast.com [164.109.28.3]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 22 ms 8 ms 9 ms 68.87.196.21
4 11 ms 8 ms 9 ms 68.87.192.6
5 9 ms 10 ms 32 ms 68.87.195.42
6 150 ms 166 ms 163 ms 12.117.240.17
7 180 ms 178 ms 177 ms tbr2032701.sffca.ip.att.net [12.122.82.2]
8 219 ms 224 ms 220 ms 12.122.81.137
9 190 ms 190 ms 194 ms att-gw.ashburn.eli.net [192.205.32.74]
10 202 ms 201 ms 227 ms 0.so-2-0-0.XL2.SCL2.ALTER.NET [152.63.57.102]
11 303 ms 299 ms 291 ms 0.so-6-0-0.XL2.DCA6.ALTER.NET [152.63.38.74]
12 196 ms 198 ms 189 ms 0.so-7-0-0.GW6.DCA6.ALTER.NET [152.63.41.225]
13 274 ms 274 ms 276 ms digex-gw.customer.alter.net [157.130.214.102]
14 268 ms 273 ms 266 ms vlan39.dca2a-fdisa-sw1-msfc1.netsrv.digex.net [1
64.109.3.149]
15 220 ms 224 ms 243 ms 164.109.31.219
16 232 ms 236 ms 235 ms 164.109.28.3
Trace complete.
And speed tests during day I get 4.6 to 5 Mbps. At night 1.2 to 1.6 Mbps. | |
|
dka69
@comcast.net
| My connection has been sucking for the last two weeks. Calls to comcast are always answered by a very polite person. Unfortunately the technician is not helpful. Escalating the issue generally falls on deaf ears. They must know something is going on but are informed not to admit anything. Sad..
tracert -d www.yahoo.com
Tracing route to www.yahoo.akadns.net [66.94.230.36]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 16 ms 27 ms 68.87.198.1
4 14 ms 11 ms 12 ms 68.87.192.53
5 13 ms 10 ms 27 ms 68.87.192.49
6 13 ms 8 ms 11 ms 68.87.192.41
7 12 ms 12 ms 11 ms 68.87.192.37
8 11 ms 30 ms 26 ms 68.87.195.46
9 198 ms 192 ms 199 ms 12.127.32.33
10 225 ms 236 ms 244 ms 12.123.13.177
11 242 ms 242 ms 236 ms 12.122.80.57
12 198 ms 198 ms 203 ms 192.205.32.206
13 338 ms 316 ms 317 ms 4.68.123.139
14 243 ms 254 ms 253 ms 64.152.69.30
15 188 ms 159 ms 147 ms 66.218.82.219
16 294 ms 269 ms 261 ms 66.94.230.36
Trace complete. | |
|
| mandms7
join:2005-10-19
Livermore, CA | Re: [Connectivity] Major Slow Down in San Jose, CA I'm in Livermore, CA and my speeds suck just as bad. Haven't tried it in the morning, but every night for the past week or so has been extremely slow. | |
|
| dadur
join:2005-04-07
| Same problem here near the SF/Daly City border (94132):
C:\>tracert www.comcast.net
Tracing route to www.comcast.net [204.127.195.15]
over a maximum of 30 hops:
1 1 ms 1 ms * 192.168.111.1
2 * * * Request timed out.
3 29 ms 18 ms 29 ms 68.87.197.193
4 11 ms 12 ms 24 ms 68.87.192.213
5 14 ms 22 ms 15 ms 68.87.192.205
6 8 ms 51 ms 14 ms 68.87.192.201
7 46 ms 26 ms 25 ms 68.87.192.197
8 11 ms 32 ms 12 ms 68.87.195.58
9 328 ms 289 ms 283 ms 12.117.240.17 <= Problem starts here
10 256 ms 294 ms 247 ms tbr2032701.sffca.ip.att.net [12.122.82.2]
11 250 ms 214 ms 201 ms 12.123.13.178
12 303 ms 303 ms 301 ms idf22-gsr12-1-pos-7-0.rwc1.attens.net [12.122.255.218]
13 285 ms 312 ms 279 ms rwcsbix11-1-4.attbi.com [63.241.85.234]
14 * * * Request timed out.
15 312 ms 288 ms 323 ms www.comcast.net [204.127.195.15]
Trace complete.
There are already two threads on the Comcast support forums about this. | |
|
| | tweekah
join:2004-06-02
San Leandro, CA
| Re: [Connectivity] Major Slow Down in San Jose, CA Horrible, every night for the last few days.
Tracing route to www.l.google.com [64.233.187.99]
over a maximum of 30 hops:
1 * * * Request timed out.
2 14 ms 8 ms 11 ms 68.87.196.129
3 10 ms 12 ms 10 ms 68.87.192.86
4 * 11 ms 9 ms 68.87.192.90
5 * 13 ms 16 ms 68.87.195.22
6 234 ms 207 ms 224 ms 12.117.240.13
7 93 ms 91 ms 85 ms tbr1011001.sffca.ip.att.net [12.122.82.74]
8 * 208 ms 201 ms 12.123.12.57
9 298 ms ^C | |
|
| | |
Britboy1
@comcast.net
|  Re: [Connectivity] Major Slow Down in San Jose, CA
tracert www.comcast.net
Tracing route to www.comcast.net [204.127.195.15]
over a maximum of 30 hops:
1 7 ms 7 ms 5 ms 10.150.144.1
2 17 ms 7 ms 7 ms 68.87.197.37
3 8 ms 7 ms 7 ms 68.87.192.105
4 7 ms 7 ms 12 ms 68.87.199.110
5 7 ms 7 ms 7 ms 68.87.192.97
6 9 ms 10 ms 23 ms 68.87.192.93
7 9 ms 9 ms 9 ms 68.87.195.46
8 344 ms 343 ms 341 ms 12.117.240.5
9 170 ms 171 ms 189 ms [12.122.82.2]
10 300 ms 307 ms 316 ms 12.123.13.178
11 206 ms 208 ms 219 ms [12.122.25
5.218]
12 276 ms 275 ms 286 ms [63.241.85.238]
13 * * * Request timed out.
14 * * * Request timed out.
15 338 ms 348 ms 340 ms [204.127.195.15] | |
|
dhavasy
join:2002-05-14
San Jose, CA
| Well it's pretty obvious we're all having the exact same problem and we can all pinpoint it to the hop that starts with 12.xxx. Is this a bad router or something that is getting abused at night during primetime?
Now that we've pinpointed the problem area, how do we actually get comcast to do something? I had a tech out today who was nice but not much help. He said he'd report the problem and hopefully in the next 10 days they'd monitor it after hours. But then even once they've found the problem he's not sure what they can do about it. He would not give me anyone else to call so i'm basically stuck just hoping they notice it.
Have the rest of you reported the problem? Any ideas how we can get some response from them?
Dave | |
|
| The Way Out
join:2003-01-20 | Re: [Connectivity] Major Slow Down in San Jose, CA Comcast is over capacity in the Bay Area. Users are getting speed increases, but Comcast isn't upgrading their uplinks at the same rate. You're experiencing a virtual traffic jam during peak usage hours. | |
|
dubb
join:2005-10-14
San Jose, CA | Ironic how we live in the high tech capitol of the world... I would've thought silicon valley might have fiber optic lines with amazing broadband speeds, needless to say - I'm highly disappointed. Thinking of dropping Comcast to go back with SBC... | |
|
blacey
join:2000-10-26
San Mateo, CA
| 
WAN Traffic | 
Ping latency to Comcast.net |
| |
|
|
comcast can suck my
@comcast.net
| Re: [Connectivity] Major Slow Down in San Jose, CA haha most of u people have what max of 3-4 weeks with these unbearable speeds from comcast?....listen to this 4 fuckin months wow i call comcast have 4 techs within 3 weeks and 1 of them says i can't find anything i'll give u another modem...doesnt solve the problem, the second one says i can't find anything wrong you want a modem change and i told them to give me their motorola sb5120 and still nothing 3rd tech tells me that it has something to do with my apt cable lines...and im liek fuck it let them say what they want to but i ask him tho how is it possible that when i call comcast customer support they tell me that they see the ping times on my modem and have proof yet when techs come they say they cannot go any further or else they will have to do a surcharge of 49.99 because they have no proof and tell me that comcast techs and comcast customer service are two different parts of the company...only word that comes to mind is WOW. so i was thinking recently how could i have such a retard to listen to that bullshit if a cable line was bad in the apt why do i get great ping in the morning while im in class so i call them back for a escalate in my problem from a regular tech to a line tech who tests the line instead of my equipment. now some lady from comcast calls me while im in class and leaves a voicemail saying they didnt send a line tech because it is a problem that has to do with where i live and the cable lines in my apt. btw i live on 4th and william area code 95112. | |
|
dhavasy
join:2002-05-14
San Jose, CA
| Yah i really fear that this problem will never be solved because comcast is just too big and cannot handle individual problems anymore.
I'm ordering DSL and testing it for a month to see if it's better because i really dont even know how to approach the comcast issue.
Are there ANY comcast techs that browse these forums who can give us advice here??? | |
|
|
See 7 replies to this post |
|
wrenchmonkey
Premium
join:2002-05-04
Sacramento, CA | SOS here in East Sac too. Comcrap sucks. | |
|
| NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| Re: [Connectivity] Major Slow Down in San Jose, CA said by wrenchmonkey :SOS here in East Sac too. Comcrap sucks. Aren't you about 50 miles east of East Oakland? 95 miles northeast of East San José?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
|
| | tweekah
join:2004-06-02
San Leandro, CA
1 edit | Re: [Connectivity] Major Slow Down in San Jose, CA SBC takeover of ATT shouldn't have anything to do with this. Comcast already tookover ATT's broadband infrastructure awhile ago. Comcast tried feeding the upgrade to Northern California but recalled it immediately (I saw my modem's config). Why? They can't handle it. Yes, I may be ignorant, but I can still speculate! | |
|
| | | NormanS
Premium,MVM
join:2001-02-14
San Jose, CA
·Pacific Bell - SBC
| Re: [Connectivity] Major Slow Down in San Jose, CA said by tweekah :SBC takeover of ATT shouldn't have anything to do with this. Comcast already tookover ATT's broadband infrastructure awhile ago. Comcast tried feeding the upgrade to Northern California but recalled it immediately (I saw my modem's config). Why? They can't handle it. Yes, I may be ignorant, but I can still speculate! It won't have anything to do with the immediate problem. Like you, I was speculating. AFAIK, the AT&T core routers were not a part of the AT&T Broadband Internet infrastructure, and remain under AT&T control.
To continue to speculate, though, maybe a regulatory restriction will be placed on the SBC buyout; the AT&T core routers would add to SBC's significant place as a backbone provider. Maybe the routers will be required to be sold off to Comcast, who would then have tighter control over them. This should be a "good thing" for Comcast, as it would give them their own backbone, as well as giving their engineers the ability to tweak the routers for improved performance.
OTOH, if they stay with SBC, then any performance improvements would be on the SBC network engineers. Perhaps tweaking their performance would have a lower priority; as long as the packets actually reach their destination, why expend effort to reduce lag for a competitor?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum | |
|
| |
wrenchmonkey
Premium
join:2002-05-04
Sacramento, CA
2 edits | Edited so I don't hurt someones sensitive feelings. | |
|
dka69
@comcast.net
| I just wanted to post an updated. It appears things are getting better with Comcast's network. Unsure if the good times will continue but I'm crossing my fingers...
Tracing route to www.l.google.com [66.102.7.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 12 ms 13 ms 28 ms 68.87.198.1
4 11 ms 9 ms 10 ms 68.87.192.53
5 12 ms 12 ms 45 ms 68.87.192.49
6 9 ms 9 ms 13 ms 68.87.192.41
7 13 ms 14 ms 16 ms 68.87.192.37
8 31 ms 48 ms 11 ms 68.87.195.62
9 46 ms 28 ms 32 ms 12.124.35.65
10 14 ms 14 ms 17 ms 12.123.13.154
11 14 ms 27 ms 18 ms 12.122.80.57
12 18 ms 17 ms 17 ms 192.205.32.206
13 36 ms 19 ms 15 ms 4.68.123.112
14 35 ms 27 ms 40 ms 209.247.202.218
15 26 ms 63 ms 27 ms 216.239.47.146
16 24 ms 24 ms 26 ms 216.239.49.150
17 25 ms 32 ms 23 ms 66.102.7.99 | |
|
| tweekah
join:2004-06-02
San Leandro, CA | Re: [Connectivity] Major Slow Down in San Jose, CA Network has been much nicer this week. Keeping fingers crossed. | |
|
|
|
|
