Nov 16, 2010, 05:47 PM
They'll give me the typical response "pings and tracerts are low priority so you cannot use them to locate the source of the issue." You're the only one with the issue anyways.
Have you at least tried reducing your rate to see if loss goes away? Yes, choke will increase.
I assume you're posting from the IP you play with?
The outbound trace looks good
173.192.18.210 is likely the other side of 173.192.18.211, so it doesn't look like that's the problem.
Have you at least tried reducing your rate to see if loss goes away? Yes, choke will increase.
I assume you're posting from the IP you play with?
The outbound trace looks good
Code:
traceroute to yourip 30 hops max, 40 byte packets
1 mpdedicated.com (174.37.110.65) 0.389 ms 0.510 ms 0.798 ms
2 po105.dar01.sr01.dal01.networklayer.com (66.228.118.220) 0.313 ms 0.434 ms 0.503 ms
3 ae6.bbr01.eq01.dal03.networklayer.com (173.192.18.210) 0.241 ms 0.244 ms 0.243 ms
4 be-10-404-pe01.1950stemmons.tx.ibone.comcast.net (75.149.228.33) 1.155 ms 1.155 ms 1.153 ms
5 pos-2-3-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.153) 1.152 ms 1.151 ms 1.149 ms
6 pos-0-12-0-0-cr01.atlanta.ga.ibone.comcast.net (68.86.85.158) 22.773 ms 22.634 ms 22.630 ms
7 so-7-0-0-0-ar01.b0atlanta.ga.atlanta.comcast.net (68.86.93.202) 22.360 ms 22.397 ms 22.404 ms
8 xe-0-0-0-0-sur01.n1alpharetta.ga.atlanta.comcast.net (68.85.108.230) 24.038 ms 24.087 ms 24.082 ms
9 xe-11-3-0-0-sur01.n2alpharetta.ga.atlanta.comcast.net (68.85.108.234) 24.580 ms 24.686 ms 24.675 ms
10 68.85.68.54 (68.85.68.54) 25.054 ms 25.070 ms 25.324 ms^C173.192.18.210 is likely the other side of 173.192.18.211, so it doesn't look like that's the problem.