traceroute info

t3ase

Banned
Contributor
I've been following the traceroute results the past few days when the site's been bogged down.. It looks like border*.servepath.com is the part of the transfer that causes the huge delay. Last night it was about 197ms while now it's at 90ms. Can anything be done about that? Anyone else do the same thing yet to see what comes up?
maptable-msprotegecom.jpg
 
107ms difference isn't even comprehensible to the human being so i don't think the problem would be there. nice traceroute program tho.
 
Code:
C:\>tracert msprotege.com

Tracing route to msprotege.com [216.93.182.168]
over a maximum of 30 hops:

  1    10 ms    10 ms    10 ms  10.160.120.1
  2   <10 ms    10 ms    10 ms  12.244.107.161
  3    40 ms    10 ms   <10 ms  12.244.72.234
  4   <10 ms    10 ms    10 ms  gbr1-p50.cgcil.ip.att.net [12.123.5.74]
  5    20 ms    20 ms    20 ms  tbr2-p013502.cgcil.ip.att.net [12.122.11.49]
  6    10 ms   <10 ms    20 ms  ggr1-p3100.cgcil.ip.att.net [12.122.11.210]
  7    10 ms    10 ms    10 ms  0.so-1-2-1.BR6.CHI2.ALTER.NET [204.255.169.145]

  8    10 ms    10 ms    10 ms  0.so-3-1-0.XL1.CHI2.ALTER.NET [152.63.71.93]
  9    10 ms    10 ms    10 ms  0.so-0-0-0.TL1.CHI2.ALTER.NET [152.63.68.82]
 10    71 ms    70 ms    80 ms  0.so-4-1-0.TL1.SCL2.ALTER.NET [152.63.1.25]
 11    80 ms    70 ms    70 ms  0.so-4-0-0.XL1.SCL2.ALTER.NET [152.63.0.254]
 12    70 ms    70 ms    70 ms  0.so-6-0-0.GW2.SCL2.ALTER.NET [152.63.56.253]
 13    80 ms    80 ms    70 ms  servepath-gw.customer.alter.net [157.130.203.38]

 14    70 ms    80 ms   100 ms  access1-ge3-0-4.sfo.servepath.net [216.93.189.98]
 15    71 ms    80 ms    70 ms  customer-server-168.servepath.com [216.93.182.168]

Trace complete.

C:\>
 
Well, while that may seem like a low ms time; it's still a bottleneck that I'm frequently seeing. HRM...
 
Back