[tomkat]

I ran / posted tracerts on two of the debate threads, with similar results confirmed by info posted by others, and the nodes at ntt.net (mainly) and verio.net (lesser extent) have consistently been a huge drag on transit times.

. . not to mention the frequent time-outs on the Chicongo hubs

click

/.02

[mmichaels1970]

I ran / posted tracerts on two of the debate threads, with similar results confirmed by info posted by others, and the nodes at ntt.net (mainly) and verio.net (lesser extent) have consistently been a huge drag on transit times.

Which leads you to believe that this is a service provider issue rather than a server issue, correct?

A partner and I once had a server collocated at a shoddy service provider. We couldn't figure out why all of our sites and services were constantly going down and dragging. We were driving 30 minutes to the collocation site almost once a week to restart.

Eventually we changed our collocation site along with service provider. It was a real pain because we had to reroute all of our DNS traffic to a new IP range. But once we did that, the server practically ran 24/7.

We were small-scale by comparison, but once we got rid of the old service provider we felt completely relieved and the stress was dramatically reduced.

[expat1000]

Tomkat, I think the problem is FR servers. Traceroute from here (Thailand) is less than 500 milliseconds - perfectly acceptable.

Maybe there was a bottleneck before at those nodes, but it’s been like that for quite a few days, and for most of those days I time out at the site, particularly when trying to read mail or pings.