3 ms·

Comcast in Northern NJ USA about 45 MI from NYC $ 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=56 time

Comcast in Northern NJ USA about 45 MI from NYC $ 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=56 time=10.8 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=56 time=11.3 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=56 time=10.7 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=56 time=10.9 ms 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=60 time=10.7 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=60 time=11.3 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=60 time=11.1 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=60 time=10.5 ms

Nition 9y ago
From a residential connection in New Zealand: $ ping 1.1.1.1 Pinging 1.1.1.1 with 32 bytes of data: Reply from 1.1.1.1: bytes=32 time=4ms TTL=60 Reply from 1.1.1.1: bytes=32 time=4ms TTL=60 Reply from 1.1.1.1: bytes=32 time=4ms TTL=60 Reply from 1.1.1.1: bytes=32 time=4ms TTL=60 $ ping 8.8.8.8 Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=27ms TTL=60 Reply from 8.8.8.8: bytes=32 time=27ms TTL=60 Reply from 8.8.8.8: bytes=32 time=27ms TTL=60 Reply from 8.8.8.8: bytes=32 time=28ms TTL=60 Seems that 1.1.1.1 is even faster than my local ISP's primary DNS: $ ping 202.180.64.10 Pinging 202.180.64.10 with 32 bytes of data: Reply from 202.180.64.10: bytes=32 time=11ms TTL=61 Reply from 202.180.64.10: bytes=32 time=11ms TTL=61 Reply from 202.180.64.10: bytes=32 time=11ms TTL=61 Reply from 202.180.64.10: bytes=32 time=11ms TTL=61
- RantyDave 9y ago
  Four! I'm getting 14 from fibre in Wellington. Google are 35 ish.
- lancewiggs 9y ago
  Residential in Auckland, NZ (Vibe, UFB) 64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=0.966 ms Outstanding. 64 bytes from 8.8.8.8: icmp_seq=0 ttl=59 time=25.478 ms Not so great.
- spludge 9y ago
  Fastest Bigpipe residential connection available in the middle of Auckland: $ ping -c 4 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=56 time=29.0 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=56 time=27.7 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=56 time=30.5 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=56 time=28.6 ms --- 1.1.1.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 27.731/28.993/30.573/1.028 ms $ ping -c 4 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=55 time=27.7 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=30.7 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=28.5 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=30.6 ms --- 8.8.8.8 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 27.772/29.409/30.710/1.280 ms I'm starting to feel I should change ISPs...
  - mwilcox 9y ago
    On WiFi in Cambridge NZ 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=59 time=7.65 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=8.53 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=10.2 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=8.04 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=59 time=7.92 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=59 time=7.85 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=59 time=7.88 ms 64 bytes from 1.1.1.1: icmp_seq=8 ttl=59 time=7.73 ms 64 bytes from 1.1.1.1: icmp_seq=9 ttl=59 time=7.73 ms
  - michaelmurfy 9y ago
    BigPipe, Spark, Skinny and Vodafone don't believe in peering and thus don't peer with Cloudflare at APE. If you wanted the best performance then 2degrees, Orcon, Voyager or Slingshot are the best for this since they peer.
    - gunkaaa 9y ago
      Vodafone have come to the party and are on AKL-IX now.

Nition 9y ago

From a residential connection in New Zealand: $ ping 1.1.1.1 Pinging 1.1.1.1 with 32 bytes of data: Reply from 1.1.1.1: bytes=32 time=4ms TTL=60 Reply from 1.1.1.1: bytes=32 time=4ms TTL=60 Reply from 1.1.1.1: bytes=32 time=4ms TTL=60 Reply from 1.1.1.1: bytes=32 time=4ms TTL=60 $ ping 8.8.8.8 Pinging 8.8.8.8 with 32 bytes of data: Reply from 8.8.8.8: bytes=32 time=27ms TTL=60 Reply from 8.8.8.8: bytes=32 time=27ms TTL=60 Reply from 8.8.8.8: bytes=32 time=27ms TTL=60 Reply from 8.8.8.8: bytes=32 time=28ms TTL=60 Seems that 1.1.1.1 is even faster than my local ISP's primary DNS: $ ping 202.180.64.10 Pinging 202.180.64.10 with 32 bytes of data: Reply from 202.180.64.10: bytes=32 time=11ms TTL=61 Reply from 202.180.64.10: bytes=32 time=11ms TTL=61 Reply from 202.180.64.10: bytes=32 time=11ms TTL=61 Reply from 202.180.64.10: bytes=32 time=11ms TTL=61

RantyDave 9y ago
Four! I'm getting 14 from fibre in Wellington. Google are 35 ish.
lancewiggs 9y ago
Residential in Auckland, NZ (Vibe, UFB) 64 bytes from 1.1.1.1: icmp_seq=0 ttl=60 time=0.966 ms Outstanding. 64 bytes from 8.8.8.8: icmp_seq=0 ttl=59 time=25.478 ms Not so great.
spludge 9y ago
Fastest Bigpipe residential connection available in the middle of Auckland: $ ping -c 4 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=56 time=29.0 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=56 time=27.7 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=56 time=30.5 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=56 time=28.6 ms --- 1.1.1.1 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3004ms rtt min/avg/max/mdev = 27.731/28.993/30.573/1.028 ms $ ping -c 4 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=55 time=27.7 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=55 time=30.7 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=55 time=28.5 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=55 time=30.6 ms --- 8.8.8.8 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3005ms rtt min/avg/max/mdev = 27.772/29.409/30.710/1.280 ms I'm starting to feel I should change ISPs...
- mwilcox 9y ago
  On WiFi in Cambridge NZ 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=59 time=7.65 ms 64 bytes from 1.1.1.1: icmp_seq=2 ttl=59 time=8.53 ms 64 bytes from 1.1.1.1: icmp_seq=3 ttl=59 time=10.2 ms 64 bytes from 1.1.1.1: icmp_seq=4 ttl=59 time=8.04 ms 64 bytes from 1.1.1.1: icmp_seq=5 ttl=59 time=7.92 ms 64 bytes from 1.1.1.1: icmp_seq=6 ttl=59 time=7.85 ms 64 bytes from 1.1.1.1: icmp_seq=7 ttl=59 time=7.88 ms 64 bytes from 1.1.1.1: icmp_seq=8 ttl=59 time=7.73 ms 64 bytes from 1.1.1.1: icmp_seq=9 ttl=59 time=7.73 ms
- michaelmurfy 9y ago
  BigPipe, Spark, Skinny and Vodafone don't believe in peering and thus don't peer with Cloudflare at APE. If you wanted the best performance then 2degrees, Orcon, Voyager or Slingshot are the best for this since they peer.
  - gunkaaa 9y ago
    Vodafone have come to the party and are on AKL-IX now.