[193895] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: google ipv6 routes via cogent

daemon@ATHENA.MIT.EDU (Marty Strong via NANOG)
Thu Mar 2 09:16:28 2017

X-Original-To: nanog@nanog.org
In-Reply-To: <001801d28f7e$d063ac10$712b0430$@gvtc.com>
Date: Thu, 2 Mar 2017 14:05:11 +0000
To: Aaron <aaron1@gvtc.com>
From: Marty Strong via NANOG <nanog@nanog.org>
Reply-To: Marty Strong <marty@cloudflare.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Cogent refuses to settlement-free peer on IPv6 to Google and Hurricane =
Electric.

The problem *in my mind* rests with Cogent trying to extract $$$ from =
said parties.

Regards,
Marty Strong
--------------------------------------
Cloudflare - AS13335
Network Engineer
marty@cloudflare.com
+44 7584 906 055
smartflare (Skype)

https://www.peeringdb.com/asn/13335

> On 25 Feb 2017, at 15:49, Aaron <aaron1@gvtc.com> wrote:
>=20
> Hi, I'm new to the nanog list, hope this isn't out of scope for what =
is
> usually discussed here.
>=20
>=20
>=20
> 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.
>=20
>=20
>=20
> Anyone know anything about this ?  .and why it happened and when it =
will be
> resolved ?
>=20
>=20
>=20
> -Aaron
>=20
>=20
>=20
>=20
>=20


home help back first fref pref prev next nref lref last post