[187023] in North American Network Operators' Group

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

Re: Youtube CDN unreachable over IPv6

daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Thu Jan 14 10:37:29 2016

X-Original-To: nanog@nanog.org
To: Seth Mos <seth.mos@dds.nl>
From: Valdis.Kletnieks@vt.edu
In-Reply-To: <5697B916.5040107@dds.nl>
Date: Thu, 14 Jan 2016 10:37:16 -0500
Cc: nanog@nanog.org
Errors-To: nanog-bounces@nanog.org

--==_Exmh_1452785836_2311P
Content-Type: text/plain; charset=us-ascii

On Thu, 14 Jan 2016 16:04:54 +0100, Seth Mos said:

> lsintra:~# telnet 62.214.62.205 443

> lsintra:~# telnet 2001:1438:1:2::d 443

> Is it possible for Google to realize some form of internal monitoring to
> catch these defunct dual stack nodes?

A traceroute to both would help greatly in determining whether it's really
Google's fault, or if your ipv6 routing is borked.

--==_Exmh_1452785836_2311P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Exmh version 2.5 07/13/2001

iQIVAwUBVpfArAdmEQWDXROgAQLLNhAAllOV+cvjesehzw+C6cwL2+XwTU37CHAv
MuUMenyTpys48niuL7hMHbavbZ3rGzp6WDPtEESm5t2XhasYA+bLAseIyhDSeEjJ
zkNnxTYoE1jGboTGkUE5EWjv94ndbHVSk90Bj+ZYUuAbx7pnQLgPZUtsK1LB+TUk
c1+cUc6zoCcyhYB3qzmU3YMINdtZj4+JdoVBduQzEZUflFHoEKFSg53CHFbtguJL
TuKRnMMcIE3WSyTfEorOjciVofR2hQ7iOtyekbG0tVR10/CfBXbGP1eiHtWHWr2J
KbWQMH+ixuxsrLUF3jI5xWFdOmSTmizpWyPe2lj7F0bQbee2zjF3R4FY3Qnt2qUp
xOhAm/rutKW2ujM6sJSoCkJ//CL8xmnDk+Pkpq1O0XrzAkHOJEyd9oOZqVEWJdBN
GKHt9A4mSGCzGHpolXEPKNUSf8qXXnChKPX+PFHuKoUL2uwT4pKL3/rHJaYrdphV
gWPLsfv9Zhf5vmOF9gy4nMGv6tOYfDZChPjqpVwlooVvcaIFHj9dFCmqyPAOBLZO
WlUAFg0szsf28O3pEJwsvuOQgyUIFDnPjq4aWDGnf1fxfQkAOK5/nkINW3k+coSw
/EXw/lop1hkQYVVVc7vVn2xiPksq16ZEGAy//T88JwCWSUU+QdsT2zaAoaSO3ILV
6U//+NVlhNk=
=Fhuy
-----END PGP SIGNATURE-----

--==_Exmh_1452785836_2311P--

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