In Chrome I'm finding I often have to try two or three times to access facebook, is anyone else finding that? I asked on facebook, a few friends have said yes, fine from mobile devices but not so good from a PC/mac.
ping -t facebook.com
Pinging facebook.com [173.252.100.16] with 32 bytes of data:
Reply from 173.252.100.16: bytes=32 time=203ms TTL=241
Request timed out.
Reply from 173.252.100.16: bytes=32 time=214ms TTL=241
Reply from 173.252.100.16: bytes=32 time=205ms TTL=241
Reply from 173.252.100.16: bytes=32 time=215ms TTL=241
Request timed out.
Reply from 173.252.100.16: bytes=32 time=204ms TTL=241
Reply from 173.252.100.16: bytes=32 time=202ms TTL=241
Reply from 173.252.100.16: bytes=32 time=200ms TTL=241
Reply from 173.252.100.16: bytes=32 time=200ms TTL=241
Reply from 173.252.100.16: bytes=32 time=207ms TTL=241
Reply from 173.252.100.16: bytes=32 time=202ms TTL=241
Reply from 173.252.100.16: bytes=32 time=202ms TTL=241
Reply from 173.252.100.16: bytes=32 time=205ms TTL=241
Reply from 173.252.100.16: bytes=32 time=214ms TTL=241
Reply from 173.252.100.16: bytes=32 time=215ms TTL=241
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.252.100.16: bytes=32 time=207ms TTL=241
Reply from 173.252.100.16: bytes=32 time=205ms TTL=241
Reply from 173.252.100.16: bytes=32 time=204ms TTL=241
Reply from 173.252.100.16: bytes=32 time=201ms TTL=241
Reply from 173.252.100.16: bytes=32 time=208ms TTL=241
Ping statistics for 173.252.100.16:
Packets: Sent = 26, Received = 19, Lost = 7 (26% loss),
Approximate round trip times in milli-seconds:
Minimum = 200ms, Maximum = 215ms, Average = 205ms
Interestingly geekzone wasn't 100% either
ping -t www.geekzone.co.nz
Pinging geekzone.co.nz [202.175.128.169] with 32 bytes of data:
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=29ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=34ms TTL=120
Reply from 202.175.128.169: bytes=32 time=24ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=24ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=25ms TTL=120
Reply from 202.175.128.169: bytes=32 time=26ms TTL=120
Request timed out.
Reply from 202.175.128.169: bytes=32 time=29ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Reply from 202.175.128.169: bytes=32 time=25ms TTL=120
Reply from 202.175.128.169: bytes=32 time=24ms TTL=120
Request timed out.
Reply from 202.175.128.169: bytes=32 time=20ms TTL=120
Reply from 202.175.128.169: bytes=32 time=26ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Reply from 202.175.128.169: bytes=32 time=27ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=25ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=23ms TTL=120
Reply from 202.175.128.169: bytes=32 time=21ms TTL=120
Reply from 202.175.128.169: bytes=32 time=26ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Reply from 202.175.128.169: bytes=32 time=22ms TTL=120
Ping statistics for 202.175.128.169:
Packets: Sent = 33, Received = 31, Lost = 2 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 34ms, Average = 23ms