Anon429075
@comcast.net
| reply to mrweirdo
Schedule an appointment! Please!
The first-level CSR I talked to said they'd only consider this an outage (presumably meaning they'd take it seriously) if enough people requested a technician to come to their house. He also mentioned he'd heard talk of horrible ping times to CA. So please do us all a favor and schedule a tech if you're having latency issues. And have your friends do the same. Then if it clears up, just call 1-888-266-2278 and cancel the tech.
I'm in Mountain View (NorCal). Traceroutes to anywhere outside comcast space look something like this, clearly showing the problem is inside comcast.
Tracing route to cnn.com [64.236.24.20]
over a maximum of 30 hops:
1 * * * Request timed out.
2 11 ms 11 ms 12 ms 12.244.25.145
3 8 ms 10 ms 12 ms 12.244.67.17
4 525 ms 558 ms 540 ms 12.244.72.206
5 544 ms 560 ms 560 ms gbr1-p70.sffca.ip.att.net [12.123.13.58]
6 562 ms 559 ms 564 ms tbr2-p012401.sffca.ip.att.net [12.122.11.81]
7 550 ms 558 ms 555 ms 12.122.80.57
8 562 ms 563 ms 561 ms pop1-sjg-P3-3.atdn.net [66.185.150.89]
9 562 ms 570 ms 604 ms bb2-sjg-P0-0.atdn.net [66.185.150.82]
10 645 ms 598 ms 592 ms bb2-las-P7-0.atdn.net [66.185.152.22]
11 565 ms 557 ms 562 ms bb1-las-P2-0.atdn.net [66.185.152.24]
12 569 ms 582 ms 577 ms bb1-pho-P7-0.atdn.net [66.185.152.27]
13 568 ms 565 ms 582 ms bb2-pho-P1-0.atdn.net [66.185.152.37]
14 606 ms 606 ms 613 ms bb2-hou-P6-0.atdn.net [66.185.152.106]
15 606 ms 612 ms 623 ms bb1-hou-P1-0.atdn.net [66.185.152.152]
16 638 ms 621 ms 622 ms bb1-atm-P7-0.atdn.net [66.185.152.184]
17 623 ms 614 ms 616 ms pop1-atl-P4-0.atdn.net [66.185.136.17]
... etc |
|
mrweirdo
join:2004-09-12
Roseville, CA
| reply to iceman420
Re: [Connectivity] NorCal high pings, slow speeds
Bad here in Roseville too I've noticed it on and off since yesterday. It gets beter in the overnight hours.
Tracing route to google.com [216.239.37.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.10
2 9 ms 7 ms 9 ms 10.184.128.1
3 8 ms 11 ms 11 ms 12.244.16.145
4 8 ms 7 ms 19 ms 12.244.69.185
5 22 ms 17 ms 16 ms 12.127.32.85
6 17 ms 15 ms 19 ms tbr1-p012301.sffca.ip.att.net [12.123.13.173]
7 27 ms 20 ms 18 ms ggr2-p300.sffca.ip.att.net [12.123.13.190]
8 32 ms 18 ms 20 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
9 16 ms 16 ms 16 ms ae-1-51.bbr1.SanJose1.Level3.net [4.68.123.1]
10 92 ms 92 ms 85 ms as-3-0.bbr2.Washington1.Level3.net [4.68.128.206
]
11 86 ms 89 ms 86 ms ae-21-54.car1.Washington1.Level3.net [4.68.121.1
14]
12 85 ms 83 ms 87 ms 4.79.228.26
13 88 ms 91 ms 92 ms 216.239.46.34
14 88 ms 88 ms 92 ms 64.233.174.130
15 90 ms 91 ms 90 ms 216.239.48.110
16 106 ms 89 ms 99 ms 216.239.37.99
Trace complete.
Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.10
2 25 ms 15 ms 9 ms 10.184.128.1
3 12 ms 8 ms 10 ms 12.244.16.145
4 10 ms 7 ms 10 ms 12.244.69.153
5 15 ms 16 ms 14 ms 12.127.32.85
6 80 ms 91 ms 80 ms tbr2-p013701.sffca.ip.att.net [12.123.13.177]
7 107 ms 80 ms 82 ms tbr1-cl2.sl9mo.ip.att.net [12.122.10.41]
8 84 ms 86 ms 83 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
9 77 ms 80 ms 82 ms gar1-p300.ascva.ip.att.net [12.123.8.49]
10 * * * Request timed out.
11 76 ms 83 ms 86 ms ae1.p400.msr1.dcn.yahoo.com [216.115.96.181]
12 82 ms 83 ms 75 ms ge10-2.bas1-m.dcn.yahoo.com [216.109.120.203]
13 81 ms 132 ms 79 ms w2.rc.vip.dcn.yahoo.com [216.109.112.135]
Trace complete. |
|
