Mailing List Archive

google<<>>Deutsche Telekom
Hi,

at the moment(for 8 hours or longer) seems to be a problem between
google and Deutsche Telekom (AS3320).

I am wondering about just one person (forum at telekom) and I
complaining it.

Can anybody confirm or solving the problem?

A lot of google-services load very slowly(fallback to IPv4), also
websites with fonts loaded from google.

googles public-dns is working, but no other things.


Regards,
Thomas
Re: google<<>>Deutsche Telekom [ In reply to ]
I'm not sure if this is a particularly good venue for this. But you mention neither source IP nor the target IP Google returned to you using DNS.Hi,

at the moment(for 8 hours or longer) seems to be a problem between
google and Deutsche Telekom (AS3320).

I am wondering about just one person (forum at telekom) and I
complaining it.

Can anybody confirm or solving the problem?

A lot of google-services load very slowly(fallback to IPv4), also
websites with fonts loaded from google.

googles public-dns is working, but no other things.


Regards,
Thomas
Re: google<<>>Deutsche Telekom [ In reply to ]
Hi,

I can confirm I am also having issues reaching anything behind 15169 via
3320.
Example src: 2003:de:4be0:a800::/56, dst: 2a00:1450:4016:804::2003.
$ traceroute6 google.de
traceroute6 to google.de (2a00:1450:4016:804::2003) from
2003:de:4be0:a800:cd43:321a:ad4e:b726, 64 hops max, 12 byte packets
1 fritz.box 1.793 ms 1.195 ms 1.013 ms
2 p200300de4bbf20a80000000000000001.dip0.t-ipconnect.de 10.093 ms *
10.843 ms
3 * * *
4 * * *
5 * * *
6 * * *
7 * * *
8 * * *
9 * * *
10 * * *

Best regards,
Chris

On Sun, Mar 6, 2016 at 8:09 PM, Thomas Schäfer <thomas@cis.uni-muenchen.de>
wrote:

> Hi,
>
> at the moment(for 8 hours or longer) seems to be a problem between google
> and Deutsche Telekom (AS3320).
>
> I am wondering about just one person (forum at telekom) and I complaining
> it.
>
> Can anybody confirm or solving the problem?
>
> A lot of google-services load very slowly(fallback to IPv4), also websites
> with fonts loaded from google.
>
> googles public-dns is working, but no other things.
>
>
> Regards,
> Thomas
>
>


--
http://www.chrisk.de/
Re: google<<>>Deutsche Telekom [ In reply to ]
Please send a traceroute or mtr (offlist is fine).

Damian

On Sun, Mar 6, 2016 at 11:09 AM, Thomas Schäfer <thomas@cis.uni-muenchen.de>
wrote:

> Hi,
>
> at the moment(for 8 hours or longer) seems to be a problem between google
> and Deutsche Telekom (AS3320).
>
> I am wondering about just one person (forum at telekom) and I complaining
> it.
>
> Can anybody confirm or solving the problem?
>
> A lot of google-services load very slowly(fallback to IPv4), also websites
> with fonts loaded from google.
>
> googles public-dns is working, but no other things.
>
>
> Regards,
> Thomas
>
>
Re: google<<>>Deutsche Telekom [ In reply to ]
On Sun, 6 Mar 2016, Christian Kildau wrote:

> Hi,
>
> I can confirm I am also having issues reaching anything behind 15169 via
> 3320.
> Example src: 2003:de:4be0:a800::/56, dst: 2a00:1450:4016:804::2003.
> $ traceroute6 google.de
> traceroute6 to google.de (2a00:1450:4016:804::2003) from
> 2003:de:4be0:a800:cd43:321a:ad4e:b726, 64 hops max, 12 byte packets
> 1 fritz.box 1.793 ms 1.195 ms 1.013 ms
> 2 p200300de4bbf20a80000000000000001.dip0.t-ipconnect.de 10.093 ms *
> 10.843 ms
> 3 * * *

I don't have any insight, but it could be that Google is now doing the
same thing to DTAG as it has done to Cogent for a few weeks, ie
specifically ask its transit partners to not announce 15169 routes to
AS3320, and deciding AS15169 now to be IPv6 Tier1, and if you don't peer
with AS15169, you're not getting the routes.

--
Mikael Abrahamsson email: swmike@swm.pp.se
Re: google<<>>Deutsche Telekom [ In reply to ]
On Sun, Mar 06, 2016 at 10:27:44PM +0100, Mikael Abrahamsson wrote:
> >I can confirm I am also having issues reaching anything behind 15169 via
> >3320.
> >Example src: 2003:de:4be0:a800::/56, dst: 2a00:1450:4016:804::2003.
> >$ traceroute6 google.de
> >traceroute6 to google.de (2a00:1450:4016:804::2003) from
> >2003:de:4be0:a800:cd43:321a:ad4e:b726, 64 hops max, 12 byte packets
> >1 fritz.box 1.793 ms 1.195 ms 1.013 ms
> >2 p200300de4bbf20a80000000000000001.dip0.t-ipconnect.de 10.093 ms *
> >10.843 ms
> >3 * * *
>
> I don't have any insight, but it could be that Google is now doing the same
> thing to DTAG as it has done to Cogent for a few weeks, ie specifically ask
> its transit partners to not announce 15169 routes to AS3320, and deciding
> AS15169 now to be IPv6 Tier1, and if you don't peer with AS15169, you're not
> getting the routes.

>From https://f-lga1.f.de.net.dtag.de/index.php?pageid=lg&query=ipv6+bgp&para=2a00%3A1450%3A4016%3A804%3A%3A2003&server=194.25.0.218&EXEC=Execute

sh ipv6 bgp 2a00:1450:4016:804::2003
BGP routing table entry for 2a00:1450:4016::/48
Paths: (1 available, best #1, table Default-IP-Routing-Table)
209 15169
::ffff:194.25.5.239 from 62.154.10.67 (194.25.5.239)
Origin IGP, metric 4000000, localpref 33, valid, internal, best
Community: 3320:1840 3320:2020 64512:200
Originator: 194.25.5.239, Cluster list: 0.0.2.189
Last update: Sun Mar 6 09:42:37 2016

It is curious the local preference is not 100
Re: google<<>>Deutsche Telekom [ In reply to ]
It works again.

There was a "nice" map:

http://allestörungen.de/stoerung/google/karte/

Thanks,

Thomas Schäfer