iceman420
join:2005-04-18
Salinas, CA
| [Connectivity] NorCal high pings, slow speeds
Is comcast having another outtage in my area or something?? This lagg started at 10am or around there thats when i started to use pc. WHAT IS COMCAST DOING TO FIX THIS???? Its been going on forever now, i dropped sbc for comcast maybe it was a bad idea
Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 11 ms 9 ms 9 ms 12.244.98.113
4 12 ms 16 ms 12 ms 12.244.67.201
5 15 ms 51 ms 13 ms 12.244.72.210
6 382 ms 382 ms 363 ms gbr5-p40.sffca.ip.att.net [12.122.2.254]
7 373 ms 410 ms 452 ms tbr2-p013501.sffca.ip.att.net [12.122.11.89]
8 397 ms 401 ms 396 ms tbr1-cl2.sl9mo.ip.att.net [12.122.10.41]
9 434 ms 382 ms 394 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
10 364 ms 361 ms 365 ms gar1-p300.ascva.ip.att.net [12.123.8.49]
11 * * * Request timed out.
12 358 ms 358 ms 377 ms vlan220-msr2.dcn.yahoo.com [216.115.96.165]
13 410 ms 376 ms 364 ms ge5-2.bas1-m.dcn.yahoo.com [216.109.120.151]
14 390 ms 413 ms 367 ms w2.rc.vip.dcn.yahoo.com [216.109.112.135]
Trace complete.
OHH 6MBPS AT ITS BEST !!!! GO COMCAST!
This especially sucks for ppl that game.
2005-08-02 14:50:15 EST: 891 / 631
Your download speed : 913402 bps, or 891 kbps.
A 111.4 KB/sec transfer rate.
Your upload speed : 646311 bps, or 631 kbps. |
|
osxboi
join:2005-03-04
Fort Lauderdale, FL
clubs:
| I'm no defender of Comcast. In fact, I'm just about ready to dump them and go back to more reliable Bellsouth DSL. However, it looks to me like the bottleneck in your traceroute is AT&T's network, not Comcast. And, it's the specific way you're being routed that's causing the difficulty. Here's my traceroute (from south Florida) to the same Yahoo IP:
traceroute to 216.109.112.135 (216.109.112.135), 64 hops max, 60 byte packets
1 c-65-34-24X-XX.hsd1.fl.comcast.net (65.34.24X.XX) 2.689 ms 1.359 ms 1.657 ms
2 10.246.32.1 (10.246.32.1) 11.644 ms 11.318 ms 15.163 ms
3 66.176.1.37 (66.176.1.37) 11.964 ms 10.916 ms 11.361 ms
4 66.176.1.93 (66.176.1.93) 12.398 ms 13.622 ms 13.420 ms
5 66.176.1.117 (66.176.1.117) 13.676 ms 13.536 ms 13.755 ms
6 12.119.94.21 (12.119.94.21) 13.693 ms 13.550 ms 14.513 ms
7 gbr4-p100.ormfl.ip.att.net (12.123.218.66) 40.308 ms 52.438 ms 40.012 ms
8 12.122.12.121 (12.122.12.121) 40.566 ms 42.395 ms 42.981 ms
9 tbr2-cl1.wswdc.ip.att.net (12.122.10.69) 41.396 ms 41.315 ms 42.054 ms
10 gar1-p390.ascva.ip.att.net (12.123.8.53) 42.239 ms 41.045 ms 38.244 ms
11 * * *
12 ae1.p400.msr1.dcn.yahoo.com (216.115.96.181) 47.623 ms vlan220-msr2.dcn.yahoo.com (216.115.96.165) 41.568 ms vlan200-msr1.dcn.yahoo.com (216.115.96.161) 41.944 ms
13 ge5-2.bas2-m.dcn.yahoo.com (216.109.120.199) 39.974 ms ge9-3.bas2-m.dcn.yahoo.com (216.109.120.155) 40.493 ms ge5-2.bas2-m.dcn.yahoo.com (216.109.120.199) 40.359 ms
14 w2.rc.vip.dcn.yahoo.com (216.109.112.135) 41.166 ms 39.882 ms 41.310 ms |
|
n1000
@comcast.net
|  reply to iceman420
I have been having the same problems with comcast recently as well. (norcal here too)
A tech came over and said that they were having problems with one of there "servers" near san francisco, and although this problem has been on and off for a couple months now, they have done seemingly nothing to fix this... |
|
chintoo874
join:2004-01-30
Fremont, CA
| reply to iceman420
Heres my tracert to yahoo.. i live in fremont, CA...
notice the problem is after the 6th Hop:
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 10.150.112.1
3 10 ms 10 ms 9 ms 12.244.101.33
4 10 ms 9 ms 10 ms 12.244.67.165
5 10 ms 25 ms 12 ms 12.244.67.14
6 513 ms 513 ms 506 ms 12.244.72.206
7 508 ms 501 ms 512 ms gbr2-p50.sffca.ip.att.net [12.123.13.62]
8 498 ms 501 ms 495 ms tbr2-p012701.sffca.ip.att.net [12.122.11.85]
9 489 ms 498 ms 491 ms ggr2-p390.sffca.ip.att.net [12.123.13.194]
10 505 ms 509 ms 527 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
11 506 ms 506 ms 506 ms ge-10-2.ipcolo3.SanJose1.Level3.net [4.68.123.13
9]
12 502 ms 502 ms 512 ms unknown.Level3.net [64.152.69.30]
13 501 ms 504 ms 499 ms UNKNOWN-66-218-82-217.yahoo.com [66.218.82.217]
14 487 ms 494 ms 502 ms p21.www.scd.yahoo.com [66.94.230.52]
Trace complete.
anyone else have this issue? |
|
wildstyle
join:2002-09-24
Salinas, CA
1 edit | reply to iceman420
same here in salinas ca.
Tracing route to p21.www.scd.yahoo.com [66.94.230.52]
over a maximum of 30 hops:
1 * * * Request timed out.
2 24 ms 9 ms 9 ms 12.244.98.97
3 12 ms 16 ms 13 ms 12.244.67.201
4 487 ms 495 ms 496 ms 12.244.72.206
5 504 ms 503 ms 505 ms gbr1-p70.sffca.ip.att.net [12.123.13.58]
6 497 ms 536 ms 524 ms tbr2-p012401.sffca.ip.att.net [12.122.11.81]
7 498 ms 491 ms 524 ms ggr2-p390.sffca.ip.att.net [12.123.13.194]
8 492 ms 493 ms 481 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
9 483 ms 480 ms 491 ms ge-11-2.ipcolo3.SanJose1.Level3.net [4.68.123.17
1]
10 490 ms 497 ms 503 ms unknown.Level3.net [64.152.69.30]
11 520 ms 527 ms 525 ms UNKNOWN-66-218-82-217.yahoo.com [66.218.82.217]
12 503 ms 497 ms 492 ms p21.www.scd.yahoo.com [66.94.230.52]
Trace complete. |
|
kevini
Premium
join:2002-08-26
Fremont, CA | Same for me going from work to my router, 500ms+ Looks like an AT&T problem in SF. Lets hope they are on a backup route while they upgrade the main route!!
It does only seem be be effecting south of SF. Dadkins in Hercules was working fine |
|
mrweirdo
join:2004-09-12
Roseville, CA
| reply to iceman420
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. |
|
Anon429075
@comcast.net
| 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 |
|
xkred27
join:2005-04-02
Kenwood, CA
| reply to iceman420
Re: [Connectivity] NorCal high pings, slow speeds
NFG here in Sonoma County, too. But as noted earlier, don't my results implicate ATT, not Comcast? Peter.
Tracing route to yahoo.com [216.109.112.135]
over a maximum of 30 hops:
1 11 ms 9 ms 23 ms 10.152.210.1
2 23 ms 11 ms 10 ms 12.244.24.49
3 13 ms 11 ms 24 ms 12.244.3.10
4 11 ms 13 ms 13 ms 12.244.67.97
5 17 ms 19 ms 19 ms 12.244.67.93
6 18 ms 11 ms 18 ms 12.124.35.65
7 683 ms 695 ms 702 ms gbr6-p80.sffca.ip.att.net [12.123.13.154]
8 705 ms 710 ms 716 ms tbr1-cl2.sl9mo.ip.att.net [12.122.10.41]
9 695 ms 700 ms 712 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
10 704 ms 708 ms 684 ms gar1-p300.ascva.ip.att.net [12.123.8.49]
11 * * * Request timed out.
12 681 ms 680 ms 677 ms ae1.p400.msr1.dcn.yahoo.com [216.115.96.181]
13 697 ms 692 ms 697 ms ge5-2.bas2-m.dcn.yahoo.com [216.109.120.199]
14 717 ms 705 ms 704 ms w2.rc.vip.dcn.yahoo.com [216.109.112.135]
Trace complete. |
|
iceman420
join:2005-04-18
Salinas, CA
| reply to iceman420
I dont want any more tech's coming out to my house, the tech has came at least 3times last month. I called comcast earlier and he filled a sheet to there network techs about our problem and i should be getting a call back by 72 house or so. (i hope)
BTW It got slower!
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 9 ms 26 ms 12.244.98.113
4 19 ms 18 ms 15 ms 12.244.67.201
5 693 ms 672 ms 675 ms 12.244.72.206
6 700 ms 671 ms 675 ms gbr2-p50.sffca.ip.att.net [12.123.13.62]
7 671 ms 677 ms 722 ms tbr1-p012702.sffca.ip.att.net [12.122.11.69]
8 676 ms 668 ms 646 ms 12.122.80.66
9 639 ms 657 ms 662 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
10 691 ms 664 ms 687 ms ae-1-55.bbr1.SanJose1.Level3.net [4.68.123.129]
11 728 ms 734 ms 731 ms as-3-0.bbr1.Washington1.Level3.net [64.159.3.254
]
12 757 ms 765 ms 766 ms ae-11-55.car1.Washington1.Level3.net [4.68.121.1
46]
13 779 ms 766 ms 772 ms 4.79.228.26
14 724 ms 715 ms 717 ms 216.239.46.34
15 717 ms 699 ms 714 ms 64.233.174.130
16 750 ms 768 ms 808 ms 216.239.48.110
17 742 ms 753 ms 752 ms 216.239.37.99
Trace complete. |
|
mtown408x
join:2003-02-01
Milpitas, CA
| reply to iceman420
Tracing route to www.yahoo.akadns.net [68.142.226.47]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 7 ms 10 ms 8 ms 12.244.25.145
4 9 ms 9 ms 9 ms 12.244.67.17
5 10 ms 9 ms 9 ms 12.244.72.210
6 717 ms 708 ms 731 ms gbr5-p40.sffca.ip.att.net [12.122.2.254]
7 712 ms 715 ms 710 ms tbr2-p013501.sffca.ip.att.net [12.122.11.89]
8 698 ms 695 ms 701 ms tbr1-cl2.sl9mo.ip.att.net [12.122.10.41]
9 727 ms 711 ms 722 ms tbr1-cl4.wswdc.ip.att.net [12.122.10.29]
10 730 ms 708 ms 712 ms gar1-p300.ascva.ip.att.net [12.123.8.49]
11 * * * Request timed out.
12 729 ms 726 ms 735 ms ge-3-1-0.p460.msr2.re1.yahoo.com [216.115.96.193
]
13 717 ms 721 ms 730 ms t-2-1.bas1.re2.yahoo.com [206.190.33.89]
14 727 ms 718 ms 724 ms p16.www.re2.yahoo.com [68.142.226.47] |
|
n1k0
join:2005-08-02 | wow its getting even slower!! >800ms ping times to google.com and yahoo.com from salinas CA. |
|
pokesph
It Is Almost Fast
Premium
join:2001-06-25
Sacramento, CA
clubs:
 ·Comcast
2 edits | reply to iceman420
Tracing route to www.google.com [66.102.7.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms . [192.168.2.1]
2 9 ms 36 ms 39 ms 10.184.224.1
3 16 ms 40 ms 89 ms 12.244.16.129
4 103 ms 95 ms 8 ms 12.244.69.185
5 12 ms 48 ms 92 ms 12.127.32.89
6 14 ms 15 ms 79 ms tbr1-p012301.sffca.ip.att.net [12.123.13.173]
7 55 ms 50 ms 89 ms 12.122.80.66
8 99 ms 63 ms 46 ms att-gw.sea.level3.net [192.205.32.206]
9 85 ms 40 ms 42 ms ge-7-1.ipcolo1.SanJose1.Level3.net [4.68.123.73]
10 25 ms 65 ms 65 ms 4.79.216.58
11 119 ms 52 ms 42 ms 64.233.174.54
12 74 ms 39 ms 49 ms 216.239.49.154
13 92 ms 78 ms 93 ms 66.102.7.99
Trace complete.
C:\WINDOWS\system32>tracert www.yahoo.com
Tracing route to www.yahoo.akadns.net [66.94.230.40]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms . [192.168.2.1]
2 60 ms 11 ms 12 ms 10.184.224.1
3 38 ms 46 ms 12 ms 12.244.16.145
4 48 ms 11 ms 8 ms 12.244.69.153
5 54 ms 38 ms 57 ms 12.127.33.45
6 121 ms 39 ms 14 ms gbr6-p30.sffca.ip.att.net [12.123.13.162]
7 44 ms 55 ms 78 ms ggr2-p390.sffca.ip.att.net [12.123.13.194]
8 60 ms 79 ms 36 ms att-gw.sea.level3.net [192.205.32.206]
9 19 ms 13 ms 35 ms ge-11-2.ipcolo3.SanJose1.Level3.net [4.68.123.17
1]
10 38 ms 54 ms 73 ms unknown.Level3.net [64.152.69.30]
11 40 ms 113 ms 16 ms UNKNOWN-66-218-82-217.yahoo.com [66.218.82.217]
12 32 ms 56 ms 80 ms www.yahoo.akadns.net [66.94.230.40]
Trace complete.
C:\WINDOWS\system32>
Looks ok here in Sacramento, CA
Webmaster Steve
- - - - - - - - - - - -
»ppnhosting.com
»sphenterprizes.com
»pokemonpalace.net |
|
retartedazn
join:2005-08-02
San Jose, CA
| reply to iceman420
oh man i live in San Jose, CA and lookat my stuff...i dunno what it means (im a noob, dunno any of this comcast stuff) and all i know is that big numbers is bad -_-
Tracing route to comcast.net [63.240.76.72]
over a maximum of 30 hops:
1 * * * Request timed out.
2 23 ms 9 ms 7 ms 12.244.24.225
3 752 ms 752 ms 758 ms 12.244.72.206
4 834 ms 817 ms 821 ms gbr1-p70.sffca.ip.att.net [12.123.13.58]
5 821 ms 820 ms 829 ms tbr1-p012402.sffca.ip.att.net [12.122.11.65]
6 824 ms 833 ms 837 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5]
7 844 ms 823 ms 820 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1]
8 826 ms 810 ms 819 ms gbr1-p10.n54ny.ip.att.net [12.122.11.2]
9 812 ms 841 ms 827 ms gar1-p360.n54ny.ip.att.net [12.123.1.129]
10 817 ms 845 ms 850 ms mdf1-gsr12-2-pos-7-0.nyc3.attens.net [12.122.255
.162]
11 825 ms 823 ms 831 ms sccsbix12-1-6.attbi.com [63.240.64.50]
12 832 ms 837 ms 831 ms 192.168.72.6
13 843 ms 841 ms 854 ms 192.168.72.73
14 854 ms 832 ms 843 ms 192.168.201.12
15 825 ms 829 ms 831 ms www.comcast.net [63.240.76.72]
Trace complete. |
|
MrPenguin
Penguins Rawk
join:2000-07-03
Castro Valley, CA
| reply to iceman420
I just started experiencing this about 20 minutes ago without a modem reboot. I've power-cycled twice; didn't solve anything. Spoke with tech support and they said it could be connected to an ongoing issue in the bay area? This is the first time I've had any connection problems in 3+ years... guess I'm lucky?
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
2 7 ms 14 ms 7 ms 10.147.152.1
3 7 ms 13 ms 10 ms 68.87.196.5
4 10 ms 9 ms 7 ms 68.87.192.125
5 8 ms 8 ms 10 ms 68.87.192.130
6 8 ms 8 ms 8 ms 68.87.192.134
7 11 ms 8 ms 12 ms 68.87.195.14
8 10 ms 10 ms 9 ms 12.127.32.61
9 821 ms 820 ms 806 ms tbr1-p012301.sffca.ip.att.net [12.123.13.173]
10 810 ms 826 ms 837 ms tbr1-cl1.cgcil.ip.att.net [12.122.10.5]
11 831 ms 821 ms 818 ms tbr1-cl1.n54ny.ip.att.net [12.122.10.1]
12 802 ms 801 ms 808 ms gar1-p341.nwrnj.ip.att.net [12.123.0.37]
13 * * * Request timed out.
14 814 ms 823 ms 798 ms 2.ge-0-0-0.gbr1.nwr.nac.net [209.123.11.213]
15 803 ms 813 ms 842 ms 0.ge-0-0-0.gbr1.oct.nac.net [209.123.11.49]
16 813 ms 813 ms 812 ms www.dslreports.com [209.123.109.175]
Trace complete.
--
Regards,MrPenguin |
|
iceman420
join:2005-04-18
Salinas, CA
| reply to iceman420
Welcome to the club MrPenguin.
Tracing route to google.com [216.239.57.99]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 9 ms 9 ms 12.244.98.113
4 141 ms 143 ms 129 ms 12.244.67.201
5 1022 ms 1031 ms 1023 ms 12.244.72.206
6 971 ms 1009 ms 1015 ms gbr2-p50.sffca.ip.att.net [12.123.13.62]
7 994 ms 987 ms 996 ms tbr1-p012702.sffca.ip.att.net [12.122.11.69]
8 1013 ms 992 ms 1029 ms ggr2-p300.sffca.ip.att.net [12.123.13.190]
9 1025 ms 1105 ms 1032 ms so-8-1.car3.SanJose1.Level3.net [209.0.227.29]
10 1041 ms 1001 ms 1003 ms ge-7-1.ipcolo1.SanJose1.Level3.net [4.68.123.73]
11 1011 ms 1003 ms 1025 ms 4.79.216.58
12 1051 ms 1008 ms 1031 ms 66.249.94.25
13 1074 ms 979 ms 987 ms 216.239.49.5
14 984 ms 952 ms 947 ms 216.239.57.99
Trace complete.
What can we do to make them fix this MAJOR issue?? Anyone have any suggestions?? |
|
eswierk
join:2003-12-20
Mountain View, CA
| Horrible latency here in Mountain View tonight.
Here are traceroutes to each of the two DNS servers that I get from Comcast DHCP. The one on the 204. network is fine, while the one on the 63. network goes through some nasty bottleneck, 12.244.72.206.
traceroute to ns1.attbi.com (204.127.198.4), 30 hops max, 38 byte packets
1 * * *
2 12.244.25.145 (12.244.25.145) 48.970 ms 15.352 ms 12.247 ms
3 12.244.67.17 (12.244.67.17) 41.494 ms 19.273 ms 16.516 ms
4 12.244.72.206 (12.244.72.206) 963.014 ms 975.598 ms 990.944 ms
5 gbr2-p50.sffca.ip.att.net (12.123.13.62) 48.930 ms 51.365 ms 50.977 ms
MPLS Label=778 CoS=5 TTL=1 S=0
6 tbr1-p012702.sffca.ip.att.net (12.122.11.69) 51.265 ms 48.537 ms 49.610 ms
MPLS Label=32441 CoS=5 TTL=1 S=0
7 gar4-p300.sffca.ip.att.net (12.123.13.174) 43.734 ms 46.054 ms 44.295 ms
8 idf22-gsr12-1-pos-6-0.rwc1.attens.net (12.122.255.222) 60.185 ms 49.612 ms 49.186 ms
9 * * *
traceroute to ns6.attbi.com (63.240.76.4), 30 hops max, 38 byte packets
1 * * *
2 12.244.25.145 (12.244.25.145) 14.175 ms 12.492 ms 11.745 ms
3 12.244.67.17 (12.244.67.17) 15.393 ms 18.245 ms 12.327 ms
4 12.244.72.206 (12.244.72.206) 984.755 ms 980.399 ms 969.847 ms
5 gbr2-p50.sffca.ip.att.net (12.123.13.62) 1040.638 ms 1050.271 ms 1042.999 ms
MPLS Label=754 CoS=5 TTL=1 S=0
6 tbr1-p012702.sffca.ip.att.net (12.122.11.69) 1025.997 ms 1017.070 ms 1020.897 ms
MPLS Label=32351 CoS=5 TTL=1 S=0
7 tbr1-cl1.cgcil.ip.att.net (12.122.10.5) 1023.865 ms 1050.209 ms 1049.872 ms
MPLS Label=32294 CoS=5 TTL=1 S=0
8 tbr1-cl1.n54ny.ip.att.net (12.122.10.1) 1029.811 ms 1003.196 ms 1007.352 ms
MPLS Label=32426 CoS=5 TTL=1 S=0
9 gbr2-p10.n54ny.ip.att.net (12.122.11.6) 1015.617 ms 1048.175 ms 1045.784 ms
MPLS Label=25 CoS=5 TTL=1 S=0
10 gar1-p370.n54ny.ip.att.net (12.123.1.133) 1029.643 ms 1026.202 ms 1032.564 ms
11 mdf1-gsr12-2-pos-7-0.nyc3.attens.net (12.122.255.162) 1033.973 ms 1044.579 ms 1033.026 ms
12 * * * |
|
mantou
join:2005-04-02
Fremont, CA | Fremont here as well, slow pings, horrible speeds since earlier today |
|
MrPenguin
Penguins Rawk
join:2000-07-03
Castro Valley, CA
| reply to iceman420
Download Speed: 210 kbps (26.3 KB/sec transfer rate)
Upload Speed: 57 kbps (7.1 KB/sec transfer rate)
I'm on the "gold" tier and usually get a solid 6.1/710 down/up. I've talked to two live analysts, the second of which said they have an internal posting regarding slow connections in the Bay Area tonight, but it's not listed on their public network status page.
This is *abysmal*.
--
Regards,MrPenguin |
|
MrPenguin
Penguins Rawk
join:2000-07-03
Castro Valley, CA
| reply to iceman420
RE: This affecting gaming... I mentioned to the online CSR that the *lowest* server ping I can see tonight in Battlefield 2 is 1040ms. Ugh.
Weird thing is, this came on in the *middle* of a file transfer. I was getting 760KB+ then nothing. What gives? It's not my computer, router, or modem; like eswierk pointed out, it's something in SF on a router coverting the 12.244.72.xxx range of IPs. Double ugh.
--
Regards,MrPenguin |
|
