Re: strange ping and traceroute results

Heh - You _learn_ that Anycast isn't good for TCP, but LinkedIn proved differently. Their website uses TCP (obviously), works almost always, and gracefully recovers when Anycast throws a curve. There's a great interview on Packet Pushers with LinkedIn Global Engineering: Packet Pushers: Show

Re: strange ping and traceroute results

Anycast is not suitable for TCP. It IS fantastic for DNS (which uses UDP), which is the first thing a client does most of the time to find the server. Akamai control server groups by allocating per-customer per-object host names, then these can be resolved using their very highly customised DNS

Re: strange ping and traceroute results

On 22/11/16 02:19, Amos Shapira wrote: > On 21 November 2016 at 18:20, Shachar Shemesh > wrote: > > The DNS resolving google.com guesses your > gegraphical location, and gives you an answer that is nearest > where

Re: strange ping and traceroute results

On 21 November 2016 at 18:20, Shachar Shemesh wrote: > The DNS resolving google.com guesses your gegraphical location, and gives > you an answer that is nearest where you are. If you use another DNS to > query the domain, you will get a different IP: > It's not always a

Re: strange ping and traceroute results

On 20/11/16 07:01, Shlomo Solomon wrote: > When I try ping or traceroute to www.google.com, I get strange results. > Both utilities "think" that www.google.com is at 213.57.*.*, but those > addresses belong to my Internet provider - Hotnet. > > What am I missing? > > [solomon@shlomo1]$ ping

Re: strange ping and traceroute results

On Sun, 20 Nov 2016 10:18:37 +0200 shimi wrote: Thanks for your very detailed reply. As you correctly assumed, I did learn about traceroute before re-inventing the wheel, so most of what you wrote was familiar. But I didn't know about the -I parameter. traceroute -I

Re: strange ping and traceroute results

Google.com is not one computer. Google spreads their locations all over the world including pops in many ISP's. https://peering.google.com/#/ On 20 November 2016 at 19:18, shimi wrote: > > > On Sun, Nov 20, 2016 at 9:38 AM, Shlomo Solomon > wrote:

Re: strange ping and traceroute results

On Sun, Nov 20, 2016 at 9:38 AM, Shlomo Solomon wrote: > On Sun, 20 Nov 2016 08:25:18 +0200 > shimi wrote: > > > I believe it's called a CDN and/or local compute clusters and the > > purpose of it is to give you a better user experience, which is a

Re: strange ping and traceroute results

On Sun, 20 Nov 2016 08:25:18 +0200 shimi wrote: > I believe it's called a CDN and/or local compute clusters and the > purpose of it is to give you a better user experience, which is a > Good Thing (TM). > snip ... snip ... snip > > Why do you think it's a problem and are

Re: strange ping and traceroute results

On 20 Nov 2016 07:02, "Shlomo Solomon" wrote: > > When I try ping or traceroute to www.google.com, I get strange results. > Both utilities "think" that www.google.com is at 213.57.*.*, but those > addresses belong to my Internet provider - Hotnet. > > What am I missing?

Re: strange ping and traceroute results

Thanks. Any way to get around this? I just tried pinging Google-UK (www.google.co.uk) and Google-Canada (www.google.ca) and I see the same behaviour. On Sun, 20 Nov 2016 05:13:29 + Geoffrey Mendelson wrote: > Google.com resolves to addresses routed to

Re: strange ping and traceroute results

This seems to be specific to www.google.com. Other addresses work as expected. Trailing dot does not change anything. On Sun, 20 Nov 2016 05:15:04 + Daniel Shahaf wrote: > Shlomo Solomon wrote on Sun, Nov 20, 2016 at 07:01:10 +0200: > > When I try ping or

Re: strange ping and traceroute results

Shlomo Solomon wrote on Sun, Nov 20, 2016 at 07:01:10 +0200: > When I try ping or traceroute to www.google.com, I get strange results. > Both utilities "think" that www.google.com is at 213.57.*.*, but those > addresses belong to my Internet provider - Hotnet. > > What am I missing? > Try with