can't ping google (at random)

[#1]

For the past couple of weeks I've noticed an odd behavior.
I would google a string and it would spin for ages .. I'd cancel and restart and it would come back straight away.
Later still it would take maybe a dozen such restarts before it would instantly reply.
I've seen this behavior before, where routing tables have become corrupt and requests simply route to the bit bucket.
I decided to investigate:

$ nslookup google.com
Server:         127.0.0.1
Address:        127.0.0.1#53
Non-authoritative answer:
Name:   google.com
Address: 209.85.227.105
Name:   google.com
Address: 209.85.227.106
Name:   google.com
Address: 209.85.227.147
Name:   google.com
Address: 209.85.227.99
Name:   google.com
Address: 209.85.227.103
Name:   google.com
Address: 209.85.227.104

$ ping 209.85.227.105
PING 209.85.227.105 (209.85.227.105) 56(84) bytes of data.
64 bytes from 209.85.227.105: icmp_seq=1 ttl=53 time=23.9 ms
64 bytes from 209.85.227.105: icmp_seq=2 ttl=53 time=23.3 ms
 C-c C-c
--- 209.85.227.105 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1002ms
rtt min/avg/max/mdev = 23.335/23.622/23.909/0.287 ms
$ ping 209.85.227.106
PING 209.85.227.106 (209.85.227.106) 56(84) bytes of data.
 C-c C-c
--- 209.85.227.106 ping statistics ---
7 packets transmitted, 0 received, 100% packet loss, time 6000ms
$ ping 209.85.227.147
PING 209.85.227.147 (209.85.227.147) 56(84) bytes of data.
64 bytes from 209.85.227.147: icmp_seq=1 ttl=53 time=22.7 ms
64 bytes from 209.85.227.147: icmp_seq=2 ttl=53 time=22.1 ms
 C-c C-c
--- 209.85.227.147 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1005ms
rtt min/avg/max/mdev = 22.174/22.479/22.785/0.340 ms
As can be seen one of the address coming back fro Google seems to not be reachable.
So either 209.85.227.106 should not be in the list (DNS problem) or should
be there but is just not pingable from plusnet network  (and not  httpable etc)
so can other folks ping 209.85.227.106 ... can you http://209.85.227.106 ?

[#2]

Works for me.
$ ping -c 5 209.85.227.106
PING 209.85.227.106 (209.85.227.106) 56(84) bytes of data.
64 bytes from 209.85.227.106: icmp_seq=1 ttl=52 time=44.5 ms
64 bytes from 209.85.227.106: icmp_seq=2 ttl=52 time=45.0 ms
64 bytes from 209.85.227.106: icmp_seq=3 ttl=54 time=44.1 ms
64 bytes from 209.85.227.106: icmp_seq=4 ttl=54 time=44.8 ms
64 bytes from 209.85.227.106: icmp_seq=5 ttl=54 time=44.1 ms
--- 209.85.227.106 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 44.118/44.543/45.052/0.440 ms

[#3]

Works here as well:
Pinging 209.85.227.106 with 32 bytes of data:
Reply from 209.85.227.106: bytes=32 time=28ms TTL=55
Reply from 209.85.227.106: bytes=32 time=28ms TTL=55
Reply from 209.85.227.106: bytes=32 time=29ms TTL=55
Reply from 209.85.227.106: bytes=32 time=27ms TTL=55
Ping statistics for 209.85.227.106:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 27ms, Maximum = 29ms, Average = 28ms