Seem to be experiencing some network blips for the last 10 minutes - intermittent and short, but uncommon here.

Here's a traceroute from my houston server to my dallas server

traceroute to 70.86.111.xxx 30 hops max, 40 byte packets
1 * * *
2 et4-1.ibr02.hstntx2.theplanet.com (74.55.252.97) 0.386 ms 0.414 ms 0.419 ms
3 et3-1.ibr01.hstntx2.theplanet.com (70.87.253.166) 0.292 ms 0.301 ms *
4 * * *
5 * * *
6 * * *
7 * * *
8 removed-for-forum-post.111.86.70.in-addr.arpa (70.86.111.xxx) 8.870 ms 11.004 ms *

Got external monitoring alerts:
1 Jul 2009, 07:15PM EDT.
1 Jul 2009, 08:30PM EDT.
1 Jul 2009, 08:55PM EDT.

(each up at the next 5 minute interval)

Put in ticket 5831364PLNT with another traceroute just as an advisory

6 145 ms 158 ms 161 ms te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]
7 * * * Request timed out.
8 204 ms 223 ms 172 ms po2.car06.dllstx5.theplanet.com [70.87.254.46]
9 * * * Request timed out.
10 * * * Request timed out.

OK for the moment, but have seen a few of these blips so far tonight so thought it was worth noting.

I had a drop in H2 around 2:06 PM CST today but it was only short enough to set off one of my alerts within a 5 minute interval. Could have been something else too.

No issue for me in H2 in relation to your monitor time stamps.

I have a stable connection to 70.87.254.46 .

Thanks ajz. I haven't experienced any further issues after 9:00. Tech support said there were no other reports in area tonight. Weird. I was logged in via ssh during one "blip" and it just paused up (didn't accept my next character as I typed for a minute, then it just returned to normal (didn't disconnect... was just a l-o-n-g pause in typing.) Server load was normal, etc. They said it was normal for the switches to timeout during traceroute, but it sure looked atypical to me to see all the timeouts before reaching my server.

Will post if I encounter this again. Hopefully not though as I prefer the normal smooth sailing