Routingproblems - Deutsche Telekom?

[Grant Ridder]

Sent off to the right people LinkedIn

-Grant

On Fri, Nov 21, 2014 at 3:34 PM, Andre Grueneberg <
list.ipv6ops at grueneberg.de> wrote:

> Thomas Schäfer wrote:
> > 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
> > Has anybody an idea? Can somebody confirm this problem by using a
> different
> > isp?
>
> This might be caused by rather strict route filters based on IRR at
> AS3320 (DTAG). We also don't see this route via our AS3320 transit.
>
> I see the following pathes:
> ... 1273 14413 197612
> ... 1299 14413 197612
> ... 6939 14413 197612
>
> $ whois -h whois.ra.net AS-LINKEDIN
> as-set:         AS-LINKEDIN
> ...
> members:        AS13443
> ...
>
> Other IPv6 routes of LinkedIn are visible via AS3320:
>        2620:109:c006::/48 <neigh> 10         100        0      E
>          AS_PATH: 3320 2914 14413 55163
>        2620:109:c00d::/48 <neigh> 10         100        0      E
>          AS_PATH: 3320 2914 14413 20049
>
> Not feeding IRR DB fires back. You might want to ask LinkedIn to fix
> their entries.
>
> Andre
> --
> Be nice to your kids.  They'll choose your nursing home.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cluenet.de/pipermail/ipv6-ops/attachments/20141121/14e6e076/attachment.htm>