Quote Originally Posted by Appleh4x View Post
I'm not reading more into it, the SE guys didn't have me run any tests, this is what they flat out told me was the problem. My own traceroutes I have run here on the forums are fine and the ones you are referring to about other people "proving" some aren't SE's fault is BS. A 200 ms ping is 1/5 of a second. That is what cogent is giving those people, 1/5 a sec of lag. What everyone is complaining about is actually several full seconds of lag, timeouts, etc that are the fault of the server. You guys have been wrong from the start and know next to nothing about how a traceroute actually even works. I saw someone blame a lone * (timeout) as the problem in someone's traceroute, not a full timeout mind you, but 1 lone asterisk.
90000 disconnect is not the same as the lag issues. They are two separate problems.
Lag issues come from two main points: 1) Server congestion (affects most people on at the time), 2) Packet shaping (affects only people whose path is being shaped)

I'm not saying the 90000 error is never on SE's side, but in general it's not, and it's also not the same thing as the lag issues... Please understand the difference between these issues and that there are more ways than one that things can go wrong.