SBC Issues/Contact?

Anyone have a contact for sbc?

They are preventing me from getting to cisco.com

P:\>tracert cisco.com

Tracing route to cisco.com [198.133.219.25]
over a maximum of 30 hops:

  1 <1 ms <1 ms <1 ms 10.5.7.254
  2 <1 ms <1 ms <1 ms 209.10.21.253
  3 28 ms 28 ms 28 ms 209.10.9.37
  4 28 ms 27 ms 27 ms 209.10.9.25
  5 28 ms 27 ms 27 ms g-1-0-0.core2.nyc15.qualitytech.com
[209.10.10.186]
  6 28 ms 28 ms 28 ms so-1-0-0.core1.cgx2.globix.net
[209.10.10.161]
  7 28 ms 28 ms 28 ms pos-2-0.peer1.cgx3.globix.net
[209.10.12.82]
  8 451 ms 455 ms 450 ms ex1-g1-0.eqchil.sbcglobal.net
[206.223.119.79]
  9 513 ms 499 ms 501 ms ded4-g8-3-0.sntc01.pbi.net
[151.164.41.165]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * *

See Paul's previous email I do not think it was just SBC becuase I was having problems on my Sprint link as well as my time warner telecom link. It is resolved for me nowe though.

Same from comcast in NJ, through att as well

christian$ traceroute cisco.com
traceroute to cisco.com (198.133.219.25), 64 hops max, 40 byte packets
1 c-3-0-ubr02.tomsriver.nj.panjde.comcast.net (73.187.160.1) 10.146
ms 8.465 ms 7.789 ms
2 ge-6-3-sr01.tomsriver.nj.panjde.comcast.net (68.86.223.253) 8.223
ms 8.598 ms 9.799 ms
3 ge-2-24-ur01.dover.nj.panjde.comcast.net (68.86.210.85) 10.688 ms
10.301 ms 8.676 ms
4 te-1-1-ur02.dover.nj.panjde.comcast.net (68.86.210.62) 10.727 ms
10.454 ms 9.871 ms
5 te-1-1-ur01.brick2.nj.panjde.comcast.net (68.86.210.66) 11.213 ms
10.364 ms 11.415 ms
6 te-1-1-ur01.brick1.nj.panjde.comcast.net (68.86.210.70) 9.916 ms
10.859 ms 11.698 ms
7 te-1-1-ur01.eatontown.nj.panjde.comcast.net (68.86.210.74) 10.080
ms 10.954 ms 10.054 ms
8 te-1-1-ur02.eatontown.nj.panjde.comcast.net (68.86.210.78) 10.563
ms 9.920 ms 9.839 ms
9 te-2-1-ar01.eatontown.nj.panjde.comcast.net (68.86.210.82) 10.175
ms 11.745 ms 12.049 ms
10 po-90-ar01.verona.nj.panjde.comcast.net (68.86.208.9) 15.755 ms
12.065 ms 16.057 ms
11 po-10-ar01.plainfield.nj.panjde.comcast.net (68.86.208.5) 14.958 ms
14.316 ms 17.811 ms
12 ge-2-0-cr01.plainfield.nj.core.comcast.net (68.86.211.2) 14.115 ms
14.604 ms 13.343 ms
13 12.118.102.17 (12.118.102.17) 35.661 ms 36.602 ms 34.957 ms
14 tbr1.n54ny.ip.att.net (12.123.3.82) 81.193 ms 80.138 ms 81.954 ms
15 12.122.16.153 (12.122.16.153) 80.224 ms 76.693 ms 78.115 ms
16 cr1.cgcil.ip.att.net (12.122.1.190) 80.754 ms 80.302 ms 79.854 ms
17 12.122.17.138 (12.122.17.138) 80.818 ms 82.913 ms 81.352 ms
18 tbr1.sffca.ip.att.net (12.122.10.6) 81.334 ms 81.121 ms 82.318 ms
19 gbr5.sffca.ip.att.net (12.122.11.74) 80.030 ms 82.585 ms 78.627
ms
20 gar1.sj2ca.ip.att.net (12.122.2.253) 81.704 ms 80.848 ms 81.740
ms
21 * * *
22 * * *
23 * * *

Regards,

Just confirmed w/ Cisco, apparently there was a power outage in San Jose

Regards,