atlanta36+37 down?

Can you tracert to them? ping them?

Although though I don't have a linode on those machines, they're talking to my ssh client from Verizon FIOS land in NJ.

% ssh atlanta36.linode.com
The authenticity of host 'atlanta36.linode.com (63.247.71.231)' can't be established.
RSA key fingerprint is c7:be:7d:b3:73:5a:02:cd:34:41:11:c3:19:e7:1c:c0.
Are you sure you want to continue connecting (yes/no)? 

The hosts, and both of your nodes are responding fine for me.

You did perform a tracroute to eliminate a network problem between you and Atlanta, right?

-Chris

@sweh:

Can you tracert to them? ping them?

Although though I don't have a linode on those machines, they're talking to my ssh client from Verizon FIOS land in NJ.

% ssh atlanta36.linode.com
The authenticity of host 'atlanta36.linode.com (63.247.71.231)' can't be established.
RSA key fingerprint is c7:be:7d:b3:73:5a:02:cd:34:41:11:c3:19:e7:1c:c0.
Are you sure you want to continue connecting (yes/no)? 

I'm sitting on a very restricted terminal at the moment. It does not allow ping and such. I noticed that the .. wait.. now web access to lish is working on both hosts.

EDIT:

The CPU graph from the dashboard says I'm suddenly using 100% CPU but the top command I'm running through web-lish says approx 0%. Strange..

EDIT2:

uptime says:

16:00:28 up 20 days, 15:20, 4 users, load average: 1.00, 0.97, 0.91

but the dashboard cpu graph still says 100%.

I can reach d.neo101.org via web-lish but cannot ping neo101.org. Both d.neo101.org and neo101.org are linodes witing the same datacenter. So the problem is likely to be with the host and not on the way from my computer (in sweden) and the datacentre, right?

Also I should mention that the way I found out about this is that a service that pings my host once every 30 minutes sent me an sms alerting me about neo101.org. That service has not yet sent me an sms that everything is ok.

root@absecon1:/# ping neo101.org PING neo101.org (64.22.109.195) 56(84) bytes of data. 64 bytes from neo101.org (64.22.109.195): icmp_seq=1 ttl=51 time=35.3 ms 64 bytes from neo101.org (64.22.109.195): icmp_seq=2 ttl=51 time=37.5 ms

@caker:

root@absecon1:/# ping neo101.org
PING neo101.org (64.22.109.195) 56(84) bytes of data.
64 bytes from neo101.org (64.22.109.195): icmp_seq=1 ttl=51 time=35.3 ms
64 bytes from neo101.org (64.22.109.195): icmp_seq=2 ttl=51 time=37.5 ms

Yes, now it works again. I guess it was a temporary error of some kind. The dashboard cpu usage graph reports very low cpu usage again. So does the top command and d.neo101.org can ping neo101.org.

Do you know what happened and if it was related?

EDIT:

host-tracker.com also reports that everything is ok now.