Knowledgebase
EasySpace?
| Posted by JenniH, 11-01-2006, 05:26 AM | |
Does anyone know what the problem is?
Traceroutes give:
TraceRoute to 84.22.161.57 [www.easyspace.com]
Hop (ms) (ms) (ms) IP Address Host name
1 0 0 0 66.98.244.1 gphou-66-98-244-1.ev1.net
2 0 0 0 66.98.241.16 gphou-66-98-241-16.ev1.net
3 0 0 0 38.99.206.173 -
4 Timed out Timed out Timed out
And:
Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time
1 0 0 1 0.6 ms
66.36.240.2 AS14361
HOPONE-DCA c-vl102-d1.acc.dca2.hopone.net. 255 US Unix: 9:24:14. 39
2 * * * 99999 ms [+99999ms]
[Unknown] [Unknown - Firewall did not respond] 0 miles [+0]
3 * * * 99999 ms [+0ms]
[Unknown] [Unknown - Firewall did not respond] 0 miles [+0]
4 * * * 99999 ms [+0ms]
[Unknown] [Unknown - Firewall did not respond] 0 miles [+0]
5 * * * 99999 ms [+0ms]
[Unknown] [Unknown - Firewall did not respond]
[4 hops with no response:
assuming we hit a firewall
that blocks pings]
This doesn't mean too much to me, other than that there is a problem somewhere. Could anyone interpret?
Thanks.
Jenni
|
| Posted by Russ Foster, 11-01-2006, 05:31 AM | |
Reading that I would say their routing information has disspeared from the network as it doesn't seem that the traceroutes are even getting onto their networks. However it is loading from here for me and from a box in London
|
| Posted by JenniH, 11-01-2006, 06:48 AM | |
Yes, it seems to be back again now. Everything was down there for a while... strange.
Thanks.
|
| Posted by Henrik, 11-06-2006, 03:54 AM | |
You could read this blog-post on the matter: http://www.hypocrisy.nu/2006/11/01/l...rly-this-year/
|
| Posted by JenniH, 11-06-2006, 09:04 AM | |
Ahh. Interesting. I never did get an explanation. Thanks Henrik.
|
| Posted by Henrik, 11-06-2006, 10:05 AM | |
I am not saying that this is the case, but it is a.. co-incident - so to speak...
|
|
 Add to Favourites
 Print this Article
|
Also Read
