jamesb wrote:
The server is i3d in The Netherlands.
I did a trace if anyone can understand it.
TraceRoute to 84.244.130.16
Hop (ms) (ms) (ms) IP Address Host name
1 1 0 0 66.98.244.1 gphou-66-98-244-1.ev1servers.net
2 0 0 1 66.98.241.16 gphou-66-98-241-16.ev1servers.net
3 0 0 0 66.98.240.13 gphou-66-98-240-13.ev1servers.net
4 1 1 1 129.250.11.137 ge-1-11.r04.hstntx01.us.bb.gin.ntt.net
5 2 2 1 129.250.2.230 xe-0-1-0.r21.hstntx01.us.bb.gin.ntt.net
6 6 6 6 129.250.4.68 p64-1-3-0.r21.dllstx09.us.bb.gin.ntt.net
7 10 6 6 154.54.11.193 t8-3.mpd01.dfw03.atlas.cogentco.com
8 6 6 6 154.54.6.93 t8-2.mpd01.dfw01.atlas.cogentco.com
9 120 120 125 154.54.2.230 t9-2.mpd01.mci01.atlas.cogentco.com
10 123 124 123 154.54.2.234 t2-3.mpd01.ord01.atlas.cogentco.com
11 48 48 47 154.54.6.17 t2-1.mpd01.bos01.atlas.cogentco.com
12 125 120 120 130.117.0.186 t1-3.mpd02.lon01.atlas.cogentco.com
13 128 127 128 130.117.1.169 p3-2.mpd01.ams03.atlas.cogentco.com
14 119 119 120 130.117.240.22 we-dare-bv.demarc.cogentco.com
15 125 117 117 84.244.177.1 ge-1-1-1.cr1.rtd.we-dare.net
16 120 121 120 84.244.130.16 -
Trace complete
All the trace route does is count the hops in between a destination. Anyways, call the people whom actually HOST the server, tell them go do a hard-reboot on the server. Maybe (especially if it's a winblows server) a daemon just crashed. I would suggest having them manually bring it back up before I make any types of assumptions.