5 ms·

Ping from University of Rochester, over wifi: Cloudflare: 64 bytes from 1.1.1.1: icmp_seq=0 ttl=128 time=2 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=128 ti

Ping from University of Rochester, over wifi: Cloudflare: 64 bytes from 1.1.1.1: icmp_seq=0 ttl=128 time=2 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=128 time=2 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=128 time=2 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=128 time=9 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=128 time=2 ms Google: 64 bytes from 8.8.8.8: icmp_seq=0 ttl=54 time=12 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=11 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=54 time=13 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=54 time=45 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=54 time=14 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=54 time=11 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=54 time=34 ms Quad9: 64 bytes from 9.9.9.9: icmp_seq=0 ttl=53 time=10 ms 64 bytes from 9.9.9.9: icmp_seq=1 ttl=53 time=69 ms 64 bytes from 9.9.9.9: icmp_seq=2 ttl=53 time=14 ms 64 bytes from 9.9.9.9: icmp_seq=3 ttl=53 time=58 ms 64 bytes from 9.9.9.9: icmp_seq=4 ttl=53 time=52 ms One thing I noticed is that when I first pinged 1.1.1.1 I got 14ms, which then quickly dropped to ~3ms consistently: 64 bytes from 1.1.1.1: icmp_seq=0 ttl=128 time=14 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=128 time=14 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=128 time=2 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=128 time=3 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=128 time=1 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=128 time=4 ms

Tree1993 9y ago
Beijing: PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=52 time=241.529 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=318.034 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=337.291 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=255.748 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=52 time=247.765 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=52 time=235.611 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=52 time=239.427 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=52 time=247.911 ms 64 bytes from 1.1.1.1: icmp_seq=8 ttl=52 time=260.911 ms 64 bytes from 1.1.1.1: icmp_seq=9 ttl=52 time=281.153 ms 64 bytes from 1.1.1.1: icmp_seq=10 ttl=52 time=300.363 ms 64 bytes from 1.1.1.1: icmp_seq=11 ttl=52 time=234.296 ms
- bgdkbtv 9y ago
  Australia :( 64 bytes from 1.1.1.1: icmp_seq=0 ttl=57 time=17.580 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=18.025 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=17.780 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=18.231 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=17.906 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=57 time=18.447 ms
  - marcus_holmes 9y ago
    Cambodia - crappy office wifi PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=59 time=22.806 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=23.321 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=24.379 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=25.869 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=24.485 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=59 time=24.165 ms PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=57 time=23.005 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=22.867 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=24.461 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=23.680 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=35.581 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=21.033 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=57 time=41.634 ms
    - kukkukb 9y ago
      Johannesburg, South Africa. 100mb/s home fibre: ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=1.36 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=1.32 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=1.34 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=1.38 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=58 time=1.37 ms ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=1.33 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=1.38 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=1.35 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=1.36 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=1.35 ms
  - brod 9y ago
    Melbourne, Australia :) PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=5.044 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=6.447 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=6.371 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=6.308 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=7.317 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=5.989 ms
- oldsharp 9y ago
  Hangzhou: $ ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 Request timeout for icmp_seq 6 Request timeout for icmp_seq 7 Request timeout for icmp_seq 8 Request timeout for icmp_seq 9 Request timeout for icmp_seq 10 $ ping 1.0.0.1 PING 1.0.0.1 (1.0.0.1): 56 data bytes 64 bytes from 1.0.0.1: icmp_seq=0 ttl=50 time=167.359 ms 64 bytes from 1.0.0.1: icmp_seq=1 ttl=50 time=165.791 ms 64 bytes from 1.0.0.1: icmp_seq=2 ttl=50 time=165.846 ms 64 bytes from 1.0.0.1: icmp_seq=3 ttl=50 time=166.755 ms 64 bytes from 1.0.0.1: icmp_seq=4 ttl=50 time=166.694 ms 64 bytes from 1.0.0.1: icmp_seq=5 ttl=50 time=166.088 ms 64 bytes from 1.0.0.1: icmp_seq=6 ttl=50 time=166.460 ms 64 bytes from 1.0.0.1: icmp_seq=7 ttl=50 time=166.668 ms 64 bytes from 1.0.0.1: icmp_seq=8 ttl=50 time=166.753 ms 64 bytes from 1.0.0.1: icmp_seq=9 ttl=50 time=165.670 ms 64 bytes from 1.0.0.1: icmp_seq=10 ttl=50 time=166.816 ms Seem not China friendly :-(
- anielsen 9y ago
  Copenhagen: PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=55 time=14.053 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=12.715 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=13.615 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=14.018 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=12.261 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=11.428 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=11.950 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=13.034 ms 64 bytes from 1.1.1.1: icmp_seq=8 ttl=55 time=13.679 ms 64 bytes from 1.1.1.1: icmp_seq=9 ttl=55 time=12.415 ms 64 bytes from 1.1.1.1: icmp_seq=10 ttl=55 time=12.088 ms
  - MarcysVonEylau 9y ago
    Pinging 1.1.1.1 with 32 bytes of data: Reply from 89.228.6.1: Destination net unreachable. Reply from 89.228.6.1: Destination net unreachable. Reply from 89.228.6.1: Destination net unreachable. Reply from 89.228.6.1: Destination net unreachable. Any idea why my ISP redirects this IP?
    - rashomon 9y ago
      Maybe an advertisement re-direct for NXDOMAINS?
  - deleted 9y ago
    [deleted]
- karthikkolli 9y ago
  PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=61 time=15.860 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=61 time=15.799 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=61 time=15.616 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=61 time=15.769 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=61 time=15.431 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=61 time=16.459 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=61 time=15.860 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=61 time=15.930 ms
shaklee3 9y ago
It might be your isp caching the DNS in a local data center after you first request it
- jasongill 9y ago
  There is no DNS involved when you're connecting directly to an IP address
  - rootusrootus 9y ago
    Unless you tell it not to, ping will try a reverse lookup on the IP you are pinging in order to display that to you in the output. It's a good idea to keep that in mind when you ping something, especially if you notice the first ping is abnormally slow.
    - dingo_bat 9y ago
      That reverse lookup time is not counted in the first ping.
      - rootusrootus 9y ago
        Perhaps that depends on operating system. In the 30 years I have been using ping on Linux, the reverse lookup time is absolutely included in the first ping time.
        dingo_bat 9y ago
        If true, that's a bug. Edit: Assuming this is the right file: https://github.com/iputils/iputils/blob/master/ping.c https://github.com/iputils/iputils/blob/master/ping.c, I don't see the reverse lookup code anywhere. But then I'm not the most proficient in reading linux code.
dannyw 9y ago
It could be a technique they use to filter out all the junk traffic.
tayo42 9y ago
Something interesting I saw pointed out on the reddit thread about this is the ttl between 1.1.1.1 and 8.8.8.8 is the ttl is way different. Your pings also have the same thing showing up 128 vs 53. I tried on my laptop and get something simmilar. traceroute to 1.1.1.1 is 1 hop which is wrong. 1.0.0.1 shows a few hops. `dig google.com @1.1.1.1` doesn't work for me.
alea12 9y ago
From Tokyo, Japan: $ ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=58 time=111.781 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=102.982 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=102.206 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=110.135 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=110.085 ms $ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=58 time=6.886 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=5.475 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=5.674 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=5.557 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=58 time=7.066 ms $ ping 9.9.9.9 PING 9.9.9.9 (9.9.9.9): 56 data bytes 64 bytes from 9.9.9.9: icmp_seq=0 ttl=58 time=5.880 ms 64 bytes from 9.9.9.9: icmp_seq=1 ttl=58 time=5.534 ms 64 bytes from 9.9.9.9: icmp_seq=2 ttl=58 time=5.251 ms 64 bytes from 9.9.9.9: icmp_seq=3 ttl=58 time=5.194 ms 64 bytes from 9.9.9.9: icmp_seq=4 ttl=58 time=5.698 ms
6t6t6t6 9y ago
Tokyo, domestic 2Gbps FO but connected through Wifi: PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=57 time=5.531 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=4.420 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=5.450 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=5.438 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=4.231 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=57 time=5.933 ms PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=57 time=6.440 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=4.574 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=4.684 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=4.992 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=5.942 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=5.955 ms

Tree1993 9y ago

Beijing: PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=52 time=241.529 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=52 time=318.034 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=52 time=337.291 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=52 time=255.748 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=52 time=247.765 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=52 time=235.611 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=52 time=239.427 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=52 time=247.911 ms 64 bytes from 1.1.1.1: icmp_seq=8 ttl=52 time=260.911 ms 64 bytes from 1.1.1.1: icmp_seq=9 ttl=52 time=281.153 ms 64 bytes from 1.1.1.1: icmp_seq=10 ttl=52 time=300.363 ms 64 bytes from 1.1.1.1: icmp_seq=11 ttl=52 time=234.296 ms

bgdkbtv 9y ago
Australia :( 64 bytes from 1.1.1.1: icmp_seq=0 ttl=57 time=17.580 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=18.025 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=17.780 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=18.231 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=17.906 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=57 time=18.447 ms
- marcus_holmes 9y ago
  Cambodia - crappy office wifi PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=59 time=22.806 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=59 time=23.321 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=24.379 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=25.869 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=24.485 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=59 time=24.165 ms PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=57 time=23.005 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=22.867 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=24.461 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=23.680 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=35.581 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=21.033 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=57 time=41.634 ms
  - kukkukb 9y ago
    Johannesburg, South Africa. 100mb/s home fibre: ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data. 64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=1.36 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=1.32 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=1.34 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=1.38 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=58 time=1.37 ms ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=56 time=1.33 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=56 time=1.38 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=56 time=1.35 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=56 time=1.36 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=56 time=1.35 ms
- brod 9y ago
  Melbourne, Australia :) PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=5.044 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=60 time=6.447 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=60 time=6.371 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=60 time=6.308 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=60 time=7.317 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=60 time=5.989 ms
oldsharp 9y ago
Hangzhou: $ ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 Request timeout for icmp_seq 5 Request timeout for icmp_seq 6 Request timeout for icmp_seq 7 Request timeout for icmp_seq 8 Request timeout for icmp_seq 9 Request timeout for icmp_seq 10 $ ping 1.0.0.1 PING 1.0.0.1 (1.0.0.1): 56 data bytes 64 bytes from 1.0.0.1: icmp_seq=0 ttl=50 time=167.359 ms 64 bytes from 1.0.0.1: icmp_seq=1 ttl=50 time=165.791 ms 64 bytes from 1.0.0.1: icmp_seq=2 ttl=50 time=165.846 ms 64 bytes from 1.0.0.1: icmp_seq=3 ttl=50 time=166.755 ms 64 bytes from 1.0.0.1: icmp_seq=4 ttl=50 time=166.694 ms 64 bytes from 1.0.0.1: icmp_seq=5 ttl=50 time=166.088 ms 64 bytes from 1.0.0.1: icmp_seq=6 ttl=50 time=166.460 ms 64 bytes from 1.0.0.1: icmp_seq=7 ttl=50 time=166.668 ms 64 bytes from 1.0.0.1: icmp_seq=8 ttl=50 time=166.753 ms 64 bytes from 1.0.0.1: icmp_seq=9 ttl=50 time=165.670 ms 64 bytes from 1.0.0.1: icmp_seq=10 ttl=50 time=166.816 ms Seem not China friendly :-(
anielsen 9y ago
Copenhagen: PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=55 time=14.053 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=55 time=12.715 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=55 time=13.615 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=55 time=14.018 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=55 time=12.261 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=55 time=11.428 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=55 time=11.950 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=55 time=13.034 ms 64 bytes from 1.1.1.1: icmp_seq=8 ttl=55 time=13.679 ms 64 bytes from 1.1.1.1: icmp_seq=9 ttl=55 time=12.415 ms 64 bytes from 1.1.1.1: icmp_seq=10 ttl=55 time=12.088 ms
- MarcysVonEylau 9y ago
  Pinging 1.1.1.1 with 32 bytes of data: Reply from 89.228.6.1: Destination net unreachable. Reply from 89.228.6.1: Destination net unreachable. Reply from 89.228.6.1: Destination net unreachable. Reply from 89.228.6.1: Destination net unreachable. Any idea why my ISP redirects this IP?
  - rashomon 9y ago
    Maybe an advertisement re-direct for NXDOMAINS?
- deleted 9y ago
  [deleted]
karthikkolli 9y ago
PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=61 time=15.860 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=61 time=15.799 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=61 time=15.616 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=61 time=15.769 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=61 time=15.431 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=61 time=16.459 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=61 time=15.860 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=61 time=15.930 ms

shaklee3 9y ago

It might be your isp caching the DNS in a local data center after you first request it

jasongill 9y ago
There is no DNS involved when you're connecting directly to an IP address
- rootusrootus 9y ago
  Unless you tell it not to, ping will try a reverse lookup on the IP you are pinging in order to display that to you in the output. It's a good idea to keep that in mind when you ping something, especially if you notice the first ping is abnormally slow.
  - dingo_bat 9y ago
    That reverse lookup time is not counted in the first ping.
    - rootusrootus 9y ago
      Perhaps that depends on operating system. In the 30 years I have been using ping on Linux, the reverse lookup time is absolutely included in the first ping time.
      - dingo_bat 9y ago
        If true, that's a bug. Edit: Assuming this is the right file: https://github.com/iputils/iputils/blob/master/ping.c https://github.com/iputils/iputils/blob/master/ping.c, I don't see the reverse lookup code anywhere. But then I'm not the most proficient in reading linux code.

dannyw 9y ago

It could be a technique they use to filter out all the junk traffic.

tayo42 9y ago

Something interesting I saw pointed out on the reddit thread about this is the ttl between 1.1.1.1 and 8.8.8.8 is the ttl is way different. Your pings also have the same thing showing up 128 vs 53. I tried on my laptop and get something simmilar. traceroute to 1.1.1.1 is 1 hop which is wrong. 1.0.0.1 shows a few hops. `dig google.com @1.1.1.1` doesn't work for me.

alea12 9y ago

From Tokyo, Japan: $ ping 1.1.1.1 PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=58 time=111.781 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=58 time=102.982 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=58 time=102.206 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=58 time=110.135 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=58 time=110.085 ms $ ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=58 time=6.886 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=58 time=5.475 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=58 time=5.674 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=58 time=5.557 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=58 time=7.066 ms $ ping 9.9.9.9 PING 9.9.9.9 (9.9.9.9): 56 data bytes 64 bytes from 9.9.9.9: icmp_seq=0 ttl=58 time=5.880 ms 64 bytes from 9.9.9.9: icmp_seq=1 ttl=58 time=5.534 ms 64 bytes from 9.9.9.9: icmp_seq=2 ttl=58 time=5.251 ms 64 bytes from 9.9.9.9: icmp_seq=3 ttl=58 time=5.194 ms 64 bytes from 9.9.9.9: icmp_seq=4 ttl=58 time=5.698 ms

6t6t6t6 9y ago

Tokyo, domestic 2Gbps FO but connected through Wifi: PING 1.1.1.1 (1.1.1.1): 56 data bytes 64 bytes from 1.1.1.1: icmp_seq=0 ttl=57 time=5.531 ms 64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=4.420 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=5.450 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=5.438 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=57 time=4.231 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=57 time=5.933 ms PING 8.8.8.8 (8.8.8.8): 56 data bytes 64 bytes from 8.8.8.8: icmp_seq=0 ttl=57 time=6.440 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=57 time=4.574 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=57 time=4.684 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=57 time=4.992 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=57 time=5.942 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=57 time=5.955 ms