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

[Graeme Fowler <graeme.f@xxxxxxxxxxxxxxx>]

Gary Peltola wrote:

> I just got a server from them and i am getting second thoughts
<snip>

Doing a traceroute from here gives me the same problem - but it's
*outside* of the Cobaltracks network (sanitised):

traceroute to 208.155.68.1 (208.155.68.1), 30 hops max, 40 byte packets
 1  a.b.c.d          18.476 ms    18.868 ms     1.273 ms
 2  e.f.g.h           2.664 ms     1.378 ms     1.370 ms
 3  i.j.k.l          13.305 ms    13.223 ms    15.533 ms
 4  m.n.o.p         140.337 ms   207.190 ms   220.898 ms
 5  q.r.s.t          26.561 ms    18.521 ms    19.447 ms
 6  u.v.w.x          18.782 ms    19.293 ms    18.836 ms
 7  194.143.164.190  83.404 ms   108.357 ms    84.180 ms
 8  194.143.180.38   88.520 ms    89.991 ms    87.455 ms
 9  166.48.41.253    89.675 ms    91.236 ms   117.658 ms
10  204.70.9.133    123.965 ms    93.493 ms    89.736 ms
11  206.24.226.61   105.062 ms    99.286 ms    95.514 ms
12  206.24.226.8   1859.535 ms  2474.379 ms  2909.095 ms
13  208.173.0.118  2997.554 ms  3068.533 ms       *
    208.173.0.122  2875.679 ms       *            *
14  208.155.68.1   2481.231 ms  2185.870 ms  2379.298 ms

Hop 12 belongs to Cable & Wireless (as does the whole Cobaltracks netblock
you refer to) but looks like a transit block to me (use:
 'whois 206.24.226.8@xxxxxxxxxxxxxx')

I'd badger (a) Cobalracks *and* (b) C&W as it appears to be a routing
fault. It may not be Cobaltracks' fault at all...

Graeme