[mackys@shell ~]$ ping www.gully.org
PING www.gully.org (220.127.116.11) from 18.104.22.168 : 56(84) bytes of data.
64 bytes from 22.214.171.124: icmp_seq=0 ttl=54 time=46.8 ms
64 bytes from 126.96.36.199: icmp_seq=1 ttl=54 time=46.7 ms
64 bytes from 188.8.131.52: icmp_seq=5 ttl=54 time=46.8 ms
64 bytes from 184.108.40.206: icmp_seq=6 ttl=54 time=46.6 ms
64 bytes from 220.127.116.11: icmp_seq=7 ttl=54 time=46.8 ms
64 bytes from 18.104.22.168: icmp_seq=10 ttl=54 time=43.8 ms
64 bytes from 22.214.171.124: icmp_seq=11 ttl=54 time=42.9 ms
64 bytes from 126.96.36.199: icmp_seq=12 ttl=54 time=93.0 ms
64 bytes from 188.8.131.52: icmp_seq=14 ttl=54 time=50.0 ms
64 bytes from 184.108.40.206: icmp_seq=16 ttl=54 time=46.9 ms
64 bytes from 220.127.116.11: icmp_seq=18 ttl=54 time=46.9 ms
64 bytes from 18.104.22.168: icmp_seq=19 ttl=54 time=46.6 ms
64 bytes from 22.214.171.124: icmp_seq=24 ttl=54 time=47.0 ms
--- www.gully.org ping statistics ---
26 packets transmitted, 13 packets received, 50% packet loss
round-trip min/avg/max = 42.9/50.0/93.0 ms
More or less returning every second packet. That's amusing...
Linode is apparently having network-wide issues due to a botched upgrade.
> During a shared library update distributed to our hosts, a number of the hosts incorrectly
> have marked Linodes as being shut down. To recover from this we may be issuing host reboots
> to upgrade their software to our latest stack, and then bringing the Linodes to their last
> state. We're working on this now and expect to have additional updates shortly. We'll also be
> notifying those affected via our support ticket system. Please stand by.
I didn't see any other threads, and their forums are down with the rest of their site so I figured I should post here.
One of my linodes has been down 2 hours now and another 2 for about 20 minutes each. Linode has been disturbingly quiet on updates. The last one was an hour ago as of this writing via twitter: "Linodes are continuing to come up as we recover from the outage"
Linode has some serious customer service issues here. First of all these updates are not nearly frequent or informative enough. Further, there is no reliable way for customers to receive updates. Their forums are useless if their entire site is going to be down, and they have no status page. They should have a SEPARATELY HOSTED status site that doesn't go down with everything else. It's ridiculous to force users to go searching for any sort of communication on twitter and elsewhere.
SRSLY Linode - having a 2nd location where you can host a status page when a back-hoe digs up your main site's fiber is networking 201. How come you guys can't figure that out?
Also, who's the genius who pushed out an update so poorly tested that it crashed every last linode? You *do* test your code before you deploy it, don't you?? (No, don't answer that. I don't want to know. Or rather, I already know...)
I'm not really complaining. Linode is a great deal and I'm not about to stop giving them money. And it's not like I'm hosting anything important or necessary on Linode. But I do have to wonder what they're thinking sometimes... or if they even are thinking at all.