Eddie's suggestion was my first instinct.
I'd just start with ping routine myself though.
With a couple quick tests it'll surely let you know if you are getting out, and how far.

FWIW ping has its weakpoints with cache also. I hit one today. Thought I'd ping a website to see if we were still hosting it (since response displays the IP). My system pinged our server (because it was in cache I guess)and of course our server responded since the bindings were still there. So I thought we had it. A while later a reverse lookup and whois showed me the error of my ways.
Wrong test for intended purpose on my part I guess.
But I learned today 'ping' in command line still has cache. Somehow I thought this may be relevant.


I do not work here, but the benefits are still awesome
Make your sound your own!