FORUM UPGRADES - COMPLETED (For real this time! I hope...)

[bnsf971]

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?

 

[bob]

Is that who "QNS Trax" is?

No, that's a member. This is simply a bot that opens the website once a minute, from varying locations, and says "Can I get there from here?" and returns the time for the reply.

 

[bnsf971]

And of course, now that you're paying for this service, the forum is behaving itself...

 

[bob]

And of course, now that you're paying for this service, the forum is behaving itself...

lol, nope. It did a real good job of documenting the fast/slow load times.

 

[D&J RailRoad]

it popped up right away that time. same with the new posts.

 

[Sirfoldalot]

Running at lighting speed at 8PM PDT?

 

[bob]

It’s running fast or not at all.
Times are like 2, 3, 2, 3, 52… it either works right away or dogs it.

 

[troyphoto]

working fast for me in Indiana (knocks wood)

 

[Colbert]

Running like a TGV in France !

 

[ctclibby]

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

 

[Smudge617]

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

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.

 

[ctclibby]

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.

Oh probably.

 

[bob]

Overnight results are good, load times consistently fast. But it seems to do that then break in the early morning. Let’s see how the day goes.

 

[bob]

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

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.

 

[ctclibby]

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.

Bob: Where is the tracking tool hosted and what is it called?

Later

 

[bob]

Pingdom. No idea where it’s located. However, they ping from around the world, using a VPN presumably. The results are consistent with that, with Japan and Australia always being slower. But when several pings in a row from different places fail or run very slow, you know there’s an issue.

 

[bob]

Pingdoms results very accurately reflect what I’m seeing as well. Here’s overnight:

Ping time in MS, lower is better.

 

[bob]

Something clearly got changed/fixed

 

[ctclibby]

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

 

[bob]

What?

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

Well, maybe that's the initial page load then, I'm really not sure, I only started using it yesterday.

I'm not as worried about the exact values, what I'm looking for is trends and wild variations. Yesterday it was bouncing all over. Now it's a nice steady trend and much lower than before. Also, most importantly of all, I'm looking for the red stripes that indicate it couldn't connect at all.