[Munra]

This server show ~120 ms ping in hlsw

Tracing route to chicago.colocrossing.com [205.234.203.93]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1 
  2    23 ms    10 ms    13 ms  74-130-176-1.dhcp.insightbb.com [74.130.176.1] 
  3    18 ms    20 ms    19 ms  74-128-19-153.dhcp.insightbb.com [74.128.19.153] 
  4    11 ms     8 ms    40 ms  74.128.9.229 
  5    99 ms   103 ms   117 ms  xe-8-3-0.edge4.Atlanta2.Level3.net [4.59.12.57] 
  6    94 ms    92 ms   105 ms  ae-27-52.car1.Atlanta4.Level3.net [4.68.103.44] 
  7    95 ms   101 ms   109 ms  atl-bb1-link.telia.net [213.248.68.53] 
  8    97 ms    95 ms    96 ms  xe-0-1-0.cr1.atl1.us.nlayer.net [69.31.135.205] 
  9   204 ms   131 ms   127 ms  xe-1-2-0.cr2.ord1.us.nlayer.net [69.22.142.45] 
 10   153 ms   132 ms   141 ms  po6.ar2.ord1.us.scnet.net [69.31.111.6] 
 11   142 ms   141 ms   129 ms  v55.ar1.ord1.us.scnet.net [216.246.95.129] 
 12   143 ms   144 ms   143 ms  61.po1.ar1.ord6.us.scnet.net [75.102.3.226] 
 13   116 ms   146 ms   151 ms  as36352.ge9-45.ar1.ord6.us.scnet.net [75.102.35.138] 
 14   116 ms    94 ms    96 ms  ge-0-1.FZ146.core.chicago.colocrossing.com [75.102.34.250] 
 15   178 ms   151 ms   143 ms  chicago.colocrossing.com [205.234.203.93] 

Trace complete.

Second server shows ~60 ms in hlsw

Tracing route to chicago.colocrossing.com [205.234.153.69]
over a maximum of 30 hops:

  1    <1 ms     1 ms     *     192.168.1.1 
  2    22 ms    21 ms    16 ms  74-130-176-1.dhcp.insightbb.com [74.130.176.1] 
  3    10 ms    11 ms    11 ms  74-128-19-153.dhcp.insightbb.com [74.128.19.153] 
  4    13 ms    36 ms    18 ms  74.128.9.229 
  5    26 ms    31 ms    33 ms  xe-8-1-0.edge4.Atlanta2.Level3.net [4.59.12.49] 
  6    90 ms   207 ms   219 ms  ae-27-52.car1.Atlanta4.Level3.net [4.68.103.44] 
  7    26 ms    21 ms    23 ms  atl-bb1-link.telia.net [213.248.68.53] 
  8    90 ms    31 ms    25 ms  xe-0-1-0.cr1.atl1.us.nlayer.net [69.31.135.205] 
  9    29 ms    32 ms    28 ms  xe-1-2-0.cr2.ord1.us.nlayer.net [69.22.142.45] 
 10    43 ms    36 ms    45 ms  po6.ar2.ord1.us.scnet.net [69.31.111.6] 
 11    52 ms    45 ms    41 ms  v55.ar1.ord1.us.scnet.net [216.246.95.129] 
 12    30 ms    28 ms    31 ms  61.po1.ar1.ord6.us.scnet.net [75.102.3.226] 
 13    32 ms    31 ms    39 ms  as36352.ge9-44.ar1.ord6.us.scnet.net [75.102.4.30] 
 14    27 ms    40 ms    38 ms  ge-0-1.FZ146.core.chicago.colocrossing.com [75.102.34.250] 
 15    45 ms    34 ms    31 ms  chicago.colocrossing.com [205.234.153.69] 

Trace complete.

Thanks for looking

[bhumphries]

Munra,

It appears that the issue stems from Level 3's network in Atlanta. As you can see in both trace routes there is a jump in latency entering Atlanta. This jump in latency just appears to be having a more adverse effect on your routing to the first server listed there. We can look into this more for you and get in touch with Level3, however please submit a ticket with us via our billing panel and provide us with your personal IP so we can look into the reverse routing.

Thanks!