Problems with either Cisco.com or AT&T?

Mailman List Mirror (Read Only)
1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

No idea -- maybe just a hiccup?

- From my office in San Jose:

%traceroute www.cisco.com

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

[snip]

  7 3 ms 3 ms 3 ms so-3-0-0.mpr2.sjc7.us.above.net
[64.125.30.173]

  8 3 ms 3 ms 3 ms above-att.sjc7.us.above.net [64.125.13.50]
  9 7 ms 7 ms 7 ms tbr1.sffca.ip.att.net [12.123.12.2]
10 6 ms 6 ms 6 ms gbr5.sffca.ip.att.net [12.122.11.74]
11 6 ms 6 ms 6 ms gar1.sj2ca.ip.att.net [12.122.2.253]
12 * * * Request timed out.
13 * * * Request timed out.
14 * ^C

- From MIT:

Tracing to: www.cisco.com

1 legacy26-0.default.csail.mit.edu (18.26.0.1) [AS3] 0 ms 0 ms 0 ms
2 kalgan.trantor.csail.mit.edu (128.30.0.245) [AS40] 0 ms 0 ms 0 ms
3 B24-RTR-2-CSAIL.MIT.EDU (18.4.7.1) [AS3] 0 ms 0 ms 0 ms
4 EXTERNAL-RTR-1-BACKBONE.MIT.EDU (18.168.0.18) [AS3] 1 ms 4 ms 2 ms
5 ge-6-23.car2.Boston1.Level3.net (4.79.2.1) [AS3356] 0 ms * 0 ms
6 * * ae-5-5.ebr1.NewYork1.Level3.net (4.69.132.250) [AS3356] 8 ms
7 ae-61-61.csw1.NewYork1.Level3.net (4.69.134.66) [AS3356] 10 ms 5 ms
16 ms
8 ae-13-69.car3.NewYork1.Level3.net (4.68.16.5) [AS3356] 67 ms 59 ms
58 ms
9 att-level3-oc192.NewYork1.Level3.net (4.68.127.150) [AS3356] 17 ms
127 ms 12 ms
10 tbr1.n54ny.ip.att.net (12.123.3.57) [] [MPLS: Label 31537 Exp 0] 80 ms
79 ms 79 ms
11 12.122.16.153 (12.122.16.153) [] [MPLS: Label 19 Exp 0] 76 ms 77 ms
77 ms
12 cr1.cgcil.ip.att.net (12.122.1.190) [] [MPLS: Label 1188 Exp 0] 77 ms
76 ms 77 ms
13 12.122.17.146 (12.122.17.146) [] [MPLS: Label 31051 Exp 0] 77 ms 78
ms 78 ms
14 tbr1.sffca.ip.att.net (12.122.10.6) [] [MPLS: Label 31320 Exp 0] 78 ms
78 ms 78 ms
15 gbr5.sffca.ip.att.net (12.122.11.74) [] [MPLS: Label 323 Exp 0] 72 ms
71 ms 71 ms
16 gar1.sj2ca.ip.att.net (12.122.2.253) [] 76 ms 76 ms 77 ms
17 * * *
18 * * *
19 * * *
20 * * *

- - ferg

2

Im seeing issues at sbc as well
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 316 ms 330 ms 326 ms ex1-g1-0.eqchil.sbcglobal.net
[206.223.119.79]
  9 368 ms 352 ms 333 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 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Regards,

3

<mtr snip>

9. tbr2.sffca.ip.att.net
                                                                                        0.0% 6.8 5.5 4.7 6.8 0.4
10. gbr5.sffca.ip.att.net
                                                                                        0.0% 3.2 36.5 3.2 181.8 66.9
11. gar1.sj2ca.ip.att.net
                                                                                        0.0% 4.3 4.0 3.5 4.4 0.2
12. ???

down from here too

-wil

4

Ditto. We've had a few folks contact the Internet Storm Center about this.
First report came in at 2 pm ET.

Marc

5

Now that you have mentioned it I am having problems reaching Cisco from Sprint as well and Time Warner Telecom.

6

I get the same thing in Atlanta. I can't pull up their site and it looks like
my trace dies the same place as yours.

braaen@brian-debian:~$ traceroute www.cisco.com
traceroute to www.cisco.com (198.133.219.25), 30 hops max, 40 byte packets
1 gw_alpha.america.net (69.60.176.65) 1.618 ms 1.499 ms 1.559 ms
2 69.60.176.21 (69.60.176.21) 9.625 ms 9.461 ms 9.439 ms
3 gwF20.Edelta.america.net (69.60.160.1) 9.260 ms 9.113 ms 9.392 ms
4 66.0.192.194 (66.0.192.194) 16.189 ms 9.219 ms 9.234 ms
5 suwC6.gig3-1-4.qualitytech.com (216.154.207.145) 13.064 ms 9.316 ms
10.029 ms
6 suw04-gig1-0-0.qualitytech.com (216.154.207.173) 41.053 ms 9.432 ms
9.315 ms
7 gig5-1.suwangaeq00w.xr.deltacom.net (66.35.174.125) 34.815 ms 9.871 ms
25.280 ms
8 pos5-0.atlngapk22w.cr.deltacom.net (66.35.174.101) 19.050 ms 40.288 ms
13.137 ms
9 pos1-0.brhmalwd6aw.cr.deltacom.net (66.35.174.13) 17.860 ms 15.823 ms
15.881 ms
10 12.117.136.41 (12.117.136.41) 22.890 ms 18.614 ms 19.742 ms
11 tbr2.attga.ip.att.net (12.123.20.14) 76.260 ms 75.531 ms 75.004 ms
12 tbr1.dlstx.ip.att.net (12.122.2.89) 70.993 ms 70.863 ms 71.373 ms
13 tbr1.la2ca.ip.att.net (12.122.10.50) 74.889 ms 75.098 ms 74.921 ms
14 gar1.sj2ca.ip.att.net (12.122.2.249) 73.098 ms 72.969 ms 72.849 ms
15 * *

7

Useless also from Sprint (via AT&T in the middle) & Cogent - Dies at the pbi.net address.

Koch, Christian wrote:

8

A brief look at routeviews shows www.cisco.com (198.133.219.25)
originating from AS109 (Cisco) and transiting via AS7132 (AT&T/SBC) and
AS7018 (AT&T). Thus I suspect this is an issue with AS109 (Cisco) and
not with their providers. Though, I do feel wrong using the plural
"providers" in this case...

-Benson

9

Getting to Cisco now, but server is resetting the connection... Power outage maybe?

<mtr snip>

  9. tbr2.sffca.ip.att.net
                                                                                        2.5% 3.8 5.0 3.4 68.4 3.2
     sjck-dmzdc-gw2-gig1-1.cisco.com
10. gbr5.sffca.ip.att.net
                                                                                        3.8% 3.9 15.6 2.7 274.1 39.3
     sjce-dmzbb-gw1.cisco.com
11. gar1.sj2ca.ip.att.net
                                                                                        3.8% 4.0 3.6 3.3 13.1 0.5
     sjck-dmzdc-gw2-gig1-1.cisco.com
12. 12.118.124.10
                                                                                       98.5% 4.6 4.4 3.8 4.9 0.2
13. sjce-dmzbb-gw1.cisco.com
                                                                            98.5% 5.2 20.8 4.4 387.4 58.6
14. sjck-dmzdc-gw2-gig1-1.cisco.com 98.6% 5.4 5.4 4.9 6.2 0.3
15. ???

-wil

10

I can't speak for Cisco or Cisco IT, but as evidenced by this email, at least part of our connectivity is up.

No doubt someone official is looking at it as we speak. (I'll just lurk Nanog to get the skinny)..

11

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Ferguson wrote:

No idea -- maybe just a hiccup?

No, the outage is real and affecting network and systems for internal and
external services.

- --

12

Yep; when I sent my previous note, AS109 was still originating routes.
But packets seemed to die at the border router. Now I'm also seeing
routes via AS701 (UU/Verizon Biz) and AS1239 (Sprint) as well as AT&T,
but still no connectivity.

A few moments ago I was getting a response from the www.cisco.com
website, but it was a 403 Forbidden response. Thus I suspect that it's
not even a network problem so much as a website (LB, server, etc) issue,
or a DDoS attack, etc.

(Perhaps operators are changing route policy, trying to "fix" the wrong
issue?)

-Benson

13

Me too, looks like were riding uunet there now

6 3 ms <1 ms <1 ms POS1-0-0.GW18.NYC4.ALTER.NET
[157.130.21.73]
7 2 ms 9 ms 1 ms 0.ge-3-0-0.XL3.NYC4.ALTER.NET
[152.63.22.226]
8 73 ms 72 ms 73 ms 0.so-1-0-0.XL1.SJC1.ALTER.NET
[152.63.50.26]
9 72 ms 72 ms 72 ms POS6-0.GW5.SJC1.ALTER.NET [152.63.54.17]
10 73 ms 73 ms 74 ms cisco-sjc-gw.customer.alter.net
[157.130.198.78]
11 81 ms 74 ms 73 ms sjce-dmzbb-gw1.cisco.com [128.107.239.89]
12 * *

14

http://infiltrated.net/ciscoOutage.jpg