[outages] Anyone else seeing IPv6 issues going through Level3?

Frank Bulk frnkblk at iname.com
Sat Mar 17 12:21:10 EDT 2012 

I get all the way through.

Try using Level3's LookingGlass (http://lg.level3.net/) and see if there is
anything unique about your prefix.  You can also use their ping gateway,
choose Atlanta, and see if you can ping yourself.  

===

nagios:/var/log# traceroute 209.55.0.1
traceroute to 209.55.0.1 (209.55.0.1), 30 hops max, 60 byte packets
 1  router-core-inside.mtcnet.net (96.31.0.254)  0.238 ms  0.254 ms  0.298
ms
 2  sxct.sxcy.mtcnet.net (167.142.156.197)  0.192 ms  0.255 ms  0.310 ms
 3  siouxcenter.sxcy.137.netins.net (167.142.180.137)  1.638 ms  1.708 ms
1.777 ms
 4  ins-db1-te-13-2-219.desm.netins.net (167.142.60.157)  7.462 ms  7.481 ms
7.574 ms
 5  ins-dc1-et-8-2.desm.netins.net (167.142.67.5)  7.446 ms  7.463 ms  7.555
ms
 6  te-3-3.car2.KansasCity1.Level3.net (4.53.34.113)  13.632 ms  13.585 ms
13.651 ms
 7  ae-11-11.car1.KansasCity1.Level3.net (4.69.135.233)  13.636 ms  13.726
ms  13.746 ms
 8  ae-5-5.ebr2.Dallas1.Level3.net (4.69.135.230)  22.586 ms  22.585 ms
22.565 ms
 9  ae-62-62.csw1.Dallas1.Level3.net (4.69.151.129)  22.550 ms
ae-72-72.csw2.Dallas1.Level3.net (4.69.151.141)  22.608 ms
ae-82-82.csw3.Dallas1.Level3.net (4.69.151.153)  22.665 ms
10  ae-63-63.ebr3.Dallas1.Level3.net (4.69.151.134)  22.553 ms  22.554 ms
ae-73-73.ebr3.Dallas1.Level3.net (4.69.151.146)  22.541 ms
11  ae-7-7.ebr3.Atlanta2.Level3.net (4.69.134.22)  42.567 ms  42.494 ms
42.497 ms
12  ae-73-73.ebr2.Atlanta2.Level3.net (4.69.148.254)  46.892 ms  46.917 ms
ae-63-63.ebr1.Atlanta2.Level3.net (4.69.148.242)  51.437 ms
13  ae-16-51.car2.Atlanta2.Level3.net (4.69.150.6)  42.449 ms
ae-26-52.car2.Atlanta2.Level3.net (4.69.150.70)  42.543 ms
ae-16-51.car2.Atlanta2.Level3.net (4.69.150.6)  42.171 ms
14  INTEGRATED.car2.Atlanta2.Level3.net (4.71.255.14)  42.367 ms  42.596 ms
42.593 ms
15  host-209-55-31-18.ibbsonline.com (209.55.31.18)  42.647 ms  42.488 ms
42.676 ms
16  host-209-55-31-14.ibbsonline.com (209.55.31.14)  45.607 ms !X * *
nagios:/var/log#

and from another network:

[fbulk at server ~]$ traceroute 209.55.0.1
traceroute to 209.55.0.1 (209.55.0.1), 30 hops max, 60 byte packets
 1  ge-0-7-0-22.r05.chcgil09.us.bb.gin.ntt.net (204.42.253.5)  0.620 ms
0.935 ms  1.046 ms
 2  ae-8.r06.chcgil09.us.bb.gin.ntt.net (129.250.4.222)  0.671 ms  0.923 ms
0.829 ms
 3  xe-8-0-0.edge4.Chicago3.level3.net (4.68.63.197)  0.203 ms
xe-1.level3.chcgil09.us.bb.gin.ntt.net (129.250.8.78)  0.187 ms  0.230 ms
 4  vlan52.ebr2.Chicago2.Level3.net (4.69.138.190)  1.915 ms  0.440 ms
0.483 ms
 5  ae-5-5.ebr2.Chicago1.Level3.net (4.69.140.193)  0.366 ms  11.047 ms
11.050 ms
 6  ae-3-3.ebr2.Atlanta2.Level3.net (4.69.132.74)  38.170 ms  38.189 ms
37.864 ms
 7  ae-26-52.car2.Atlanta2.Level3.net (4.69.150.70)  32.691 ms  32.332 ms
32.696 ms
 8  INTEGRATED.car2.Atlanta2.Level3.net (4.71.255.14)  36.600 ms  36.814 ms
36.747 ms
 9  host-209-55-31-18.ibbsonline.com (209.55.31.18)  41.200 ms  41.180 ms
41.191 ms
10  host-209-55-31-14.ibbsonline.com (209.55.31.14)  36.637 ms !X * *
[fbulk at server ~]$

-----Original Message-----
From: TJ Scott [mailto:tscott at insideconnect.net] 
Sent: Saturday, March 17, 2012 11:14 AM
To: Frank Bulk
Cc: outages at outages.org
Subject: Re: Anyone else seeing IPv6 issues going through Level3?

traceroute to 209.55.0.1 (209.55.0.1), 64 hops max, 52 byte packets
 1  dd-wrt (192.168.1.1)  4.149 ms  1.025 ms  1.033 ms
 2  * * *
 3  74-128-20-77.dhcp.insightbb.com (74.128.20.77)  24.800 ms  13.379 ms
29.368 ms
 4  74.128.8.97 (74.128.8.97)  11.847 ms  11.378 ms  9.896 ms
 5  xe-9-3-0.edge2.chicago2.level3.net (4.59.28.41)  23.036 ms  17.941 ms
24.760 ms
 6  vl-3601-ve-225.ebr2.chicago2.level3.net (4.69.158.50)  32.579 ms
    vl-3604-ve-228.ebr2.chicago2.level3.net (4.69.158.62)  20.431 ms
    vl-3603-ve-227.ebr2.chicago2.level3.net (4.69.158.58)  19.685 ms
 7  ae-5-5.ebr2.chicago1.level3.net (4.69.140.193)  19.420 ms  19.491 ms
19.159 ms
 8  ae-3-3.ebr2.atlanta2.level3.net (4.69.132.74)  33.008 ms  32.132 ms
36.105 ms
 9  ae-26-52.car2.atlanta2.level3.net (4.69.150.70)  31.813 ms  30.816 ms
31.241 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

TJ Scott
Inside Connect Cable
502-955-4882
www.iccable.com

On Mar 17, 2012, at 12:11 PM, Frank Bulk wrote:

> Please share a target IP and a traceroute so others can test from their
> perspective.
> 
> Frank
> 
> -----Original Message-----
> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
> Behalf Of TJ Scott
> Sent: Saturday, March 17, 2012 11:03 AM
> To: outages at outages.org
> Subject: Re: [outages] Outages Digest, Vol 46, Issue 8
> 
> I'm seeing outage on level3 in Atlanta
> 
> TJ Scott
> Sent from my iPhone
> 
> On Mar 17, 2012, at 12:02 PM, "outages-request at outages.org"
> <outages-request at outages.org> wrote:
> 
>> Send Outages mailing list submissions to
>>   outages at outages.org
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>>   https://puck.nether.net/mailman/listinfo/outages
>> or, via email, send a message with subject or body 'help' to
>>   outages-request at outages.org
>> 
>> You can reach the person managing the list at
>>   outages-owner at outages.org
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Outages digest..."
>> 
>> 
>> Today's Topics:
>> 
>>  1. Re: Anyone else seeing IPv6 issues going through Level3?
>>     (Frank Bulk)
>>  2. Re: Anyone else seeing IPv6 issues going through Level3?
>>     (Frank Bulk)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Fri, 16 Mar 2012 18:50:11 -0500
>> From: "Frank Bulk" <frnkblk at iname.com>
>> To: <outages at outages.org>
>> Subject: Re: [outages] Anyone else seeing IPv6 issues going through
>>   Level3?
>> Message-ID: <00ff01cd03cf$868c07d0$93a41770$@iname.com>
>> Content-Type: text/plain; charset="us-ascii"
>> 
>> Our upstream provider opened up a ticket with Level3 late this afternoon.
>> Hopefully it will be resolved, soon.
>> 
>> Our upstream provider has three dual-stacked transit providers and they
> shut
>> down the Level3 IPv6 peering, but then we lost access to another third or
> so
>> of the sites.  For example, ipv6.t-mobile.com is only visible to us from
>> Level3, same with www.globalcrossing.com.  ipv6.cablelabs.com is with HE
> and
>> Level3 and we should be able to get HE via Sprint, but we lost visibility
>> anyways.
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
>> Behalf Of Frank Bulk
>> Sent: Friday, March 16, 2012 8:05 AM
>> To: 'Teun Vink'
>> Cc: outages at outages.org
>> Subject: Re: [outages] Anyone else seeing IPv6 issues going through
> Level3?
>> 
>> Thanks, Teun.
>> 
>> Someone else pointed to me offlist that this could be just our prefix,
>> 2607:fe28::/32.  I've already contacted our upstream provider who buys
the
>> transit from Level3.
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: Teun Vink [mailto:teun at teun.tv]
>> Sent: Friday, March 16, 2012 7:39 AM
>> To: Frank Bulk
>> Cc: outages at outages.org
>> Subject: Re: [outages] Anyone else seeing IPv6 issues going through
> Level3?
>> 
>> On Fri, 2012-03-16 at 07:12 -0500, Frank Bulk wrote:
>>> I monitor over 30 IPv6 hosts, and starting around 1:54 am (Central) I
>>> couldn't access about a third of them.  Here's the list of sites that I
>>> currently can't access:
>>> 
>> 
>> http://ring.nlnog.net promotime :)
>> 
>> Just ran a few tests from 88 host in 78 ASN's, 24 countries:
>> 
>>> ipv6_akamai_com_29  (2001:418:2401:9::8367:8929)
>> 
>> $ ring-ping 2001:418:2401:9::8367:8929
>> 2001:418:2401:9::8367:8929 - 87 servers: 119ms average
>> 2001:418:2401:9::8367:8929 - unreachable via: 1 server
>> 
>>> ipv6_akamai_com_40  (2001:418:2401:9::8367:8940_
>> 
>> $ ring-ping 2001:418:2401:9::8367:8940
>> 2001:418:2401:9::8367:8940 - 87 servers: 120ms average
>> 2001:418:2401:9::8367:8940 - unreachable via: 1 server
>> 
>>> ipv6_cnn_com
>> 
>> bit at bit01:~$ ring-http ipv6.cnn.com
>> unreachable via: 88 hosts
>> 
>>> ipv6_google_com
>> 
>> $ ring-http ipv6.google.com
>> unreachable via: 88 hosts
>> 
>>> ipv6_sprint_com
>> 
>> $ ring-http ipv6.sprint.com
>> 88 servers: OK
>> 
>> 
>> A ring-trace from all these hosts to 2001:418:2401:9::8367:8940
>> https://ring.nlnog.net/paste/p/pv2jaodnosy8mget
>> 
>> 
>> regards,
>> Teun
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>> 
>> -------------- next part --------------
>> A non-text attachment was scrubbed...
>> Name: smime.p7s
>> Type: application/pkcs7-signature
>> Size: 6517 bytes
>> Desc: not available
>> URL:
>
<https://puck.nether.net/pipermail/outages/attachments/20120316/6f0a0a8d/att
> achment-0001.p7s>
>> 
>> ------------------------------
>> 
>> Message: 2
>> Date: Fri, 16 Mar 2012 20:48:46 -0500
>> From: "Frank Bulk" <frnkblk at iname.com>
>> To: <outages at outages.org>
>> Subject: Re: [outages] Anyone else seeing IPv6 issues going through
>>   Level3?
>> Message-ID: <010801cd03e0$176bc9b0$46435d10$@iname.com>
>> Content-Type: text/plain;    charset="us-ascii"
>> 
>> Service was restored to me at 7:15 pm.  I don't have an RFO -- I can only
>> guess there was some routing table issue for our netblock in Level3's
>> infrastructure.
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
>> Behalf Of Frank Bulk
>> Sent: Friday, March 16, 2012 6:50 PM
>> To: outages at outages.org
>> Subject: Re: [outages] Anyone else seeing IPv6 issues going through
> Level3?
>> 
>> Our upstream provider opened up a ticket with Level3 late this afternoon.
>> Hopefully it will be resolved, soon.
>> 
>> Our upstream provider has three dual-stacked transit providers and they
> shut
>> down the Level3 IPv6 peering, but then we lost access to another third or
> so
>> of the sites.  For example, ipv6.t-mobile.com is only visible to us from
>> Level3, same with www.globalcrossing.com.  ipv6.cablelabs.com is with HE
> and
>> Level3 and we should be able to get HE via Sprint, but we lost visibility
>> anyways.
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On
>> Behalf Of Frank Bulk
>> Sent: Friday, March 16, 2012 8:05 AM
>> To: 'Teun Vink'
>> Cc: outages at outages.org
>> Subject: Re: [outages] Anyone else seeing IPv6 issues going through
> Level3?
>> 
>> Thanks, Teun.
>> 
>> Someone else pointed to me offlist that this could be just our prefix,
>> 2607:fe28::/32.  I've already contacted our upstream provider who buys
the
>> transit from Level3.
>> 
>> Frank
>> 
>> -----Original Message-----
>> From: Teun Vink [mailto:teun at teun.tv]
>> Sent: Friday, March 16, 2012 7:39 AM
>> To: Frank Bulk
>> Cc: outages at outages.org
>> Subject: Re: [outages] Anyone else seeing IPv6 issues going through
> Level3?
>> 
>> On Fri, 2012-03-16 at 07:12 -0500, Frank Bulk wrote:
>>> I monitor over 30 IPv6 hosts, and starting around 1:54 am (Central) I
>>> couldn't access about a third of them.  Here's the list of sites that I
>>> currently can't access:
>>> 
>> 
>> http://ring.nlnog.net promotime :)
>> 
>> Just ran a few tests from 88 host in 78 ASN's, 24 countries:
>> 
>>> ipv6_akamai_com_29  (2001:418:2401:9::8367:8929)
>> 
>> $ ring-ping 2001:418:2401:9::8367:8929
>> 2001:418:2401:9::8367:8929 - 87 servers: 119ms average
>> 2001:418:2401:9::8367:8929 - unreachable via: 1 server
>> 
>>> ipv6_akamai_com_40  (2001:418:2401:9::8367:8940_
>> 
>> $ ring-ping 2001:418:2401:9::8367:8940
>> 2001:418:2401:9::8367:8940 - 87 servers: 120ms average
>> 2001:418:2401:9::8367:8940 - unreachable via: 1 server
>> 
>>> ipv6_cnn_com
>> 
>> bit at bit01:~$ ring-http ipv6.cnn.com
>> unreachable via: 88 hosts
>> 
>>> ipv6_google_com
>> 
>> $ ring-http ipv6.google.com
>> unreachable via: 88 hosts
>> 
>>> ipv6_sprint_com
>> 
>> $ ring-http ipv6.sprint.com
>> 88 servers: OK
>> 
>> 
>> A ring-trace from all these hosts to 2001:418:2401:9::8367:8940
>> https://ring.nlnog.net/paste/p/pv2jaodnosy8mget
>> 
>> 
>> regards,
>> Teun
>> 
>> 
>> 
>> 
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>> 
>> 
>> 
>> 
>> ------------------------------
>> 
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>> 
>> 
>> End of Outages Digest, Vol 46, Issue 8
>> **************************************
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages
>

More information about the Outages mailing list