[193988] in North American Network Operators' Group
Re: google ipv6 routes via cogent
daemon@ATHENA.MIT.EDU (Alarig Le Lay)
Wed Mar 8 02:18:10 2017
X-Original-To: nanog@nanog.org
Date: Wed, 8 Mar 2017 08:18:01 +0100
From: Alarig Le Lay <alarig@swordarmor.fr>
To: nanog@nanog.org
In-Reply-To: <001801d28f7e$d063ac10$712b0430$@gvtc.com>
Errors-To: nanog-bounces@nanog.org
--ezjc55ymqfxfmxvx
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On sam. 25 f=C3=A9vr. 09:49:56 2017, Aaron wrote:
> 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 i=
pv6
> 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
Hi,
Since this morning, I see again google routes from cogent:
https://paste.swordarmor.fr/raw/wnFQ
But, with very bad latency. To go from Rennes (France) to Frankfurt
(Germany), it transits via Sydney, and still thought other ASes:
https://paste.swordarmor.fr/raw/PlSM
--=20
alarig
--ezjc55ymqfxfmxvx
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iQEzBAEBCAAdFiEE+2yGwT0H0n57WkRbrzhKwWsgK4gFAli/sCYACgkQrzhKwWsg
K4gI7ggAhSvrk0JShR0S0RVJ5BB4pvsvDEPcvPx3cbjBmyUsbeqfZGCTt9VcxRW6
JJGnj+cFkwCzEWyCjylqhbF0spWEIP8eHVgZ5UeL/zwgRcdoEmWCOOOPuSfON+CQ
RS0BbP/oZLR3p7+XRsAoUpisdLmJiCW1FJK7TJld+002zIInQCgmv3RpaArmYS5v
0QXlpVBjsQyX+EtGc+MT1qiUUUMJ4v47XG8ddPjtJnZ/FjMwwvoPmUYFpUfxpE0+
7WkqDHzUXkqjRyY+bT5PT9qgNOJN0rcpXdo0bCY7GGRW9NZfGcn2hUzG+dqTk1H/
xOTpmBP3D3b/+lT2hMCnwEONAxc8DQ==
=mMYZ
-----END PGP SIGNATURE-----
--ezjc55ymqfxfmxvx--
