How to Diagnose Lag and Rubberbanding
View Single Post
Join Date: Jun 2012
01-12-2013, 08:28 AM
Originally Posted by
te0-2-0-2.ccr22.lpl01.atlas.cogentco.com (126.96.36.199) 95.251 ms te0-2-0-7.ccr21.lpl01.atlas.cogentco.com (188.8.131.52) 97.377 ms
12 te0-1-0-3.ccr21.bos01.atlas.cogentco.com (184.108.40.206) 153.103 ms
te0-1-0-5.ccr22.lpl01.atlas.cogentco.com (220.127.116.11) 74.971 ms te0-6-0-4.ccr21.bos01.atlas.cogentco.com (18.104.22.168) 153.896 ms
13 te4-2.ccr01.bos06.atlas.cogentco.com (22.214.171.124) 150.692 ms te3-4.ccr01.bos06.atlas.cogentco.com (126.96.36.199) 153.652 ms 153.478 ms
14 188.8.131.52 (184.108.40.206) 149.651 ms 149.672 ms 150.059 ms
15 220.127.116.11 (18.104.22.168) 152.882 ms 153.226 ms 173.113 ms
So you're showing the same congestion at the Cogent Communications Boston hub that many other posters in this thread are showing... (But not everyone has this problem... Connecting from the Silicon Valley, I myself have only suffered barely noticeable lag and a occasional Server DC...) The next question to ask is have you tried using the US Proxy setting in the Launcher, as many users have reported good results with this...
As far as Cogent Communications, and other Internet Backbone providers are concerned, performance is a growing concern. But with the infrastructure damage caused by Hurricane Sandy, plus the growing demand for bandwidth, (with Netflix video streaming taking up over 60% of the total bandwidth in many parts of this country), as the saying toes in the industry *(&^ happens...