[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [cobalt-users] calling cobaltrack customers...



Amanda and Gary,
Mine's like that too. Once the tracert hits Washington DC it nearly falls
over dead. There's got to be something wrong with that Cable & Wireless node
there.
It's normally not like this at all.

Here's my trace if anyone's interested, I'm in VA Beach, @Home cable
connection:
Tracing route to 208.155.66.219 over a maximum of 30 hops

  1    14 ms    14 ms    13 ms  10.86.66.1
  2    15 ms    15 ms    14 ms  10.0.191.1
  3    16 ms    15 ms    15 ms  10.0.188.1
  4    16 ms    15 ms    15 ms  c1-pos5-0.nrflva1.home.net [24.7.73.109]
  5    24 ms    24 ms    24 ms  c1-pos5-0.gnvlsc1.home.net [24.7.65.217]
  6    32 ms    31 ms    31 ms  c1-pos3-0.atlnga1.home.net [24.7.65.65]
  7    33 ms    32 ms    31 ms  208.172.67.205
  8    34 ms    33 ms    34 ms  corerouter1.Atlanta.cw.net [204.70.9.142]
  9    53 ms     *      517 ms  corerouter1.WashingtonEast.cw.net
[204.70.9.133]
 10    53 ms    58 ms    53 ms  acr1-loopback.Washingtondck.cw.net
[206.24.226.61]
 11  1936 ms  2895 ms  2620 ms  bar3-loopback.Washingtondck.cw.net
[206.24.226.8]
 12  2686 ms  3046 ms  2124 ms  visual-link-internet.Washingtondck.cw.net
[208.173.0.122]
 13  2068 ms     *     2631 ms  208.155.66.219

Trace complete.

Carrie Bartkowiak