Is that who "QNS Trax" is?I've signed up for a monitoring service that checks it minute by minute (literally). It's documenting the whole "fine x 40" then "slow x 9" and "not found x 2" cycle. I'm hoping it will help troubleshoot the issue.
Is that who "QNS Trax" is?I've signed up for a monitoring service that checks it minute by minute (literally). It's documenting the whole "fine x 40" then "slow x 9" and "not found x 2" cycle. I'm hoping it will help troubleshoot the issue.
Is that who "QNS Trax" is?
And of course, now that you're paying for this service, the forum is behaving itself...
You do realise now, that if the forum goes tits up again, you are going to get 100% of the blame for jinxing it, right.Well, looks like as20055.net changed the routing from Seattle to Provo. Now goes through Palo Alto then to Salt Lake and we do not have the degraded stuff that was happening for the last what, 2 weeks between Yakima and Seattle. Google servers in Seattle now have no waits or other comboobulations. The google servers ...um... serve the Ads and such after your browser's page is loaded. No TLS handshake slow downs either. Bob will be happy. Of course, it is early in the am so fingers crossed.
Later
Oh probably.You do realise now, that if the forum goes tits up again, you are going to get 100% of the blame for jinxing it, right.
Well, looks like as20055.net changed the routing from Seattle to Provo. Now goes through Palo Alto then to Salt Lake and we do not have the degraded stuff that was happening for the last what, 2 weeks between Yakima and Seattle. Google servers in Seattle now have no waits or other comboobulations. The google servers ...um... serve the Ads and such after your browser's page is loaded. No TLS handshake slow downs either. Bob will be happy. Of course, it is early in the am so fingers crossed.
Later
Bob: Where is the tracking tool hosted and what is it called?It is definitely working better so far, but it’s still morning. Also, the problems seemed to be mostly at Bluehost. One of the tracking tools does a ping once a minute. Doesn’t load anything, just grabs the html code. It shows a very distinct pattern of fast/slow, which often changes by the minute. It’s not the typical “ok, the place is busy, it’s running a bit slower” you’d normally expect. It’s either nice and fast or broken.
Hmmm, I would question that 1.123 second response. I am seeing 55mS to 61mS response over 4 pings to MRF a few seconds ago. Also, everything is under 65mS with traceroute over 19 hops from me to MRF. This is a good thing!
Later