4 ms·

It's not only about connection speed but also about infrastructure. If you look at this map https://cloud.google.com/about/locations/ https://cloud.google.com/a

by tangue 10y ago

It's not only about connection speed but also about infrastructure. If you look at this map https://cloud.google.com/about/locations/ https://cloud.google.com/about/locations/ you'll see that your packets have a looong way to reach their data center. AWS is no better than Google on this point. Guess it's not bankable

witty_username 10y ago
That only adds about 200-300ms RTT I'd guess. I live in India and use many websites which are hosted in the US, and they work fine.
- estsauver 10y ago
  (Hello from Kenya) There are usually CDN nodes in India. Cloudfront has edge nodes there, google's cdn does. There's also a Mumbai AWS datacentre. When you get far away from the common edges, it gets real noticeable.
  - witty_username 10y ago
    ~$ ping imgur.com PING imgur.com (151.101.40.193) 56(84) bytes of data. 64 bytes from 151.101.40.193 (151.101.40.193): icmp_seq=1 ttl=53 time=342 ms imgur.com works fine ~$ ping python.org PING python.org (23.253.135.79) 56(84) bytes of data. 64 bytes from 23.253.135.79 (23.253.135.79): icmp_seq=1 ttl=48 time=267 ms python.org works fine news.ycombinator.com and reddit.com also works fine even though I'm logged in (there's about a 300ms, 700ms delay in the Network tab of Chrome's devtools for news.ycombinator.com and reddit.com)
    - tangue 10y ago
      PING imgur.com (151.101.12.193): 56 data bytes 64 bytes from 151.101.12.193: icmp_seq=3 ttl=51 time=499.633 ms 64 bytes from 151.101.12.193: icmp_seq=65 ttl=51 time=330.021 ms 64 bytes from 151.101.12.193: icmp_seq=66 ttl=51 time=557.491 ms 64 bytes from 151.101.12.193: icmp_seq=67 ttl=51 time=478.380 ms 64 bytes from 151.101.12.193: icmp_seq=68 ttl=51 time=400.365 ms Request timeout for icmp_seq 69 PING python.org (23.253.135.79): 56 data bytes 64 bytes from 23.253.135.79: icmp_seq=0 ttl=44 time=615.871 ms 64 bytes from 23.253.135.79: icmp_seq=1 ttl=44 time=539.681 ms I'm on an island lost in the middle of the Indian Ocean. But ping weren't that different (50 ms more or less) on the continent (I went to RSA and Namibia)

by tangue 10y ago

witty_username 10y ago

That only adds about 200-300ms RTT I'd guess. I live in India and use many websites which are hosted in the US, and they work fine.

estsauver 10y ago
(Hello from Kenya) There are usually CDN nodes in India. Cloudfront has edge nodes there, google's cdn does. There's also a Mumbai AWS datacentre. When you get far away from the common edges, it gets real noticeable.
- witty_username 10y ago
  ~$ ping imgur.com PING imgur.com (151.101.40.193) 56(84) bytes of data. 64 bytes from 151.101.40.193 (151.101.40.193): icmp_seq=1 ttl=53 time=342 ms imgur.com works fine ~$ ping python.org PING python.org (23.253.135.79) 56(84) bytes of data. 64 bytes from 23.253.135.79 (23.253.135.79): icmp_seq=1 ttl=48 time=267 ms python.org works fine news.ycombinator.com and reddit.com also works fine even though I'm logged in (there's about a 300ms, 700ms delay in the Network tab of Chrome's devtools for news.ycombinator.com and reddit.com)
  - tangue 10y ago
    PING imgur.com (151.101.12.193): 56 data bytes 64 bytes from 151.101.12.193: icmp_seq=3 ttl=51 time=499.633 ms 64 bytes from 151.101.12.193: icmp_seq=65 ttl=51 time=330.021 ms 64 bytes from 151.101.12.193: icmp_seq=66 ttl=51 time=557.491 ms 64 bytes from 151.101.12.193: icmp_seq=67 ttl=51 time=478.380 ms 64 bytes from 151.101.12.193: icmp_seq=68 ttl=51 time=400.365 ms Request timeout for icmp_seq 69 PING python.org (23.253.135.79): 56 data bytes 64 bytes from 23.253.135.79: icmp_seq=0 ttl=44 time=615.871 ms 64 bytes from 23.253.135.79: icmp_seq=1 ttl=44 time=539.681 ms I'm on an island lost in the middle of the Indian Ocean. But ping weren't that different (50 ms more or less) on the continent (I went to RSA and Namibia)