[7355608]

Well that's fine and dandy for him to say, except for 1 tiny problem with that theory.... I don't get that choke. So if it was a hardware issue, everyone would have that same issue, not just you. Really he should've explained that to you.

Choke can be caused by a number of things. If it was packetloss I would say, ya it's prolly a network issue. Choke is more like throttling. Like the server is sending you 100 packets, but your pc is only handling 70 of them properly. Check your rates, make sure the cl_updaterate and cl_cmdrate are set to 66 or 67. Next is to disable vsync. With vsync on it will limit your fps to your desktop refresh rate. This is known to cause choke, as well as bad fps, stuttering visuals, etc. The only advantage to vsync is no image tearing.

Now choke can also work the reverse. The server is sending you 30 packets and you're expecting 100. That should only happen if the server is lagging badly, in which case (once again) this would affect everyone.

Have you done anything to your CSS or your pc recently (or around when this started)?

The only other thing that I can think of, is that the route that your taking is not very efficient. I don't think there's much of anything that can be done about it tho. I don't know who controls the routing, or how it's managed. It sounds to me like it's sending your signal to alaska then back to ny.