nanog mailing list archives
Re: google ipv6 routes via cogent
From: Olivier Benghozi <olivier.benghozi () wifirst fr>
Date: Thu, 2 Mar 2017 15:11:14 +0100
Due to various peering disputes (notably with Hurricane Electric) Cogent just don't have all the routes in IPv6 (and should be regarded as a partial IPv6 transit only). One should not rely only on Cogent for its transit, anyway :) Don't count on any improvement soon. It was already discussed here one year ago...
On 25 feb. 2017 at 16:49, Aaron <aaron1 () gvtc com> wrote : Cogent is telling me that I can't route through cogent to get to google ipv6 routes (particularly the well known dns addresses 2001:4860:4860::88xx) because google decided not to advertise those route to one of their mutual peers. Anyone know anything about this ? .and why it happened and when it will be resolved ?
Current thread:
- Re: google ipv6 routes via cogent, (continued)
- Re: google ipv6 routes via cogent Jeremy Austin (Mar 03)
- Re: google ipv6 routes via cogent Patrick W. Gilmore (Mar 04)
- Re: google ipv6 routes via cogent Jared Mauch (Mar 02)
- Re: google ipv6 routes via cogent joel jaeggli (Mar 07)
- Re: google ipv6 routes via cogent Chuck Anderson (Mar 02)
- Re: google ipv6 routes via cogent Hunter Fuller (Mar 02)
- Message not available
- Message not available
- Re: google ipv6 routes via cogent Baldur Norddahl (Mar 04)
- Re: google ipv6 routes via cogent Dennis Bohn (Mar 02)
- Re: google ipv6 routes via cogent Theodore Baschak (Mar 02)
- Re: google ipv6 routes via cogent Christopher Morrow (Mar 02)
- Re: google ipv6 routes via cogent Marty Strong via NANOG (Mar 08)
- Re: google ipv6 routes via cogent Alarig Le Lay (Mar 08)