Tracing route to 66.135.42.153 over a maximum of 30 hops
  1    <1 ms    <1 ms    <1 ms  my secret IP
  2     1 ms     2 ms     1 ms my 2nd secret IP
  3    12 ms     4 ms     4 ms  vlan623.asr1.lon3.gblx.net [64.215.29.233]
  4     6 ms     6 ms     4 ms  4.68.110.157
  5   181 ms   203 ms   204 ms  vl-3602-ve-226.csw2.london1.level3.net [4.69.166
.149]
  6   209 ms   150 ms   155 ms  ae-56-221.ebr2.london1.level3.net [4.69.153.129]
  7   160 ms   203 ms   203 ms  ae-41-41.ebr1.newyork1.level3.net [4.69.137.66]
  8   159 ms   150 ms   154 ms  ae-81-81.csw3.newyork1.level3.net [4.69.134.74]
  9   306 ms   321 ms   255 ms  ae-82-82.ebr2.newyork1.level3.net [4.69.148.41]
 10   136 ms   278 ms   277 ms  ae-3-3.ebr2.dallas1.level3.net [4.69.137.121]
 11   293 ms   300 ms   303 ms  ae-82-82.csw3.dallas1.level3.net [4.69.151.153]
 12   257 ms   273 ms   326 ms  ae-3-80.edge9.dallas1.level3.net [4.69.145.144]
 13   431 ms   272 ms   183 ms  peer-1-netw.edge9.dallas1.level3.net [4.59.118.6
]
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16   278 ms   304 ms     *     66.135.42.153
 17   288 ms   317 ms   274 ms  66.135.42.153
Trace complete.
you people may not want to share home IP's... the first and second one ... anyways im running a hotel wireless connection, it looks reasonable on the tracert however im lagging like a ... something 

 i gave up on playing for the time being i cant do anything except chat and even that's hard due timing out