Guys, this is BRUTAL.

Why are you doing shared library upgrades in the middle of the afternoon when they can affect ALL of your sites like this? I like the fact that I can have geographical diversity with your services but what's the point if you do things that take out all the sites...

Do you have any updates or an ETA on when this will be resolved?

I agree, this is brutal.... My monitors show that my outage started at 1:10PM (PDT). It's now 2:34PM... help

I have to admit it seems that pushing the upgrade to all data centres at ones wasn't the smartest option, but then again, it may have been inevitable to do all datacentres at once. I'm sure it'll be elaborated upon once this issue has been resolved.

My linode is up again (downtime less than 2 hours), so thanks for fixing it

What DC are you in?
I'm in Atlanta and my host is still up and running fine (knock on wood).

I wish i could say the same about the linode.com page, it's slow as hell (including the forums).

Glad you said that, I was going nuts trying to figure out what is wrong with my network connection.

2 hours and counting...

Argh!!

My Linode and sites are running, but my host actually has a load (first time I've seen that since I've been at Linode). My SSH session is locked up and I can't reboot or shutdown my Linode.

I'm in Fremont.

*linode.com/* is slow has molasses for me as well. Except for accessing the support page. That loaded and sent my support request nice and speedy

Support referred me to this thread.

They sent me to this thread, after I had already posted on it. And support isn't updating the thread, so what's the point?

This isn't OK. 3 hours. Deafening silence. No progress updates. I've loved Linode up till now, but I can't accept this type of lack of communication.

I think we would all feel better if Linode would commit to providing regular and frequent updates. This lack of communication is beyond frustrating.

So we were supposed to be notified via the support system of this outage? We didn't receive anything. Our linodes were shutdown ungracefully, which of course isn't good for our databases.

We run a public safety avalanche forecast site on one of these linodes and it's the first day of wet, unstable snow. We only saw 8 minutes of downtime, luckily. 2 hours like others are reporting would've definitely been unacceptable.

Well. My linode at Fremont was rebooted around 30 minutes ago. Total downtime is around 20 minutes according to Pingdom, although from the Linode Manager it looks like at least 1-2 hours offline. The downtime would be even less if I did not forget to bootstrap some services in RC script. Everything is speedy again -- unlike the Linode website and this forum.

You guys hosted on a Linode 360?!

3 hours and 20 minutes. It looks like my server is 80% up now. I still see some errors. And the instance is slooooooooooooooow.

I've been offline since 4:05pm EST. That's nearly 4 hours now and I've seen one(1)! update in this thread in that time. They're not large sites but I was running some critical processes at the time. I'm fed up.

We've been working as fast as we can to bring the machines affected to a stable state.

There are still a few problem hosts we're working through, although we expect all issues to be resolved shortly. Please stand by for additional updates.

-Chris

My linode has been down over 4 hours now with no warning and no information other than a canned response from support referring me to this thread. Not impressed.

Can we please get some forewarning next time?

I understand these things happen, but it sounds to me like this could have been avoided, or at least delayed.

We could have at least gotten some warning to let our clients know.