Thread: Reporting Lag - How to Tracert

Tracert results should look like:

Code:

C:\Windows\system32>tracert tpgbf4.nfoservers.com


Tracing route to tpgbf4.nfoservers.com [67.215.65.132]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    33 ms    28 ms    29 ms  c-98-215-144-1.hsd1.il.comcast.net [98.215.144.1]
  3     9 ms     9 ms     8 ms  te-9-1-ur02.pekin.il.chicago.comcast.net [68.85.179.69]
  4    12 ms     9 ms     7 ms  te-8-3-ur01.pekin.il.chicago.comcast.net [68.85.176.130]
  5    17 ms    18 ms    19 ms  te-0-11-0-9-ar01.area4.il.chicago.comcast.net [68.85.177.162]
  6    17 ms    20 ms    21 ms  he-3-7-0-0-cr01.350ecermak.il.ibone.comcast.net [68.86.90.53]
  7    17 ms    19 ms    19 ms  he-1-2-0-0-cr01.chicago.il.ibone.comcast.net [68.86.88.25]
  8     *        *        *     Request timed out.
  9    40 ms    37 ms    36 ms  4.69.158.218
 10    37 ms    36 ms    38 ms  ae-101-3501.edge2.chicago2.level3.net [4.69.158.1]
 11    16 ms    18 ms    16 ms  open-dns-in.edge2.chicago2.level3.net [4.30.175.70]
 12    18 ms    16 ms    15 ms  hit-nxdomain.opendns.com [67.215.65.132]


Trace complete.

To do a tracert, open a command prompt (cmd.exe if you go to the start menu -> run) and type:

tracert <server ip/name>

The bf4 servers are named following (use the name because the ip may change):
tpgbf4.game.nfoservers.com
teamplayergaming.game.nfoservers.com

CSGO (use the name because the ip may change):
tpgcsgoserver.game.nfoservers.com

TF2:
72.249.124.135

L4D2:
50.56.185.42

DOD:S:
72.249.124.131

Reporting lag without this information is relatively useless to us, so please. Pretty please with sugar on it. Tracert.

This looks bad. Is this bad? I know my internet is terrible back here, but I usually just deal with it. (I'm in Los Angeles.)

Code:

C:\Users\Zoe>tracert 72.249.124.135

Tracing route to 135.124.249.72.hypernia.com [72.249.124.135]
over a maximum of 30 hops:

  1     3 ms     3 ms     3 ms  192.168.1.1
  2    38 ms    29 ms    30 ms  cpe-98-148-208-1.socal.res.rr.com [98.148.208.1]

  3    14 ms    12 ms    12 ms  tge0-7-0-7.cnpkca2601h.socal.rr.com [76.166.8.41
]
  4    12 ms    11 ms    16 ms  agg21.chwocadq01r.socal.rr.com [72.129.27.128]
  5    17 ms    15 ms    15 ms  agg24.lsancarc01r.socal.rr.com [72.129.25.0]
  6    18 ms    20 ms    15 ms  agg1.cyprcabw01r.socal.rr.com [72.129.21.1]
  7    18 ms    19 ms    19 ms  agg10.cyprcabw02r.socal.rr.com [72.129.21.5]
  8    19 ms    19 ms    16 ms  agg27.tustcaft01r.socal.rr.com [72.129.21.2]
  9    19 ms    18 ms    20 ms  ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214]
 10    18 ms    16 ms    18 ms  bu-ether14.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.4]
 11     *        *        *     Request timed out.
 12    18 ms    17 ms    15 ms  bboi.net.any2ix.coresite.com [206.223.143.33]
 13    28 ms    40 ms    38 ms  phx-ten2-1-la-ten3-3.bboi.net [64.127.128.146]
 14    49 ms    48 ms    50 ms  dal-ten2-4-phx-ten1-1.bboi.net [64.127.128.237]

 15   193 ms   203 ms   216 ms  8011-on-net-cust.bboi.net [64.127.129.118]
 16    49 ms    50 ms    51 ms  quadranet-colocrossing.quadranet.com [96.44.148.
54]
 17    50 ms    68 ms    54 ms  host.colocrossing.com [206.217.134.14]
 18    48 ms    51 ms    50 ms  135.124.249.72.hypernia.com [72.249.124.135]

Trace complete.

C:\Users\Zoe>tracert 72.249.124.135

Tracing route to 135.124.249.72.hypernia.com [72.249.124.135]
over a maximum of 30 hops:

  1     3 ms     3 ms     3 ms  192.168.1.1
  2    37 ms    13 ms    24 ms  cpe-98-148-208-1.socal.res.rr.com [98.148.208.1]

  3    12 ms    13 ms    11 ms  tge0-7-0-7.cnpkca2601h.socal.rr.com [76.166.8.41
]
  4    13 ms    15 ms    16 ms  agg21.chwocadq01r.socal.rr.com [72.129.27.128]
  5    16 ms    15 ms    15 ms  agg24.lsancarc01r.socal.rr.com [72.129.25.0]
  6    18 ms    15 ms    18 ms  agg1.cyprcabw01r.socal.rr.com [72.129.21.1]
  7    18 ms    20 ms    19 ms  agg10.cyprcabw02r.socal.rr.com [72.129.21.5]
  8    20 ms    16 ms    19 ms  agg27.tustcaft01r.socal.rr.com [72.129.21.2]
  9    17 ms    15 ms    16 ms  ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214]
 10    17 ms    15 ms    16 ms  bu-ether14.lsancarc0yw-bcr00.tbone.rr.com [66.10
9.6.4]
 11     *        *        *     Request timed out.
 12    15 ms    16 ms    16 ms  bboi.net.any2ix.coresite.com [206.223.143.33]
 13    25 ms    25 ms    25 ms  phx-ten2-1-la-ten3-3.bboi.net [64.127.128.146]
 14    48 ms    47 ms    48 ms  dal-ten2-4-phx-ten1-1.bboi.net [64.127.128.237]

 15    50 ms    51 ms    50 ms  8011-on-net-cust.bboi.net [64.127.129.118]
 16    51 ms    52 ms    49 ms  quadranet-colocrossing.quadranet.com [96.44.148.
54]
 17    50 ms    50 ms    51 ms  host.colocrossing.com [206.217.134.14]
 18    49 ms    51 ms    50 ms  135.124.249.72.hypernia.com [72.249.124.135]

Trace complete.

C:\Users\Zoe>

one hop is pretty bad, but the rest look ok. Not a whole lot you can do about that one hop thought. It's out of roadrunner's control.

It's rubberbanding bad. For everyone, not just me.

There was only two people connected... I restarted it. And cleaned up a couple of teamspeak instances that shouldn't have been running... maybe that will help