Routingproblems - Deutsche Telekom?

[Jan Hugo Prins]

www.linkedin.com is an alias for pop-idb2-alpha.www.linkedin.com.
pop-idb2-alpha.www.linkedin.com has address 91.225.248.129
pop-idb2-alpha.www.linkedin.com has IPv6 address 
2620:109:c007:102::5be1:f881


NetRange:       2620:109:C000:: - 2620:109:C00F:FFFF:FFFF:FFFF:FFFF:FFFF
CIDR:           2620:109:C000::/44
NetName:        LINKEDIN
NetHandle:      NET6-2620-109-C000-1
Parent:         ARIN-V6-ENDUSER-BLOCK (NET6-2620-1)
NetType:        Direct Assignment
OriginAS:       AS20049
Organization:   LinkedIn Corporation (LINKE-1)
RegDate:        2012-01-12
Updated:        2012-02-08
Ref: http://whois.arin.net/rest/net/NET6-2620-109-C000-1

bgp01.as48972.net# sh ipv6 bgp regexp _20049$
BGP table version is 0, local router ID is 95.130.232.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - 
internal,
               r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete

    Network          Next Hop            Metric LocPrf Weight Path
*  2620:109:c00d::/48
                     2001:1540:800:4000::2:1
                                                    90      0 16243 6939 
14413 20049 i
* i                 2a02:d28:5580:e:1000::221
                                                    90      0 5580 3356 
14413 20049 i
*>                  2a02:d28:5580:e:1000::b5
                                                    90      0 5580 3356 
14413 20049 i

Total number of prefixes 1

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=56 time=20.1 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=2 ttl=56 time=20.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=3 ttl=56 time=20.0 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=4 ttl=56 time=20.3 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=5 ttl=56 time=20.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=6 ttl=56 time=20.1 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=7 ttl=56 time=20.1 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=8 ttl=56 time=20.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=9 ttl=56 time=20.2 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=10 ttl=56 time=20.0 ms
64 bytes from 2620:109:c007:102::5be1:f881: icmp_seq=11 ttl=56 time=20.4 ms
^C
--- www.linkedin.com ping statistics ---
11 packets transmitted, 11 received, 0% packet loss, time 10013ms
rtt min/avg/max/mdev = 20.067/20.215/20.435/0.135 ms


On 11/21/2014 09:09 PM, Thomas Schäfer wrote:
> 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
>
>
>
>
>
>
>   
>
>