Chris, thank you for checking. It is an intermittant problem. It has been fine for the last few days, but is awful at the moment.
If I ping google.com, it looks like this:
Request timed out.
Request timed out.
Reply from 172.217.0.46: bytes=32 time=87ms TTL=252
Reply from 172.217.0.46: bytes=32 time=49ms TTL=252
Reply from 172.217.0.46: bytes=32 time=30ms TTL=252
Reply from 172.217.0.46: bytes=32 time=61ms TTL=252
Reply from 172.217.0.46: bytes=32 time=53ms TTL=252
Reply from 172.217.0.46: bytes=32 time=85ms TTL=252
Reply from 172.217.0.46: bytes=32 time=29ms TTL=252
Reply from 172.217.0.46: bytes=32 time=794ms TTL=252
Reply from 172.217.0.46: bytes=32 time=47ms TTL=252
Reply from 172.217.0.46: bytes=32 time=143ms TTL=252
Request timed out.
Request timed out.
Reply from 172.217.0.46: bytes=32 time=65ms TTL=252
Reply from 172.217.0.46: bytes=32 time=148ms TTL=252
Request timed out.
Request timed out.
Reply from 172.217.0.46: bytes=32 time=113ms TTL=252
Reply from 172.217.0.46: bytes=32 time=116ms TTL=252
Reply from 172.217.0.46: bytes=32 time=35ms TTL=252
Reply from 172.217.0.46: bytes=32 time=63ms TTL=252
Reply from 172.217.0.46: bytes=32 time=152ms TTL=252
Reply from 172.217.0.46: bytes=32 time=92ms TTL=252
Reply from 172.217.0.46: bytes=32 time=125ms TTL=252
Request timed out.
Reply from 172.217.0.46: bytes=32 time=90ms TTL=252
Reply from 172.217.0.46: bytes=32 time=92ms TTL=252
Reply from 172.217.0.46: bytes=32 time=28ms TTL=252