Yup same here on NY2 the VPS in spam of 9 hrs went down for reboot twice due to possible underlying node issues. What action did DO do ?

I am trying to take a snapshot so i can move it from NY2 to San Francisco region right now

well my snapshot process has been stuck for over an hour now and no way of stopping the process for manual migration

5+ hrs of downtime and counting https://nodeping.com/reports/uptime/gbc9ojls-uxiw-4r6s-9ixh-omk139scycm5 !

My site is down again and there is nothing we can do.

Sounds like we might both be on the same node ? You at NY2 ? I at 6+ hour downtime mark now https://nodeping.com/reports/uptime/gbc9ojls-uxiw-4r6s-9ixh-omk139scycm5?interval=days&start=1384698357815&end=1385856000000 with snapshot process still stuck. DO support finally got back to me they're looking into it.

My site is hosted in nyc 1 is down. Is very disappointing the service.

"...their quality doesn't make them competitor to other cloud providers."

Really? Because other cloud providers are not susceptible to hardware failures?

Maybe I'm on the same node as you. According to my monitoring my droplet has been down for the last 6 hours. I received no notification of any issue from DO and would have been ignorant of the issues except for my own external independent monitoring.

Googling "digital ocean hardware failure" gives this answer as one of the top results: https://www.digitalocean.com/community/questions/is-harddisk-failure-transparent-to-me which seems to indicate we should have been moved to a new server within 15 to 25 minutes.

Maybe that answer is not relevant to the situation happening now, but we are way past 15 to 25 minutes. I was disappointed that DO's monitoring either did not catch this or that they did not notify customers of the failure.

I'm already more than six hours out of the air and still not getting any concrete answer on when the service will be available again, only that this was such a hardware problem!

Mine is back up now

today, for the second time in a week, my snapshot never ends,...

the first ime it taken more than 9 hours... when service was offline ... damn ... and it's happening again...