September 2012 - Outages

Godaddy / Premium DNS outage?
by chris 06 Oct '12

06 Oct '12

It appears PDNS01 and PDNS02 are not resolving. Anyone else seeing the issue? PDNS01.DOMAINCONTROL.COM PDNS02.DOMAINCONTROL.COM thanks chris

39 43

Chunkhost LAX2 outage
by Sadiq Saif 30 Sep '12

30 Sep '12

Confirmed via their twitter: https://twitter.com/chunkhost/status/252523170257575937 -- Sadiq S O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

1 0

Amazon.com
by Robert Kulagowski 30 Sep '12

30 Sep '12

Down in Chicago on Comcast; http://www.downforeveryoneorjustme.com/www.amazon.com agrees.

6 6

Comcast
by Jacob Heider 28 Sep '12

28 Sep '12

Anyone else in the Southeast seeing a Comcast outage between Miami and everything else?

1 1

Chicago-area Level3 to Amazon AWS EAST-1
by Sarlas, George 27 Sep '12

27 Sep '12

Since approx. 4am CT, we've been seeing 15-30% dropped packets for traffic going from our Chicago Level3 connection to Amazon's EAST-1 data center. Our San Francisco office (also using Level3) isn't experiencing a problem. I've re-routed this traffic to our backup Internet connection (Airlogic) for now, and that traffic is getting through just fine. Anyone else seeing this problem? Ticket already opened with Level3, waiting to hear back. Thank you. Here's the route my traffic is taking (time outs at the bottom are normal, ICMP gets blocked from that point on). Tracing route to zioreports.com [75.101.163.221] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms ge-6-2-107.car4.Chicago1.Level3.net [4.71.102.161] 2 * * * Request timed out. 3 16 ms 22 ms 25 ms ae-5-5.ebr2.Chicago2.Level3.net [4.69.140.194] 4 19 ms 24 ms 25 ms ae-6-6.ebr2.Washington12.Level3.net [4.69.148.145] 5 * * * Request timed out. 6 16 ms 18 ms 23 ms ae-82-82.csw3.Washington1.Level3.net [4.69.134.154] 7 16 ms 16 ms 17 ms ae-3-80.edge2.Washington1.Level3.net [4.69.149.142] 8 17 ms 17 ms 16 ms AMAZON.COM.edge2.Washington1.Level3.net [4.79.22.74] 9 * * * Request timed out. 10 17 ms 18 ms 17 ms 72.21.222.139 11 18 ms 18 ms 18 ms 216.182.224.17 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 * * ^C Here are the results of a TCPing to port 443: 2012:09:27 09:50:02 Probing 75.101.163.221:443/tcp - Port is open - time=20.926ms 2012:09:27 09:50:03 Probing 75.101.163.221:443/tcp - Port is open - time=31.168ms 2012:09:27 09:50:05 Probing 75.101.163.221:443/tcp - Socket is not connected (10057) - time=2012.341ms 2012:09:27 09:50:07 Probing 75.101.163.221:443/tcp - Port is open - time=31.358ms 2012:09:27 09:50:08 Probing 75.101.163.221:443/tcp - Socket is not connected (10057) - time=2012.448ms 2012:09:27 09:50:10 Probing 75.101.163.221:443/tcp - Port is open - time=30.985ms 2012:09:27 09:50:12 Probing 75.101.163.221:443/tcp - Port is open - time=31.224ms 2012:09:27 09:50:13 Probing 75.101.163.221:443/tcp - Port is open - time=32.065ms 2012:09:27 09:50:15 Probing 75.101.163.221:443/tcp - Socket is not connected (10057) - time=2012.375ms 2012:09:27 09:50:17 Probing 75.101.163.221:443/tcp - Port is open - time=31.115ms Ping statistics for 75.101.163.221:443 10 probes sent. 7 successful, 3 failed. Approximate trip times in milli-seconds (successful connections only): Minimum = 20.926ms, Maximum = 32.065ms, Average = 20.884ms ---- George Sarlas Manager, IT Operations iRhythm Technologies, Inc. 2 Marriott Dr. Lincolnshire, IL 60069 email: gsarlas(a)irhythmtech.com phone: 224-543-4253

4 4

pnc.com/pncvirtualwallet.com
by Brandon Galbraith 27 Sep '12

27 Sep '12

pnc.com and pncvirtualwallet.com appear down from Chicago, IL on Comcast fiber connection. Is anyone seeing similar issues? traceroute to pnc.com (170.201.60.3), 64 hops max, 52 byte packets 3 te-0-8-0-0-ar01.area4.il.chicago.comcast.net (69.139.200.137) 11.540 ms 9.807 ms 7.451 ms 4 pos-3-12-0-0-cr01.350ecermak.il.ibone.comcast.net (68.86.91.233) 10.902 ms 10.016 ms 8.221 ms 5 pos-0-13-0-0-pe01.350ecermak.il.ibone.comcast.net (68.86.87.250) 7.479 ms 7.336 ms 7.216 ms 6 ix-1-3-0-0.tcore2.ct8-chicago.as6453.net (206.82.141.137) 19.081 ms 6.789 ms 7.133 ms 7 64.86.79.2 (64.86.79.2) 6.709 ms 7.219 ms 7.316 ms 8 206.82.141.134 (206.82.141.134) 7.208 ms 6.755 ms 7.312 ms 9 0.so-2-0-1.xt1.dca6.alter.net (152.63.13.18) 35.845 ms 35.466 ms 35.397 ms 10 20.tengigabitethernet9-0.sa1.dca6.alter.net (152.63.42.13) 35.428 ms 35.587 ms 35.965 ms 11 * * * 12 * * * 13 * * * 1

5 5

Citrix's support site unavailable
by Nate Carlson 27 Sep '12

27 Sep '12

..at least from the Minneapolis area. The main Citrix home page works (http://www.citrix.com) but links like Support -> Knowledge Center (which is http://support.citrix.com/) redirect to: http://cdn.ws.citrix.com/static/503-global.html

4 4

Level 3 -> XO
by Jayson Navitsky 26 Sep '12

26 Sep '12

We're showing intermittent (well -- now no) connectivity to XO from Level 3 in NYC (and from the looks of the L3 looking glass other areas of the US.) Anyone else seeing this? NYC to XO Web: traceroute to www.xo.com (205.158.160.76), 30 hops max, 60 byte packets 4 ge-9-23.car1.newyork1.level3.net (4.26.32.89) 4.240 ms 4.210 ms 4.177 ms 5 ae-2-70.edge2.newyork1.level3.net (4.69.155.80) 2.200 ms 2.155 ms 1.895 ms 6 206.111.13.65.ptr.us.xo.net (206.111.13.65) 1.963 ms 1.667 ms 1.624 ms 7 * * * 8 * * * NYC to XO (NYC): traceroute to 207.86.XXX.x (207.86.XXX.x), 30 hops max, 60 byte packets 4 ge-9-23.car1.newyork1.level3.net (4.26.32.89) 2.702 ms 2.678 ms 2.667 ms 5 ae-4-90.edge2.newyork1.level3.net (4.69.155.208) 1.607 ms 1.558 ms 1.538 ms 6 206.111.13.65.ptr.us.xo.net (206.111.13.65) 1.644 ms 1.575 ms 1.549 ms 7 * * * 8 * * * *Show Level 3 (Dallas, TX) Traceroute to 205.158.160.76* 1 ae-1-60.edge2.Dallas3.Level3.net (4.69.145.12) 0 msec ae-2-70.edge2.Dallas3.Level3.net (4.69.145.76) 0 msec ae-4-90.edge2.Dallas3.Level3.net (4.69.145.204) 4 msec 2 XO-Level3.edge2.Dallas3.Level3.net (4.68.127.150) 0 msec 0 msec 12 msec 3 * * * 4 * * * -J

15 17

L3 cut in Baton Rouge?
by Chris Boyd 25 Sep '12

25 Sep '12

Sorry, no details, but I'm hearing about a fiber cut on Level 3, near baton Rouge. --Chris

2 1

Capital One outage
by Josh Luthman 25 Sep '12

25 Sep '12

I made a purchase less than an hour ago (car parts) and then went across the street to Walmart and found my credit card wasn't working - tried it twice. I used another card and it worked. The successful purchase is listed on their website - capitalone.com It seems their phones are down/busy - 804.934.2001 or 800.955.7070 from my landline, Verizon cell and Google Voice. Never seen anything like this before. Does anyone have any other information? Nothing on their Twitter account - https://twitter.com/CapitalOne Josh Luthman Office: 937-552-2340 Direct: 937-552-2343 1100 Wayne St Suite 1337 Troy, OH 45373

2 3