down for 2 hours...

I did. running a tracert seems to show the problem was at secureserver.net where there were several timeouts before routing finallly went onto 68.178.232.100 (rangefinderforum.org)
Infact tracert is still showing timeouts at secureserver.net and performance is not great. They seem to have a bottleneck somewhere. They need a kick!
 
I can handle a shakeup in Washington, or even photo.net being down; but I HAVE to have my RFF connection. I start getting anxious if it doesn't come up within 5 seconds.
 
It got my standard reaction: 'bloody computers -- they all do that'.

It's better than the BBC. Whenever their site is working too well, they draft in the IT-wallahs to 'improve' it (or, as we say in English, to f*** it up).

I wrote about 3500 words today...

Cheers,

R.
 
Back
Top Bottom