Routingproblems - Deutsche Telekom?

[Frank Bulk]

We lost IPv6 connectivity to www.t-online.de 2:13 am US Central (20-11-2014).  I had previously gotten that fixed by working with one of their peering staff, but when I contacted him about it yesterday he said something about engineering not liking his approach.  So I suspect some kind of change was made.

Frank

-----Original Message-----
From: ipv6-ops-bounces+frnkblk=iname.com at lists.cluenet.de [mailto:ipv6-ops-bounces+frnkblk=iname.com at lists.cluenet.de] On Behalf Of Thomas Schäfer
Sent: Friday, November 21, 2014 2:10 PM
To: IPv6 Ops list
Subject: Routingproblems - Deutsche Telekom?

Hi,

today the "internetsociety" has anounced that linkedin has joined the World 
IPv6 Launch Measurements Project. So far so good (marketing).

But I was confused by using still IPv4.

This company has more than one addresses.

de.linkedin.com has no AAAA-Record. Ok, shit happens.

but www.linkedin.com has an AAAA-Record.


from home via DSL (Deutsche Telekom) I get this:

ping6 www.linkedin.com
PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
>From 2003:0:1803:8268::2 icmp_seq=3 Destination unreachable: No route
>From 2003:0:1803:8268::2 icmp_seq=7 Destination unreachable: No route
^C
--- www.linkedin.com ping statistics ---
8 packets transmitted, 0 received, +2 errors, 100% packet loss, time 16047ms

from work via LRZ/DFN I get this:

ping6 www.linkedin.com
PING www.linkedin.com(2620:109:c007:102::5be1:f881) 56 data bytes
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=1 ttl=47 time=50.4 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=2 ttl=47 time=50.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=3 ttl=47 time=50.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=4 ttl=47 time=50.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=5 ttl=47 time=50.3 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=6 ttl=47 time=50.1 ms
^C
--- www.linkedin.com ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5006ms
rtt min/avg/max/mdev = 50.199/50.293/50.446/0.158 ms

I found also some other problems in 26.... but they are not so prominent.

www.opus1.com
www.ipv6book.ca

Has anybody an idea? Can somebody confirm this problem by using a different 
isp?

Regards,
Thomas