[outages] Anyone else seeing IPv6 issues going through Level3?
TJ Scott
tscott at insideconnect.net
Sat Mar 17 12:13:45 EDT 2012
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