Routing problem in Nottingham?

JonathanLH · 22-12-2005, 17:34

I have a dedicated server in the USA, (Seattle, west coast) and since about 15 minutes ago, have been unable to access it. It is hosted in the WowRack datacenter, and I can't get to their site either www.wowrack.com

Traceroute here:

C:\WINDOWS>tracert 216.176.182.82

Tracing route to 216.176.182.82 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router2 [10.0.0.252]
2 7 ms 8 ms 11 ms nott-grim-ubr-1-ge20.inet.ntl.com [10.189.223.254]
3 11 ms 9 ms 10 ms nott-t2cam1-a-v128.inet.ntl.com [80.4.47.161]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.

Normally it routes over OpenTransit, or Level3

EDIT: Just got this

C:\WINDOWS>tracert 216.176.182.82

Tracing route to 216.176.182.82 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router2 [10.0.0.252]
2 9 ms 12 ms 18 ms nott-grim-ubr-1-ge20.inet.ntl.com [10.189.223.254]
3 12 ms 11 ms 38 ms nott-t2cam1-a-v128.inet.ntl.com [80.4.47.161]
4 * 10 ms * nott-t2core-a-ge-wan84.inet.ntl.com [80.1.79.105]
5 * * * Request timed out.
6 * nott-t2core-a-ge-wan84.inet.ntl.com [80.1.79.105] reports: Destination host unreachable.

22-12-2005, 18:49

I can get the site to load, now, wheras earlier, while at work, it crashed my browser, when I clicked on the link.

Code:

12/22/05 17:50:44 Fast traceroute 216.176.182.82
Trace 216.176.182.82 ...
 1 10.189.183.254   19ms   10ms   15ms  TTL:  0  (No rDNS)
 2 10.189.183.254   26ms   10ms   18ms  TTL:  0  (No rDNS)
 3 80.4.47.161      26ms   14ms  147ms  TTL:  0  (nott-t2cam1-a-v128.inet.ntl.com ok)
 4 80.1.79.77       50ms   42ms   16ms  TTL:  0  (nott-t2core-a-ge-wan73.inet.ntl.com ok)
 5 80.1.79.2        18ms   25ms   16ms  TTL:  0  (nott-t2core-b-ge-wan91.inet.ntl.com ok)
 6 62.253.188.37    47ms   25ms   18ms  TTL:  0  (nth-bb-b-so-300-0.inet.ntl.com ok)
 7 62.253.185.117   17ms   16ms   16ms  TTL:  0  (nth-bb-a-ae0-0.inet.ntl.com ok)
 8 193.251.254.141  83ms   28ms   36ms  TTL:  0  (so-0-3-2-0.loncr4.London.opentransit.net ok)
 9 193.251.154.90   72ms   43ms   46ms  TTL:  0  (so-0-0-0-0.fftcr4.Frankfurt.opentransit.net ok)
10 193.251.242.234  39ms   39ms   74ms  TTL:  0  (gi15-0.fftcr3.FrankfurtAmMain.opentransit.net ok)
11 208.51.74.13     49ms   40ms   39ms  TTL:  0  (ge4-3-0-1000M.ar2.FRA3.gblx.net ok)
12 67.17.71.181    205ms  213ms  203ms  TTL:  0  (so6-0-0-2488M.ar2.SEA1.gblx.net ok)
13 64.215.184.162  209ms  206ms  204ms  TTL:  0  (ge-2.swift.gblx.net ok)
14 66.228.202.130  209ms  207ms  223ms  TTL:  0  (No rDNS)
15 216.176.182.82  213ms  222ms  204ms  TTL:107  (216-176-182-82.reverse.wowrack.com ok)

JonathanLH · 22-12-2005, 19:08

yeah, it's working now, thanks