Hi Michel. I'm with you.
Since the beggining I said that I believe that is a route problem somewhere.
If it's a problem at UT it should manifest for most users and it should be noticed
at your system administration. These kind of issues are, at 99,9%, routing
problems.
I have similar problems with other sites, but no problem with UT.

>>I certainly understand the dilemma -- if you can't replicate it, you can't fix it. But if you came to my office (or Mike's, for that matter), you would certainly see this happen many times an hour. I use Firefox, but I don't think the browser matters. All other sites respond very fast even while UT is spinning its wheels endlessly. I have no idea what this could be, but there is some SERIOUS random latency going on somewhere in your system -- and I don't say this lightly, because I have verified continued crisp responsiveness while UT is stuck somehow.
>
>No, the browser is certainly not a factor. But, we have seen situations in the past where such situation was running for months and it turned out to be a bad routing issue on a specific part of the world. If I recall correctly, I have also seen a situation where our site was not even visible from a specific location and the user thought we were offline. That was also caused by something like that.