[outages] Access to ipv6.cnn.com

[Frank Bulk]

Thanks.  Fails somewhere with Qwest for me:

root at nagios:/tmp/ndisc6-1.0.1# tcptraceroute6 ipv6.cnn.com
traceroute to ipv6.cnn.com (2620:100:e000::8001) from 2607:fe28:0:1003:223:7dff:fe93:4bbf, port 80, from port 44330, 30 hops max, 60 bytes packets
 1  2607:fe28:0:1003::1 (2607:fe28:0:1003::1)  0.227 ms  0.184 ms  0.182 ms
 2  sxct.movl.mtcnet.net (2607:fe28:11:1002::194)  0.776 ms  0.449 ms  0.476 ms
 3  2001:5f8:7f06::9 (2001:5f8:7f06::9)  4.249 ms  3.374 ms  4.202 ms
 4  v6-ins-kb1-et-11-6-307.kmrr.netins.net (2001:5f8:2:2::1)  7.003 ms  7.231 ms  7.859 ms
 5  v6-ins-kc2-te-8-3.kmrr.netins.net (2001:5f8::11:1)  7.247 ms  7.912 ms  6.844 ms
 6  v6-ins-dc1-et-8-1.desm.netins.net (2001:5f8::8:1)  9.241 ms  8.441 ms  10.661 ms
 7  2001:428:3801:210:0:1:0:1 (2001:428:3801:210:0:1:0:1)  20.452 ms  20.549 ms  20.867 ms
 8  2001:428:0:1:205:171:202:246 (2001:428:0:1:205:171:202:246)  43.377 ms  44.020 ms  44.096 ms
 9  * * *
10  * * *
11  * * *

I will open a ticket with our upstream provider who has the relationship with Qwest.

Frank

-----Original Message-----
From: Mark Kamichoff [mailto:prox at prolixium.com] 
Sent: Wednesday, March 02, 2011 12:06 PM
To: Frank Bulk
Cc: outages at outages.org
Subject: Re: [outages] Access to ipv6.cnn.com

On Wed, Mar 02, 2011 at 09:35:35AM -0600, Frank Bulk wrote:
> I've been unable to access to ipv6.cnn.com since 4:19 am Central -
> anyone else aware of what's going on?

Looks ok from here:

% sudo tcptraceroute -q 1 ipv6.cnn.com.
traceroute to ipv6.cnn.com. (2620:100:e000::8001), 30 hops max, 80 byte packets
 1  vb0.dax.prolixium.net (2001:48c8:1:12e::1)  0.136 ms
 2  voxel.prolixium.net (2001:48c8:1:2::1)  0.492 ms
 3  0.ae2.tsr1.lga5.us.voxel.net (2001:48c8::82d)  0.466 ms
 4  te-4-3.car2.Dallas1.Level3.net (2001:1900:4:2::22d)  1.169 ms
 5  vl-69.car1.NewYork1.Level3.net (2001:1900:19:1::3)  2.015 ms
 6  2001:1900:4:1::3b9 (2001:1900:4:1::3b9)  6.995 ms
 7  2001:1900:4:1::3be (2001:1900:4:1::3be)  202.630 ms
 8  vl-90.car1.Washington3.Level3.net (2001:1900:15:8::e)  7.693 ms
 9  MCI-level3-10G.WashingtonDC4.Level3.net (2001:1900:4:3::13e)  7.803 ms
10  mcr1.smyrna-ga.us.xo.net (2610:18::3050)  35.157 ms
11  2620:100:e000:8::d (2620:100:e000:8::d)  37.992 ms
12  2620:100:e000:8::5 (2620:100:e000:8::5)  37.580 ms
13  2620:100:e000:8::6 (2620:100:e000:8::6)  38.630 ms
14  2620:100:e000::8001 (2620:100:e000::8001)  37.453 ms

% wget http://ipv6.cnn.com/               
--2011-03-02 13:03:53--  http://ipv6.cnn.com/
Resolving ipv6.cnn.com... 2620:100:e000::8001
Connecting to ipv6.cnn.com|2620:100:e000::8001|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: “index.html”

    [  <=>                          ] 101,709      228K/s   in 0.4s    

2011-03-02 13:03:53 (228 KB/s) - “index.html” saved [101709]

Although on the 28th I noticed that their prefix (2620:100:e000::/47)
disappeared from the DFZ for a couple hours...

- Mark

-- 
Mark Kamichoff
prox at prolixium.com
http://www.prolixium.com/