12 hours without service

[VOIPoTim]

The ping times were accurate, I noticed the excessive delay, that's why I posted as much info as possible. Now voipo is working, as you can see from these times the speed has increased dramatically.

I did not think to capture the trace route data earlier to see if one router was causing the problem, will continue to monitor this during the next few days.

Reply from 4.2.2.3: bytes=32 time=14ms TTL=59
Reply from 4.2.2.3: bytes=32 time=14ms TTL=59
Reply from 4.2.2.3: bytes=32 time=13ms TTL=59
Reply from 4.2.2.3: bytes=32 time=13ms TTL=59

Reply from 67.111.81.6: bytes=32 time=17ms TTL=52
Reply from 67.111.81.6: bytes=32 time=17ms TTL=52
Reply from 67.111.81.6: bytes=32 time=17ms TTL=52
Reply from 67.111.81.6: bytes=32 time=19ms TTL=52

That looks a lot better. It sounds like something was definitely causing the delay. We see that kind of thing a lot with newer advanced routers which analyze/rewrite all the traffic that goes through them.

Hopefully it's resolved for you.

[patoka]

Think I found the problem, Carbonite.

My ping time went from the times in my earlier post to 500+ ms again, noticed heavy outbound traffic in the router and disabled Carbonite for 10 min, ping times dropped immediately.

I'm going to work on QOS and prioritizing traffic in the morning to see if either choking Carbonite back or giving the Voipo ports higher priority works best.

Might be worth adding Carbonite / Mozy to your troubleshooting list.