Giorgio, I guess as a professional I have to concede that possibility that its a coincidence

but since I don't believe in them

its hard to discount the timing. I mean I have NEVER in the past 5 years that I can recall, gotten this message once and we have been using the same provider for coming up on 4 years, but I have been getting connection timedout as a result of the issues with NS that were resolved by using other browsers, so why I figured they might be related. But, as I said, its possible I suppose, just so much of it and so suddenly.

Especially that network diagnostics internally or externally all the way to the OC3 junction reports ZERO problems and there is no log of anything wrong. No system even or firewall events either or hardware events to explain it either, so software was the only thing. If it was predictable and reproducible on specific sites, I could test with other things but its so random that I can't.

Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2